A few things:
- the roundlines and colors work fine, like you can see if you temporarily comment out the relevant part of the bodies of the current measures and replace them with some basic incrementing Calc measures (notice how I forced MeasureRing to have a percentual value of 1 aka 360/360, and how the other 2 measures use the same values and update dividers to be in sync as I assume you want; the SkinWidth and SkinHeight are just a replacement of your skin being larger in this test sample, as are the X and Y in the 1st meter): - apparently, the GPU memory usage in the 2nd measure is not the same as the dedicated GPU memory usage by all processes in the 3rd measure; don't ask me why, just find the correct equivalent to the former in PerfMon.exe, if any, so that they both represent the same thing (if that's what you want, of course)
- like said earlier, if you wanted the 2nd and 3rd measure to represent the same thing, you should have made sure that they have the same value and are updated using the same update divider to be in sync
That being said, it's not exactly clear what you want to show. The MSI AB measure is fine, I use more or less the same in my skins, but the UsageMonitor one needs a bit of looking into it depending on what you want to represent there. And yeah, Windows doesn't make it easy for the user to identify which is which when it comes to some counters, although I'm pretty sure the math checks out if using the formulas they use (and which we can only guess).
- the roundlines and colors work fine, like you can see if you temporarily comment out the relevant part of the bodies of the current measures and replace them with some basic incrementing Calc measures (notice how I forced MeasureRing to have a percentual value of 1 aka 360/360, and how the other 2 measures use the same values and update dividers to be in sync as I assume you want; the SkinWidth and SkinHeight are just a replacement of your skin being larger in this test sample, as are the X and Y in the 1st meter):
- like said earlier, if you wanted the 2nd and 3rd measure to represent the same thing, you should have made sure that they have the same value and are updated using the same update divider to be in sync
That being said, it's not exactly clear what you want to show. The MSI AB measure is fine, I use more or less the same in my skins, but the UsageMonitor one needs a bit of looking into it depending on what you want to represent there. And yeah, Windows doesn't make it easy for the user to identify which is which when it comes to some counters, although I'm pretty sure the math checks out if using the formulas they use (and which we can only guess).
Statistics: Posted by Yincognito — Today, 2:15 pm