SilverAzide wrote: ↑March 14th, 2023, 7:55 pm
This is known behavior. It actually changed in Win 11 22H2; it was OK in earlier versions of Windows 11.
In summary, the old CPU measure and the UsageMonitor with the CPU alias no longer work as they used to. You will need to change any of these measures as mentioned in my posts to use the utility-based counters instead of time-based counters.
The bad news is that -- so far -- there is no way I know of to fix the "top process" type measures because these are all based on CPU time, not CPU utility. As a result, the measures return data that is not the same as what you saw before.
Well, I've been fiddling with some of the code from the skins of my suite recently, and I discovered this:
Code: Select all
[Variables]
[Rainmeter]
Update=1000
DynamicWindowSize=1
AccurateText=1
BackgroundMode=2
SolidColor=47,47,47,255
---Measures---
[RainmeterCPUAlias]
Measure=Plugin
Plugin=UsageMonitor
Alias=CPU
Name=Rainmeter
[RainmeterCPUCounter]
Measure=Plugin
Plugin=UsageMonitor
Category=Process
Counter=% Processor Time
Name=Rainmeter
---Meters---
[Results]
Meter=String
FontFace=Consolas
FontColor=255,255,255,255
Padding=5,5,5,5
FontSize=16
AntiAlias=1
Text="Rainmeter CPU Usage (Alias) = [RainmeterCPUAlias:]#CRLF#Rainmeter CPU Usage (Counter) = [RainmeterCPUCounter:]"
DynamicVariables=1
Alias vs Counter.jpg
Mind you, this is on Windows 10, not Windows 11. The question is, unless I'm missing the obvious here, shouldn't these two forms of getting the CPU usage of a process return the same value, since, according to
the manual, the
Alias=CPU is just another way of writing
Category=Process and
Counter=% Processor Time for the said process? I mean, the difference is too significant to be caused by (hypothetical) different moments of getting the data, and at least
one such comparison in the past (not sure what the code was, but the "by alias" vs "by counter" lines in the screenshot are self explanatory) seemed to yield the same values...
So, what am I missing (if I'm missing something, that is)? Is it a bug? Can this be used to "correct" the lower CPU usage of processes on Windows 11, if by any chance those lower values were caused by using the alias and not the plain counter? SilverAzide, you dealt with such things in your suite, both on Win 10 and Win 11, so what do you think about it? Did you notice this?
Everyone else, can you replicate this? If so, what are your thoughts about it?
P.S. The funny thing is that, while PerfMon.msc presents the (higher) counter value, the Win 10 Task Manager seems to prefer the (lower) alias one. Maybe in Win 11 its Task Manager finally presents the former instead?
You do not have the required permissions to view the files attached to this post.
You have an omission in your