Help: Rainmeter Skins • Re: Usage Monitor Plug-in and Roundlines/Dedicated GPU Process Memory Usage/Having Trouble With the Values.

I still don't understand what advice you're giving me. I know what the advice is, I just know how this is related to my question which was; the roundlines aren't changing colors as they should with the assigned values when I play a game. In the screenshot above the Memory Usage says "460.2MB" but the roundline is green, it should be yellow. And memory clock and core clock act the same way, the colors don't change when gaming.

It's un-clear to me as to what is needed to have it work correctly.

Well, I already explained that part in my first reply, but I'll be even more precise this time: your [GPU0MemUsage] and [mMemoryUsage] meters from Extended GPU Data (MSI).inc are based on the [GPU0MemoryUsage] measure value to display data (i.e. the total memory usage for GPU 0). By comparison, setting the colors in your [mGPU0MU] measure is based on the [mGPU0MU] measure value (i.e. the GPU Process Memory > Dedicated Usage for all processes, which is for all video cards in the system). In short, there are 2 problems:
- the value of [mGPU0MU] is different than the value of [GPU0MemoryUsage] (this is how my 2nd reply / screenshot relates to your question)
- the value of [mGPU0MU] is not scaled properly in the comparison (mGPU0MU is in bytes, and the numbers you used are megabytes)
So, in code, you'd need something like:to scale mGPU0MU to the unit used for the 250 and 500 numbers, but even so, mGPU0MU will be different and bigger than GPU0MemoryUsage, the latter of which is displayed in your skin as "460.2MB" and as a roundline, because mGPU0MU is the sum of the dedicated memory usage for all processes on all GPUs. I have no idea which of them is what you want to use, I'm just saying they're different and if you use the UsageMonitor value that needs to be scaled for the IfConditions to work.

After further thought I think this is a futile attempt because any GPU skin working with MSI will never be the same on someone else's system.
Each end user of any GPU MSI would have to do some manually configuring and I was going to make an attempt to try and avoid that for the end user but I may have took on more than my knowledge will allow. So thanks. And this forum takes more work than I like in order to be understood properly.

Not quite. Unlike the old HWiNFO way of getting data using the Shared Memory Viewer (which indeed required user / system specific configuration), MSI AB has a consistent syntax for the MSI AB plugin measure options, irrespective of system (I'm talking about the syntax of options like SourceId, DataSource, GPUDescriptor, etc). If you're talking about configuring how much memory the GPU has or similar, you can already get that using wmic (which is a bit obsolete by now) or PowerShell's Get-CimInstance from a RunCommand measure, similar to how you did in your R1 and R2 measures.

Statistics: Posted by Yincognito — Yesterday, 6:53 pm

---