This may optionally be used in place of specific Category and Counter options on the measure. Alias Default: NoneĪlias or 'shortcut' for a particular Category and Counter combination. Options General measure optionsĪll general measure options are valid. Additional Alias values may be supported over time. The UsageMonitor plugin will optionally allow you to select common counters with a single Alias, rather than the specific, case-sensitive Category and Counter names. So each measure will have distinct number and string values. The measure will return the current number value of the instance, and the current string value of the name of the instance. So for example, Index=1 would return the current value and name of the instance with the highest value for that counter. This will be either Index=0, which will always return the current total of all instances for a given counter, Index=-1, which will always return the current average of all instances for a given counter,or Index=N, which will return the instance at the defined point in a sorted list of all instances, with their values ordered from most to least. This will be the specific (case sensitive) text name of a single given instance, and will return the current value for that specific instance of a counter. The UsageMonitor plugin will allow you to define instance in the measure in one of two ways: Instance - Counters may have individual instances like 'Rainmeter' or 'C:'.Counter - Categories have individual counters like '% Processor Time' or 'Bytes Read/sec'.This is also referred to as Object in Perfmon.exe Category - Counters are organized into related categories like 'Process' or 'PhysicalDisk'.To open it, run Perfmon.exe.Ĭounters in Windows Performance Monitor have the following hierarchy: All available counters can be viewed using the Performance Monitor application. The Windows Performance Monitor exposes counters, which monitor various kinds of system metrics in different categories, and tracks their usage. However as said just to form better habits, which in future might be useful, using the brackets is indeed a good idea (same way as enclosing the values set through bangs into quotes).Plugin=UsageMonitor retrieves infromation from the Windows Performance Monitor. IfTrueAction=!SetOption TempMeterBar BarColor 0,0,255,255 is same well as IfTrueAction=. If only one single bang is used, it works even with no brackets. If you want to set such a condition into another measure, you have to use the name of the measure explicitly.Īlthough this always is an excelent idea, it's not mandatory. Note that this works ONLY if the condition is set into the same measure. For instance the above IfCondition might be: IfCondition=#CURRENTSECTION#40) & (#CURRENTSECTION#<=46). That's why it is always a better idea to use the #CURRENTSECTION# variable instead of naming exactly the measure. Any idea what might be happening?īalala wrote: ↑ February 19th, 2020, 2:09 pm

Won't change color at all after it turns blue. If it's anywhere over that initially, it stays white until it drops to fulfill that condition. The thing is, the color only stays blue when it registers temperature measure <=40. Values I took for my processor from here: IfTrueAction5=!SetOption TempMeterBar BarColor 255,0,0,255 IfCondition=MeasureMaxTemp40) & (MeasureMaxTempColor46) & (MeasureMaxTempColor60) & (MeasureMaxTempColor71

Rainmeter realtemp cpu temp skin