[Meterred]
meter=image
SolidColor=#Accent9#,80
X=0
y=0
h=300
w=300
[measureCPU]
; This measure returns the average CPU load between all cores.
Measure=CPU
Processor=0
[measureRAM]
; Returns the amount of RAM used in bytes.
Measure=PhysicalMemory
UpdateDivider=20
; UpdateDivider sets the rate at which the value of the measure is updated. It is
; calculated as follows: UpdateDivider x Update. In this case, Update is set to
; 1000 milliseconds (in the [Rainmeter] section). 1000 x 20 = 20000 ms or 20 seconds.
[measureSWAP]
Measure=SwapMemory
UpdateDivider=20
[styleLeftText]
StringAlign=Left
FontColor=#colorText#
FontFace=Teko
FontSize=14
AntiAlias=1
[styleRightText]
StringAlign=Right
StringCase=None
StringStyle=Bold
StringEffect=Shadow
FontEffectColor=0,0,0,20
FontColor=#colorText#
FontFace=#fontName#
FontSize=#textSize#
AntiAlias=1
ClipString=1
[styleBar]
BarColor=#colorBar#
BarOrientation=HORIZONTAL
SolidColor=255,255,255,30
[meterTitle]
Meter=String
; Using MeterStyle=styleTitle will basically "copy" the
; contents of the [styleTitle] section here during runtime.
X=150
Y=6
W=190
H=18
Text=System
StringAlign=Center
StringCase=Upper
FontColor=ffffff
FontFace=Die in a fire PG
FontSize=20
AntiAlias=1
; Even though the text is set to System, Rainmeter will display
; it as SYSTEM, because styleTitle contains StringCase=Upper.
LeftMouseUpAction=["taskmgr.exe"]
; Left-clicking this meter will launch taskmgr.exe (the Task Manager).
ToolTipText=Open Task Manager
; Hovering over this meter will display a tooltip with the text above.
[meterLabelCPU]
Meter=String
MeterStyle=styleLeftText
X=10
Y=50
W=190
H=14
Text=CPU Usage
[meterValueCPU]
Meter=String
fONTCOLOR=ffffff
AntiAlias=1
FONTFACE=Teko
fontsize=15
MeasureName=measureCPU
X=210
Y=72
Text=%1%
[meterBarCPU]
Meter=Bar
MeterStyle=styleBar
MeasureName=measureCPU
X=10
Y=70
W=190
H=20
[meterLabelRAM]
Meter=String
MeterStyle=styleLeftText
X=10
Y=100
W=190
H=14
Text=RAM Usage
[meterValueRAM]
Meter=String
fONTCOLOR=ffffff
AntiAlias=1
FONTFACE=Teko
fontsize=15
MeasureName=measureRAM
X=210
Y=122
W=190
H=14
Text=%1%
Percentual=1
[meterBarRAM]
Meter=Bar
MeterStyle=styleBar
MeasureName=measureRAM
X=10
Y=120
W=190
H=20
are almost very similar. The second one is from a skin that I made a long time ago, which I am integrating into my other larger skin.
The CPU bar in the second one is refreshing wayyy faster than the first one. Even tough, I have set Updatedivider=20 in both of them
What am I doing wrong? What is the ideal refreshrate for CPU or RAM measures
You do not have the required permissions to view the files attached to this post.
[Meterred]
meter=image
SolidColor=#Accent9#,80
X=0
y=0
h=300
w=300
[measureCPU]
; This measure returns the average CPU load between all cores.
Measure=CPU
Processor=0
[measureRAM]
; Returns the amount of RAM used in bytes.
Measure=PhysicalMemory
UpdateDivider=20
; UpdateDivider sets the rate at which the value of the measure is updated. It is
; calculated as follows: UpdateDivider x Update. In this case, Update is set to
; 1000 milliseconds (in the [Rainmeter] section). 1000 x 20 = 20000 ms or 20 seconds.
[measureSWAP]
Measure=SwapMemory
UpdateDivider=20
[styleLeftText]
StringAlign=Left
FontColor=#colorText#
FontFace=Teko
FontSize=14
AntiAlias=1
[styleRightText]
StringAlign=Right
StringCase=None
StringStyle=Bold
StringEffect=Shadow
FontEffectColor=0,0,0,20
FontColor=#colorText#
FontFace=#fontName#
FontSize=#textSize#
AntiAlias=1
ClipString=1
[styleBar]
BarColor=#colorBar#
BarOrientation=HORIZONTAL
SolidColor=255,255,255,30
[meterTitle]
Meter=String
; Using MeterStyle=styleTitle will basically "copy" the
; contents of the [styleTitle] section here during runtime.
X=150
Y=6
W=190
H=18
Text=System
StringAlign=Center
StringCase=Upper
FontColor=ffffff
FontFace=Die in a fire PG
FontSize=20
AntiAlias=1
; Even though the text is set to System, Rainmeter will display
; it as SYSTEM, because styleTitle contains StringCase=Upper.
LeftMouseUpAction=["taskmgr.exe"]
; Left-clicking this meter will launch taskmgr.exe (the Task Manager).
ToolTipText=Open Task Manager
; Hovering over this meter will display a tooltip with the text above.
[meterLabelCPU]
Meter=String
MeterStyle=styleLeftText
X=10
Y=50
W=190
H=14
Text=CPU Usage
[meterValueCPU]
Meter=String
fONTCOLOR=ffffff
AntiAlias=1
FONTFACE=Teko
fontsize=15
MeasureName=measureCPU
X=210
Y=72
Text=%1%
[meterBarCPU]
Meter=Bar
MeterStyle=styleBar
MeasureName=measureCPU
X=10
Y=70
W=190
H=20
[meterLabelRAM]
Meter=String
MeterStyle=styleLeftText
X=10
Y=100
W=190
H=14
Text=RAM Usage
[meterValueRAM]
Meter=String
fONTCOLOR=ffffff
AntiAlias=1
FONTFACE=Teko
fontsize=15
MeasureName=measureRAM
X=210
Y=122
W=190
H=14
Text=%1%
Percentual=1
[meterBarRAM]
Meter=Bar
MeterStyle=styleBar
MeasureName=measureRAM
X=10
Y=120
W=190
H=20
are almost very similar. The second one is from a skin that I made a long time ago, which I am integrating into my other larger skin.
The CPU bar in the second one is refreshing wayyy faster than the first one. Even tough, I have set Updatedivider=20 in both of them
What am I doing wrong? What is the ideal refreshrate for CPU or RAM measures
UpdateDivider is affected by the Rainmeter section. What is your skins' Update?
the DA GALLERYFor some Reason, the square root of X2 does not involve X
Alloutofmercy wrote: ↑January 13th, 2022, 7:31 pm
What is the ideal refreshrate for CPU or RAM measures
As David8192 said, the update of a measure or meter is controlled by both, the Update option of the [Rainmeter] section, as well as the UpdateDivider option set on the measure or meter itself. For most skins the default Update=1000 (in [Rainmeter] section) is the best approach. Furthermore most (or even all) skins using WebParser measures (at least those parsing online resources - however how often go such skins online to get the resources is controlled by the UpdateRate option of the parent WebParser measure as well) practically must have the default Update=1000 option (and UpdateDivider=1 on the parent WebParser measure).
For CPU and RAM measures the default UpdateDivider=1 is again the best approach. In fact for most skins and most measures / meters, these are the best options. Exceptions are the visualizer skins and skins showing up some animations, which have to have a much lower Update value.
You can find a very good description of all this things here: https://docs.rainmeter.net/tips/update-guide/
Alloutofmercy wrote: ↑January 14th, 2022, 7:21 am
This is what I've set for my meter. However something is bothering it and it is not updating by that rate
And what UpdateDivider is set on the (probably String) meter, showing the result returned by the [measureCPU] measure?
