SilverAzide wrote: βMay 19th, 2023, 12:12 pm
Glad to hear you got it all working! It looks good!
![Thumbs Up :thumbup:](./images/smilies/ay.gif)
... CoreTemp is a nice lightweight utility to grab temps with, and the latest version now properly handles hybrid CPUs. HWiNFO is the usual go-to if you want to monitor more than temps, like GPUs, fans, hard drive temps, etc., but it's harder to configure and obviously a bit heavier on resource usage.
Thanks!... Yeah that was my thinking too generally TBH -- HWinfo is a great tool (especially for exploring the specs of a new system, or troubleshooting) and it detects/monitors more information about my system than I ever imagined... but it does take several seconds to load, where as CoreTemp takes <1 sec.
SilverAzide wrote: βMay 19th, 2023, 12:12 pm
To calculate the average temp across all the cores you'll need to have a CoreTemp measure for each physical core, as you've done (i.e., 6 measures)... You'll need 12 measures for your CPU usage, one for each logical core.
Ah, yeah I think you may be right!
Screenshot 2023-05-29 010518 -- Rainmeter over 100%.png
SilverAzide wrote: βMay 19th, 2023, 12:12 pm
This can get quite involved if you want your skin to run on a 64-core/128-thread AMD Threadripper, where you need hundreds of measures to get all the info. You can easily configure the measures to disable themselves if you have fewer cores than measures, so not all measures will need to be running.
OMG, threadrippers!... Yeah, that is insane!
Seriously, though, your last comment has just blown my mind slightly -- as in, for me - the fix was to copy and paste about 5 lines of code 12x, it's a bit annoying but not too bad!... But then if you're talking about people with threadrippers and other extreme core-count CPUs, and [Microsoft are] expecting them to write literally hundreds to thousand+ lines of code to fix their reporting, how does this make sense?.... Am not saying you're wrong, but I just can't help but think "surely this can NOT be thee right answer!?"
I know this is a little off-topic, but I was thinking through the stack / layers involved in reporting temp, usage and things, and came up with the below model...
Sensor_layers.jpg
I know it isn't perfect and some of the layers may be missing/wrong, but using this as a discussion point. Is is really the case that...
β’ Microsoft made a change in say "layer 3"
β’ This change then broke reporting for everyone else "down the chain"
β’ They didn't fix it
β’ The "fix" is for everyone else (i.e. end users) to individually fix their scripts / apps / monitoring tools!?
β’ That just seems messed up!
I appreciate that I have probably mis-understood something about the change, or what is going on "under the hood" -- and that's fine, am happy to be corrected and learn more about what has changed/broken, why, and the way(s) to fix it. But please can someone explain this to me?
You do not have the required permissions to view the files attached to this post.