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. And nVidia has provided this data in their drivers. 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. I believe Intel integrated graphics also does not have the correct settings in HWiNFO to get a correct display for memory used. The nVidia settings should continue to work properly for nVidia cards. That does not show all the memory used, but that is as close as you will get for the Memory meter with AMD cards. Then choose the D3D Dedicated memory used HWiNFO sensor. Select the AMD box and type in the max memory your card has. 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. Make sure all information is correct for each sensor.Īfter 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, this seemed the best way to make sure everyone can enter the sensor IDs they have. I found on one of my GPU that HWiNFO placed a couple of sensors under a different SensorID. In the GPU settings skin, I provided the SensorID and Instance for each sensor EntryID. There are 1 minute time lines to help show when the data spike occurred. I only run this one when I want to see the last 4 minutes of data all in sync. Some may choose to use this instead of some of the other meters. I added this mostly for troubleshooting to save 4 minutes of data while I am using full screen programs. You only need to fill in what you plan on using.Īll-in-One meter. The other Temp skins will use however many cores you have. Meaning the skin with only 1 temp will only use Temp Core 0. Each CPU skin with temps will only use the fist of the temp Cores listed. You must already have HWiNFO installed and running before you can setup the IDs. Click the HWiNFO icon to start up the Shared Memory Viewer. Use the Settings skin to fill in the correct Temp sensor IDs for you system. Requires HWiNFO.ĬPUmemTemp2to1.ini - This is for most Intel processors that have 2 threads per Temp sensor. Requires HWiNFO.ĬPUmemTemp1nocores.ini - only displays 1 Temp, and no individual cores, only the Average CPU usage.ĬPUmemTemp1to1.ini - This is more for AMD processors that have 1 core per Temp sensor. The original no Temps, and 3 with Temp versions.ĬPUmem.ini - the original meter with no Temps, no CPU fan.ĬPUmemTemp1.ini - only displays 1 Temp, if you don't want to see every core. There are 4 variants of the CPUmem Meter. 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. Clicking on any Histogram will start up the Performance Resource monitor. There are several clickable locations on the meters. I'll fix any bugs as best I can, and I am trying to slow down on changes to this skin. This became way bigger that I thought it would, but they are all useful. I think I am just about done adding new things. At this time, they are simple but provide enough information so I can see if my system is running normally. These are Simple Performance monitoring meters (and a couple of extras) that I wanted for my own use. Just make sure to set some value in each Clock that you use. Not a big deal if you don't, the settings for each clock will not have default values. Since I added more clocks to the globalsettings.inc file, if you restore the previous version of the file, you may want to copy the Clock variables from the new globalsettings.inc to your restored file. SimplePerfMeters\ Resources\globalsettings.inc That should keep most all of your settings from before. 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. I needed to have my time and the TimeZone from a couple other parts of the world for work. I also added TimeZones and DST to the Clock, and add more clocks for a total of 4. I added this to help me troubleshoot issues in programs when I cannot look at the meters. UPDATE 2.3.0 - : 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |