Shop Forum More Submit  Join Login
SimplePerfMeters 2.3.0 by TGonZ0 SimplePerfMeters 2.3.0 by TGonZ0
UPDATE 2.3.0 - 2015-04-12:  There is now an All-in-One meter that has CPU usage, RAM usage, PageFaults/sec, PageFile usage, Disk Bytes/sec, and Net IO in Bits or Bytes.  It show 4 minutes of data.  I added this to help me troubleshoot issues in programs when I cannot look at the meters.  I also added TimeZones and DST to the Clock, and add more clocks for a total of 4.  I needed to have my time and the TimeZone from a couple other parts of the world for work.

If upgrading from 2.2.0 to 2.3.0 and you want to keep your old settings files, backup these files and copy them back after you upgrade, and refresh all the skins.  That should keep most all of your settings from before.  Each GPU has it's own settings file.  Restore which ever ones you are using.
   SimplePerfMeters\ @ Resources\
   SimplePerfMeters\ @ Resources\

Since I added more clocks to the file, if you restore the previous version of the file, you may want to copy the Clock variables from the new to your restored file.  Not a big deal if you don't, the settings for each clock will not have default values.  Just make sure to set some value in each Clock that you use.

These are Simple Performance monitoring meters (and a couple of extras) that I wanted for my own use.  At this time, they are simple but provide enough information so I can see if my system is running normally.  I think I am just about done adding new things.  This became way bigger that I thought it would, but they are all useful.  I'll fix any bugs as best I can, and I am trying to slow down on changes to this skin.

There are several clickable locations on the meters. Clicking on any Histogram will start up the Performance Resource monitor. The idea is, you see a meter with high activity, click it to get quick access to the Resource monitor so you can investigate why it is happening.

There are 4 variants of the CPUmem Meter.  The original no Temps, and 3 with Temp versions.
CPUmem.ini - the original meter with no Temps, no CPU fan.
CPUmemTemp1.ini - only displays 1 Temp, if you don't want to see every core.  CPU fan rpm.  Requires HWiNFO.
CPUmemTemp1nocores.ini - only displays 1 Temp, and no individual cores, only the Average CPU usage.
CPUmemTemp1to1.ini - This is more for AMD processors that have 1 core per Temp sensor.  CPU fan rpm.  Requires HWiNFO.
CPUmemTemp2to1.ini - This is for most Intel processors that have 2 threads per Temp sensor.  CPU fan rpm.  Requires HWiNFO.

Use the Settings skin to fill in the correct Temp sensor IDs for you system.  Click the HWiNFO icon to start up the Shared Memory Viewer.  You must already have HWiNFO installed and running before you can setup the IDs.  Each CPU skin with temps will only use the fist of the temp Cores listed.  Meaning the skin with only 1 temp will only use Temp Core 0.  The other Temp skins will use however many cores you have.  You only need to fill in what you plan on using.

All-in-One meter.  I added this mostly for troubleshooting to save 4 minutes of data while I am using full screen programs.  Some may choose to use this instead of some of the other meters.  I only run this one when I want to see the last 4 minutes of data all in sync.  There are 1 minute time lines to help show when the data spike occurred.

GPU meter added.  In the GPU settings skin, I provided the SensorID and Instance for each sensor EntryID.  I found on one of my GPU that HWiNFO placed a couple of sensors under a different SensorID.  So, this seemed the best way to make sure everyone can enter the sensor IDs they have.  Make sure all information is correct for each sensor.

AMD GPU settings.
After researching the AMD GPU and HWiNFO and DirectX APIs, it seems like AMD and D3D APIs do not provide a good way to determine the accurate GPU memory total and used MB.  So, I added some new GPU settings that will allow you to get closer to a correct meter of memory used, not completely correct, but closer to being correct.  Select the AMD box and type in the max memory your card has.  Then choose the D3D Dedicated memory used HWiNFO sensor.  That does not show all the memory used, but that is as close as you will get for the Memory meter with AMD cards.
The nVidia settings should continue to work properly for nVidia cards.
I believe Intel integrated graphics also does not have the correct settings in HWiNFO to get a correct display for memory used.
So, it seems Intel and AMD did not add the extra memory data points in their drivers, so HWiNFO cannot get access to correct memory used.  And nVidia has provided this data in their drivers.

If you change the Temperature Units from C to F and back in HWiNFO, all the temps in all the skins will change with the appropriate Units.

I did my best to make Settings skins so you would not have to edit the file by hand. You can still do that if you like, but the Settings skins should be enough to make it all work.

Any issues getting HWiNFO to run on your system, please visit the HWiNFO site and check their forums for help.

All in One
  • click * in upper right corner to open the Settings to change scale of meters, now auto-hides
  • All meters display 4 minutes of data, with 1 minute marker lines
  • Uptime
  • CPU Usage
  • RAM usage
  • PageFaults/sec
  • PageFile usage
  • Disk Bytes/sec (Read and Write combine), currently C: only
  • Net IO (In and Out combine) Bits or Bytes follows the Network meter settings
  • scalable size
CPUmem Meter
  • click * in upper right corner to open the Settings to change scale of meters, now auto-hides
  • Histogram of average CPU usage
  • tooltip of CPU model when mouse over "CPU usage" string
  • Bars of average CPU and per thread CPU usage
  • CPU temperatures, 4 variants (no temps, only 1 core, 1 core per temp, 2 threads per temp) (req HWiNFO) *New*
  • CPU speed in MHz, it may change to show current speed, choose from PerfMon or from HWiNFO
  • CPU fan rpm, from HWiNFO, on variants with CPU temps
  • click CPU/TASK to start the Task Manager
  • click RAM/SYS to open the Control Panel -> System information page
  • click P/F to open the window where you can change your Page File
  • the CPU bar meters will automatically show only the number of CPUs you have up to 12
  • Memory size and usage, tooltip to show available mem
  • Pages/sec is when memory allocation went to disk, which slows the system
  • P/F Page File size and usage
  • scalable size

Simple Perf Meter Settings
  • click X in upper right corner to close 
  • click the bar to change the scaling factor from 1x to 2x in size
  • set Background Color for all meters
  • Sensor ID input for the Temperature readings
  • CPU fan Sensor IDs, with display on/off switch
  • CPU Mhz Sensor IDs, choose from HWiNFO or from PerfMon, red block = selected

Network Meter

  • click * in upper right corner to open the Network Settings, use this if your Internal IP display is not correct, now auto-hides
  • click Ext/Int IP address to open the Network and Sharing Center
  • Network Upload/Download graphs in Bits or Bytes
  • scalable size

Network Settings

  • click X in upper right corner to open to close
  • this will show up to 6 network interfaces and the IP address assigned to them
  • click the IP address to set that as the displayed Internal IP
  • Selectable Bits or Bytes

Disk Meter
  • click the Drive Letter to open a Windows Explorer to that drive
  • click the drive size to open the Restore Point configuration
  • click Percent Used number to open the Disk Cleanup utility to that drive, tooltip shows available space
  • the Center Yellow bar is also space used
  • Read/Write graphs in Bytes
  • Drive temperature from HWiNFO, can be turned on/off in the Disk settings 
  • scalable size

Disk Settings

  • click X in upper right corner to close
  • Type in any drive letter for each of the 8 disks
  • turn the temps on/off
  • enter the associated S.M.A.R.T. temperature sensor IDs to the correct Windows Drive letter

Clock Meter
  • click * in upper right corner to open the Clock Settings, auto-hides
  • You can now have 4 clocks running in different TimeZones
  • Time on top, with seconds as a thin bar just below the time
  • click Time to open the Windows clock settings
  • click Month to open a browser link to the current Month
  • click Year to open a browser link to the current Year
  • in 12 hour mode, the : will be bright for AM, and dim for PM
  • added Locale for Month and Day of Week, change in settings, "Local" will use your Windows Locale
  • scalable size

Clock Settings

  • click X in upper right corner to close
  • Each clock has it's own settings
  • TimeZone is only set by number offset from GMT, 0, -5, -9, 5.5, etc (sorry, that is how Rainmeter allows this)
  • If the TimeZone is set to Local, it will use your computers TimeZone and DST settings.
  • Label is only displayed (at the top) if you type something, anything you like, city, timezone, etc.
  • DST Daylight Savings Time on/off
  • Select 12 hour or 24 hour
  • Locale setting, Local, en-US, de-DE, fr-FR, it-IT, es-ES, etc.  It changes the Month and Day of Week.

Volume Meter
  • click the volume percent number at the top to open Windows sound settings
  • click anywhere on the volume bar to set volume 
  • scroll wheel also changes volume
  • click mute to toggle mute
  • scalable size

Weather Meter

  • click * in upper right corner to open the Weather Settings, auto-hides
  • click the Temperature to open the forecast
  • click the City name to open a web browser to that city at
  • click Radar to open a web browser to that city's radar at
  • data is from
  • scalable size

Weather Settings

  • click X in upper right corner to close
  • Standard / Metric
  • Web Update Rate, 300 seconds (5 minutes) seems to work pretty good
  • Locale setting, en_US, de_DE, fr_FR, it_IT, es_ES, etc.  It changes a couple of fields from the data stream.
  • type in your city, st, country and hit enter, click a new Location ID number to set it

GPU Meter
  • Requires HWiNFO running with Shared Memory access enabled
  • Up to 4 GPU meters
  • Display Graphics card model
  • GPU load and graph, also has Core Clock speed
  • GPU temperature and graph, also has Fan speed in rpm or % of operation
  • Temp graph is 0-100 C or 0-212 F.  Change C/F in HWiNFO settings.
  • GPU memory used and graph, and displays the total memory on the card

GPU Settings

  • HWiNFO needs to be installed and running first
  • HWiNFO icon to start up the Shared Memory Viewer to find the IDs for your system
  • Fill in the sensor ID information from the Shared Memory Viewer
  • Pick if you want Fan rpm or % of Fan operation to be displayed, or turn it off
  • Choose nVidia or AMD setting for GPU memory histogram

These HWiNFO sensors seem to work the best for nVidia and AMD cards, as noted below.

HWiNFO - GPU Memory Usage (%)   <-- use this for: GPU0 NV
HWiNFO - GPU D3D Usage (%)

HWiNFO - GPU Memory Allocated (MB)      <-- use this for: GPU0 NV
HWiNFO - GPU D3D Memory Dedicated (MB)    <-- use for: GPU0 AMD
HWiNFO - GPU D3D Memory Dynamic (MB)

On all Histogram meters, the number on the left is the current sample and the number on the right is the scale of the Histogram.

Internal IP address.  It seems the plugin that gets the Internal IP address works well most of the time.  If it does not, you can choose the IP from a list that your system currently has configured in the Network Settings.

Background color.  I set the default to black and is mostly transparent. (0,0,0,100)  That way some color from your wallpaper would show through.  If you have a very light or very dark wallpaper, and want a more solid color similar to the blue in my cover image, try using 0,50,100,240.  That works good with all the other colors I used in the skins.

FYI, I made these on my Windows 7 system, and I've been told by others that it works well in Windows 10.

UPDATE 2.3.0 - 2015-04-12:  There is now an All-in-One meter that has CPU usage, RAM usage, PageFaults/sec, PageFile usage, Disk Bytes/sec, and Net IO in Bits or Bytes.  It show 4 minutes of data.  I added this to help me troubleshoot issues in programs when I cannot look at the meters.  I also added TimeZones and DST to the Clock, and add more clocks for a total of 4.  I needed to have my time and the TimeZone from a couple other parts of the world for work.
UPDATE 2.2.0 - 2015-12-03:  Added more GPU meters, up to 4 now.  Added on/off switch for GPU fan display.  Fixed divide by 0 error some were getting in the GPU max memory calculation.  Added a CPU meter with only the Average and no cores, if you want a simpler look.
UPDATE 2.1.0 - 2015-10-09:  Changed Disk Meters so you can type any drive letter for any of the 8 disk meters in the Disk Settings skin.  In doing this, I changed many variable names to make it more consistent, so if you save your old config files, you will need to re-enter the settings for the Disks.   Change the labels in the GPU settings skin to match what is in the HWiNFO for the memory settings.
UPDATE 2.0.7 - 2015-09-23:  Added GPU settings to help AMD graphics cards get a better result on the GPU meter for memory.  See below for explanation.  Made Weather Forecast toggle quicker. Added network external IP hide setting.  Sometimes I screen share and wanted to hide my external IP.  Fixed Disk available MB tooltip calculation.  I hope this update will be it for a while.  If you copy the and files from 2.0.5, just make sure you click and fill in the new options in Network Settings and GPU settings.
UPDATE 2.0.5 - 2015-09-20:  Only a couple of minor visual changes, I moved the CPU fan display, now the CPU/GPU/Disk temps will display correctly when you change from C to F and back in HWiNFO.  I consolidated all settings for all skins to the file, and all HWiNFO settings for all skins to the file.  So, after installing this version, you can save these 2 files, upgrade to future versions, and restore these 2 files and all meter settings and HWiNFO settings will return.  I had them in several different files before, making this process more difficult.  I'll do my best to keep only these 2 files going forward to make restoring your settings easier.  Cleaned up the code and modulerized the CPUmem skins and variants to make changes to them easier.
UPDATE 2.0.2 - 2015-09-08:  Sorry, I found a couple more bugs in the new Disk Settings skin where you could not enter IDs.  All fixed now.  I hope that's it.
UPDATE 2.0.1 - 2015-09-08:  Oops, missed the Disk temps on D: and H:, now fixed.
UPDATE 2.0.0 - 2015-09-07:  added Disk temps and a settings skin to enter the sensor IDs and turn them on/off, cleaned up some code and settings files for other skins.
UPDATE 1.9.5 - 2015-09-07:  added on/off switch for the CPU fan
UPDATE 1.9.4 - 2015-09-06:  as requested, added CPU fan, added CPU Mhz by HWiNFO or PerfMon, settings * now auto hide, added a few tooltips for more information.  Okay, I think I have added enough to these skins for awhile.  The settings skins are starting to get out of control. :-)  Enjoy.
Add a Comment:
Brjck Featured By Owner Sep 18, 2018
Was looking thru for hours and I found you! This is my perfect skin thanks for making it!
Acidinmyfridge Featured By Owner Jul 27, 2018
wow, you put all together in one. This is some neat and handy skin. Thank you so much for this! :D
thunderbolt61 Featured By Owner Dec 21, 2017
im having some problems with pagefile sec. not showing propper numbers, always 0 pf/sec
riki59 Featured By Owner Oct 6, 2017
Merci cela va m'etre tres pratique , c,est un tres beau skin merci!
benzite Featured By Owner Jun 27, 2017
I can not believe that I just discovered this awesome skin.
I noticed you added scaling to some of the features but not the others such as GPU and Time Zone.
Is there a way a noob like me can do this manually or is this a feature you are working on for a future update.

Tanks again
KAMKillJoy Featured By Owner May 8, 2017
How about sound visualizer? Realy like your design.
thunderbolt61 Featured By Owner Mar 12, 2017
There is a bug in cpumem, P/F(page file) not show correctly. in concrete i have the "cpumemtemp1to1"
Prophet4NO1 Featured By Owner Edited Dec 2, 2016
I have been using this for a while and really like it!  Is there a way to get an added feature though?  A PSU meter?  I have a Corsair AX1200i hooked up via USB for Corsair Link.  Turns out HWinfo detects it as well.  I would love to see power in/out, efficancy (if doable), temp, and fan.  Or at least power in at a minimum.  Thanks.  
alpha736 Featured By Owner Aug 28, 2016  Hobbyist General Artist
Is there a way I can get this to work better with a dual socket motherboard/dual CPUs?  I have an X8DTi-F motherboard with two Xeon E5645.  Two Hex-core CPUs with Hyper-Threading, 12 threads/cpu, 24 threads total.  Windows sees this as 24 CPU cores.
willis936 Featured By Owner Edited Apr 10, 2018
I did this manually last night.  It's pretty labor intensive.  Rather than make proper fixes I just hard coded new stuff.  In the 2to1 you need to basically double everything.  Identifying the numbers that need to be incremented is a pain.  I made a matlab script to make the larger parts that needed to be added and did the rest by hand.  I then copied the CPUmem folder over and changed the instance reference from the perfmeter variable to 0x1.

There's another limitation I ran into though which is that rainmeter's cpu measure isn't well documented and certainly was not designed with multiple CPU systems in mind.  Specifically there is no "per CPU, average core usage", only "total CPU average core usage".  I'm currently updating the CPU usage meters to use HWINFO instead.

EDIT: I just got it working.  The big gotcha was I didn't know that "MinValue" and "MaxValue" had to be set manually with the HWINFO measures.  They are implicitly set with the built in rainmeter cpu measure.  I'd be happy to share my hacked rmskin if the author is okay with it.
alpha736 Featured By Owner Nov 15, 2018  Hobbyist General Artist
I'd love to get a copy of that if you still have it.
H3ll1um Featured By Owner Jul 29, 2016
yayy !! niceee but, where is the download button ?
H3ll1um Featured By Owner Jul 29, 2016
where is the download link ?
nickglott Featured By Owner Jul 10, 2016
TGonZO amazing job I love your work. Is there any way way could add another CPU fan, Possibly 2? One would be for my water pump RPMs. I have been tinkering and trying to find out how to add more. Another widget for fans would probably be the best thing. I want to monitor my 2CPU fans, CPU waterpump and 4 case fans from a widget. They all show up in shared Memory viewer just need the code. :(
nickglott Featured By Owner Jul 11, 2016
Figured that out, was not to difficult. I am now working on a FAN skin to put all fans and system temps on. I am trying to use the GPU one as a base as I would like to have a graph of the fans RPM's. I am no coder so it may take a while hahaha. You have some good code though I having trouble figuring out the graphs.
Rubez2525 Featured By Owner Jun 23, 2016  Hobbyist Digital Artist
I have a suggestion if you want something to add. Have you considered putting in PSU monitoring? Some newer PSUs allow you to monitor stuff like power and temp, and those sensors are visible in HWiNFO.
11Hz Featured By Owner Jun 15, 2016  Hobbyist Digital Artist
Great work!!:happybounce: 

Thanks to make this skin.
mesh24 Featured By Owner Apr 28, 2016  Hobbyist Digital Artist
This is probably the best most thought out skin for rainmeter period. After using this I'm finally able to ditch Core Temp and Afterburner and use HWinfo64 exclusively! Even works/looks great on my 2K monitor since it has scaling abilities built in.
adremides Featured By Owner Apr 19, 2016
Thank you very much for sharing this! This was my first replacement for windows 7 gadgets in Windows 10 :)
Exper1mental Featured By Owner Apr 15, 2016  Hobbyist General Artist
Just FYI you need to update the version of HWiNFO you are using, there is a newer version available ;)
TGonZ0 Featured By Owner Apr 15, 2016
Will do.  I guess I have not checked on that in a while.  Thanks.
TmrGast Featured By Owner Apr 13, 2016  Hobbyist General Artist
Damn, this is exactly what I was looking for, the HWinfo plugin allows for a lot more on screen information than most other hardware plugin do. And the great simplistic style of art fits right into my other desktop meters!
TGonZ0 Featured By Owner Apr 14, 2016
Thanks, glad you like them.
FailBail Featured By Owner Mar 25, 2016
Hey, great skin!

I notice there's no place to monitor case fans, would this be easy to add myself or might you be able to add it in the future?

Otherwise keep up the great work!
TGonZ0 Featured By Owner Apr 14, 2016
Thanks.  I'll look into more fans.  Not sure how I will do it yet.  Maybe a new meter.  We'll see.
DarkDarwin Featured By Owner Feb 22, 2016
Thank you so much.Love 2.0.
Excellent clean precise work.
TGonZ0 Featured By Owner Apr 14, 2016
Thanks for the nice comments.  I also wanted simple clean meters and decided to just make what I wanted.
AzzaNancazza Featured By Owner Dec 18, 2015
Great skin! Just finished getting it all set up, and am very happy.

Quick question (read: request) - is it possible to add in another volume meter w/mute option for microphone?
TGonZ0 Featured By Owner Dec 22, 2015
Thanks, I'm glad you like it.  For now, there is not a good way to control the mic from Rainmeter.  I've looked around a bit, and have not found anything yet.  If a plugin is created that can control the mic, I can look into it then.
Exper1mental Featured By Owner Edited Feb 18, 2016  Hobbyist General Artist
If your interested you actually should be able to control the mic with Rainmeter using either AutoHotKey (AHK) scripts or NirCmd.

Here's a simple AHK script someone posted on GitHub that toggles muting/unmuting the mic:…

You should be able to use the AHK SoundGet command to return the mic volume and the SoundSet command to change the mic volume.

If AHK doesn't work NirCmd is probably your best shot with it's changesysvolumesetsysvolume and mutesysvolume commands.

Bear in mind that in instances where multiple mics are being used the end-user will most-likely need to be able select which mic to control, further complicating things. Controlling the mic probably isn't worth all the effect needed to integrate control with Rainmeter but I thought I'd toss this out there anyway.

Side note
You may want to update the version of the HWiNFO plugin you include with the skin, I've the old one may not run correctly in some instances on Rainmeter 3.3
AzzaNancazza Featured By Owner Dec 24, 2015
Oh ok, no worries - thanks for looking into it anyways :)
Emperorr Featured By Owner Dec 2, 2015   Photographer
REALLY good skin, but I can't believe there isn't an option to show more than one GPU...It has EVERYTHING but that...
TGonZ0 Featured By Owner Edited Dec 4, 2015
Hi Emperorr,  Well, now it has everything.  lol.  I added more GPU meters so you can have up to 4 running, each with their own settings window.  Enjoy.
Emperorr Featured By Owner Dec 21, 2015   Photographer
That was QUICK!

You're the man dude, love the meters!
TGonZ0 Featured By Owner Dec 2, 2015
Thanks.  I did write most of the GPU skin with GPU0 in most all the variables and measure/meter names, but not all.  So, I should be able to fix that, and add a 2nd GPU skin without a huge effort.  I'll look into that real soon.
Rubez2525 Featured By Owner Oct 7, 2015  Hobbyist Digital Artist
How do you configure temperature settings for drives NOT in C-H (2.0.7)? I don't see any obvious ways to add them to diskconfig.ini
TGonZ0 Featured By Owner Edited Oct 8, 2015
Hi, I'm not sure I completely understand your question.  Did you create more Disk meters above H, and are now trying to add Temps to the Meters above H?  And you would like to add Drive temps above H to the Diskconfig.ini skin?  If so, it's not easy. Sorry.  I can probably clean up that skin, so it is easier to add more Disk temps.  What is the highest Drive letter you are using?

Let me know what you mean, and I'm sure we can work it out.
Rubez2525 Featured By Owner Edited Oct 8, 2015  Hobbyist Digital Artist
Yes, that is pretty much what I mean. Adding the drive meters themselves are easy with the way you have it set up, but adding the temperatures to them through "Disk HWiNFO Settings" window (aka diskconfig.ini) is hard since it is still only C-H in the settings. I have disks B and W. I do see the fields like [measureInputCdriveTempEntry], etc. But I am not sure if copying and pasting and changing the letters will add them in nor do I know exactly all the things that need to be added to get the temp to work for added disks.

It may be too much to ask: But I suggest just simply including every letter in the alphabet by default. They could be organized into a single DiskMeter folder and have each one labeled something like [insert letter]diskmeter.ini. Obviously, I don't know how much work that would be for you or if it would break with the way you have it set up, but at least that system should work with anyone's hard drive setup.

On the topic of disks: This is a very minor issue/bug, but whenever there is no read/write values on the histogram, the maximum values (ones on the right) display "2" instead of "O B" like on the current read/write values (ones on the left). This is actually seen on your preview here with the idle disks. I just thought I mention it if you are still looking for bug reports.
TGonZ0 Featured By Owner Edited Oct 8, 2015
To make it a bit easier to add other drive letters, I am changing the Disk Settings skin and putting the code that creates each line into it's own file, and then including that.  It should be much easier to copy a the file to a new letter and add another include line.  Then do change the drive letter in that new file.  I'm still thinking about some other ideas though.

I like the idea of using variants for additional drive letters, but I am also thinking of trying to add a field to just type the drive letter you want for each Disk meter.  I'm not sure how each of these ideas will look and work in practice, but I think I can do something different to make them more configurable and still easy to setup.  I've tried really hard to make these as easy to configure as I can.

In the Disk Histograms, the number on the right is the max value of the Histogram at that moment.  Rainmeter is designed so that Histograms always display a minimum of 0-2.  So the max value will never be below 2.  That's just how Rainmeter works.  So when there is no activity (all values are 0) then the max possible value of the histogram display will still be 2.

You can add the Temps for your B and W drives yourself, manually, without using the Disk Settings skin if you wish.  You will have to edit 2 settings files for variables.

1.  edit  Rainmeter\skins\SimplePerMeters\resources\  file
Scroll to the bottom, and copy the 3 variables from another drive, change the drive letter in the new variables, and set the parameters for each.

2.  edit  Rainmeter\skins\SimplePerMeters\resources\  file
Find the C:driveTempOnOff=0  settings, copy it and change the driver letter to your new drives.
0 = On
1 = Off

With those changes the Temps should show up on a refresh of the skin.
This manual method should be easier than you trying to edit the Disk Settings skin.  And you will have temps until I can work out a better way.

Hope that helps for now. 
Rubez2525 Featured By Owner Edited Oct 8, 2015  Hobbyist Digital Artist
Ok cool. By the way, I did mod in a fix that does mask the "2" on the histogram. I just made a simple IF statement:

  if HistMax == 2 then
    HistMax = 0

I just glued it into FindMaxHistValue.lua right before "return HistMax". So there is at least a way to cover it up.
TGonZ0 Featured By Owner Edited Oct 8, 2015
You can make that change for yourself if you like.  
But the smallest Max value of 2 is correct, the histogram height represents 0-2 for data values when all data points are 0.  The number on the Left is the current new data value, where the number on the right is what the histogram max is set to from auto scaling, smallest value being 2.

I have decided to go with a text field to type in the drive letter you want for each of the 6 drive meters.  That way you can have any 6 drive letters you like.  I have it working on my system, but I still have to clean up some code a bit, and test it out a bit more.

keep an eye out for a new version soon.
Rubez2525 Featured By Owner Edited Oct 9, 2015  Hobbyist Digital Artist
Ok, neat. I will look out for it. For the change to the histogram: I think it would be more accurate to display the actual max read/write values shown on the histogram rather than the smallest scale on the histogram allowable by Rainmeter. I don't know, that is just my reasoning for changing it. As long as you are aware of it and it is not a bug, then that is fine.
TGonZ0 Featured By Owner Edited Oct 9, 2015
I'll try to explain the numbers I put on the histograms, there is no bug, it is all working properly.

The value on the Left side is the data value that was just added to the histogram.  This number on the left should be constantly changing as the incoming data changes.  I think this is what you are looking for.  Examples:
R 0 B = Read zero Bytes
R 96 kB = Read 98,304 Bytes
W 237 kB = Write 242,688 Bytes

I am using the Auto-Scale feature of the Histogram meter.  When the Auto-Scale is used, the histogram will change the range of data values being displayed based on the largest data value in the current Histogram display.

So, it would be a scale of 0-2 when all data is 0 (idle disk).  Number in the right of the histogram is 2.  The Number on the left will be R 0 B.

When disk activity happens and a Read of say 14530 bytes/sec occurs, (number on left will be "R 14 kB" for one second) the Histogram will change the scale to display data ranging from 0 - 16384, or 0 - 16k.  Then the number in the right of the histogram is 16k, and will remain 16k until the data value of 14530 slowly slides off to the left and disappears from the histogram.  At that time, a new max will be calculated for the number on the right.

I hope that helps.
(1 Reply)
voodoo-curse Featured By Owner Sep 11, 2015
Everything works great, but I'm having trouble setting up the GPU meter properly. What sensors should we actually be using for MemUseMB and MemUsePercent? I've tried using GPU D3D Memory Dedicated/Dynamic, GPU D3D Usage, and GPU Memory Controller Utilization, but it's giving me wildly inaccurate values. As I type this, it seems to think I have 41GB of RAM on my R7 260x.
MarcusCorbacho Featured By Owner Sep 20, 2015

These are my Configurations. Unfortunately the AMD sensors not match the NVIDIA, but is ok. On % just select the D3D Usage because is on % on HwInfo...

PS. Keep working on the these. Excellent !
voodoo-curse Featured By Owner Sep 24, 2015
That certainly gets closer to an accurate reading, thanks
TGonZ0 Featured By Owner Edited Sep 20, 2015
If you could show me the details from HWiNFO and GPU-Z for the AMD GPU, I would like to understand what info is available.  Maybe I can make a change to help the AMD display the Memory better.
Here is an example of my system of what I would like to see from your system.  And tell me how much memory your GPU has.  Thanks.

(I use "GPU Memory Usage, %" and "GPU Memory Allocated, MB")
TGonZ0 Featured By Owner Sep 12, 2015
Yeah, getting the correct sensors can sometimes be a bit tricky.  I'll explain as best I can, what I'm using with my GeForce GTX970.    I see you have a R7, but hopefully you have equivalent entries to choose from.

I calculate the Max installed Memory on the card based on the Mem Used in MB and the Mem Used in %.  As you see, if these are not correct, it will not calculate correctly.

On my card, I see 2 entries for getting the % used.
GPU Memory Usage (%)   <-- I use this one.
GPU D3D Usage (%)

As I understand these 2 settings, the D3D is always less because it only shows what GPU memory is allocated for D3D operations.  Where the GPU Memory Usage show all GPU memory allocated as a %.  Use the GPU Memory Usage (%) for the GPU0 MemUsePercent.

Next for the MB sensor I see 3 possible entries.
GPU Memory Allocated (MB)      <-- I use this one.
GPU D3D Memory Dedicated (MB)
GPU D3D Memory Dynamic (MB)

Again, the D3D are only showing a smaller usage of only what the D3D is using.  The GPU Memory Allocated show the total about used in MB.  Use the GPU Memory Allocated for the GPU0 MemUseMB.

So, as best I can tell, you do not use any of the D3D sensors.
Hopefully your ATI/AMD R7 has similar sensor entries as mine does to choose from.

Hope that helps.
voodoo-curse Featured By Owner Sep 24, 2015
I see. Unfortunately my card does not have a "GPU Memory Allocated" sensor value.

I plan to replace it with an Nvidia card soon anyway, so hopefully this is only a temporary issue.
Add a Comment:


Submitted on
July 12, 2015
File Size
877 KB


113,293 (53 today)
226 (who?)
33,372 (13 today)