Quantcast
Channel: Rainmeter Forums
Viewing all articles
Browse latest Browse all 482

Usage Monitor Plug-in and Roundlines/Dedicated GPU Process Memory Usage/Having Trouble With the Values.

$
0
0
I took it upon myself to create one of the most accurate MSI Afterburner GPU skins, after what I thought was a completed skin I realized there was something wrong with the Category and Counter I was using for the Memory Usage, Memory Clock and Core CLock, so I changed them to the correct ones, which are, "Category=GPU Process Memory and "Counter=Dedicated Usage but now the roundlines don't work as they should when running a game. I'm aware we can never get a 100% true accurate measure when working with MSI Afterburner and Rainmeter but I believe we can get as close as possible and from what my research as gathered there is none, anywhere. If there is a fully loaded MSI GPU skin I'm unaware of it and wouldn't mind knowing where it is so I can use it as a sample learning tool.

SIDENOTE: I had CoPilot help me three times editing some code and all three times it got it wrong but we worked it out and got it right. Point Is; AI will not get the Rainmeter code right the first time.

I'm aware that not everyone has the same GPU and if need be I will add settings so the end user's card RAM size and any other values (such as SourceID numbers) needed to be entered by the end user will be available so the measures will be as accurate as possible.

(when working with GPU Process Memory I'm not sure of the values I should enter, so I did what I think should be entered. MaxV is the total amount of memory the GPU has, in this case, mine is 2GB -250MB memory used the color should be 75,216,19, above 250MB and lower than 500MB the color should turn to 247,138,5, and between 1Gb and 1Gb the color should turn 247,180,5, above 1GB and MaxV the color should turn to 247,17,5 but the roundline colors don't fluctuate the colors when I'm playing a game. The roundline color stays at 0,200,0. Not to mention I'm still have problems with the other roundlines and their values changing colors too. All the measures, SourceID and meters -I believe- are correct, all the Categories and Counters are correct as well. My best guess as to what the issue is, its in the IfCondition(s) value and the IfTrueAction(s) values).

One more thing I should add: I know the organization of the code in the document "Extended GPU Data (MSI).inc" isn't Ideal so I plan on re-arranging it.

Image

Code:

[GPU0MemoryUsage]Measure=PluginPlugin=MSIAfterburner.dllGPU=0SourceId=49UpdateDivider=2MinValue=0MaxValue=#MaxV#[GPU0Roundline3]Meter=ROUNDLINEMeasureName=MeasureRingLineColor=255,216,0,100LineWidth=6.0LineLength=55LineStart=50X=395rY=0rAntiAlias=1Solid=1Group=Details[GPU0MemUsage]Meter=ROUNDLINEMeasureName=GPU0MemoryUsageLineColor=184,32,15LineWidth=6.0LineLength=55LineStart=50StartAngle=(Rad (270))RotationAngle=(Rad (360))X=0rY=0rAntiAlias=1Solid=1Group=Details[mGPU0MU]Measure=PluginPlugin=UsageMonitorCategory=GPU Process MemoryCounter=Dedicated UsageIndex=0IfCondition=(mGPU0MU < 250)IfTrueAction=[!SetOption GPU0MemUsage LineColor "75,216,19"]IfCondition2=(mGPU0MU >= 250) && (mGPU0MU < 500)IfTrueAction2=[!SetOption GPU0MemUsage LineColor "247,138,5"]IfCondition3=(mGPU0MU >= 1024) && (mGPU0MU < 1024)IfTrueAction3=[!SetOption GPU0MemUsage LineColor "247,180,5"]IfCondition4=(mGPU0MU >= 1024) && (mGPU0MU < #MaxV#)IfTrueAction4=[!SetOption GPU0MemUsage LineColor "247,17,5"]
MSI GPU_SampleTest_1.rmskin

Statistics: Posted by Thinkr8 — July 10th, 2024, 11:06 am — Replies 22 — Views 2300



Viewing all articles
Browse latest Browse all 482

Trending Articles