Yes that is normal, to prevent Rainmeter from being blocked (aka doing nothing) while reading performance counters I just give Rainmeter empty data until the counters have updated, then on the next update of your skin it will read those counters now that they have been set up. These counters take a very long period of time to set up and update (EACH counter has an unavoidable ~100ms hit on EVERY update even on a decent CPU). So if no other skin is currently also reading that counter then it is going to take time to get everything set up and reading back data, this takes even longer to happen with GPU aliases due to us also needing to set up another counter so that we can translate the PIDs and Graphics Engine data into a human readable name. This is likely why that one is giving you issue due to it being a separate performance counter that has more work to set it up every time. Also GPU usage in from that data can seem odd like that, for example you will find even if you are GPU bound in a game that it likely will never hit 100% load. This is because frequently there are other things holding your FPS back besides raw compute such as memory transfer speed bottlenecks as well as some of that GPU cost that programs have is hidden in system apps that are frequently in blocklists like DWM, System, csrss, and several others that escape me at the moment.Yincognito wrote: ↑August 8th, 2020, 12:39 am By the way, is it normal to have those UsageMonitor values at 0 for a couple of moments when loading Rainmeter? I don't recall it happening before - although I could be very well mistaken, since the skin stayed a for long time showing the static value of CPU usage before these tests (the walkthrough the aliases is more of a feature than something I personally use). I do remember the skin showing numbers like 1 or 2 (as the name of the top process) at Rainmeter load though, in the past, so it might be just a part of the normal "initialization" process...
P.S. No errors so far.
EDIT: One other thing I wanted to ask: the GPU alias is always 0 when dynamically walking through aliases once every second, and when I pause it to show the GPU top processes, only Rainmeter with a little more than 1% GPU usage is shown. Is this normal? Could it be because my GPU card (AMD HD 7610M, 1GB DDR3) doesn't support hardware encoding and thus less programs use the GPU? Even so, Chrome should definitely use it and be quite high on it, since it's taking up quite a bit of CPU as well when it starts.
I would recommend maybe the instead of scrolling through aliases on one measure make a different measure for each alias you want to use and scroll through the measure that the meter reads from. This should avoid you needing to use DV=1 and you data will also likely be more recent than what you have now. This also may fix your GPU stuff being 0 and likely will have a more consistent if not also a little bit better performance than before as I built usage monitor to share as much CPU cost as possible between measures, even if they are in different skins so having multiple measure is not an issue