I did have one more issue in v7.16.
My MAX DIMM temperature custom sensor wasn't working. Not a bug, but you renamed the DIMM temperatures to include the bank and channel information so they no longer worked.
I just renamed them to the old names and it works fine.
Only the operations I listed.
If you do play with it, keep this in mind:
1. The names of the sensors you use in a custom user sensor must be those that are displayed in the HWInfo sensor display. So if you have renamed a sensor you must use its new name.
2. The sensors used in the custom...
You set it up in the Windows registry. For example, here are some of my custom sensors:
The Ambient In is the average of two temperature probes at my intake. The Average core temperature is "instantaneous" average across all cores. The registry entries are:
No. There are physical sensors and derived custom sensors. Custom sensors can be created in the windows registry as new sensors that are mathematical manipulations of physical sensors or other custom sensors. You can do simple operations of addition, subtraction, division and MIN and MAX on a...
These quasi-static values are already displayed in the GUI but are not avaialble as sensors. They would be useful in creating some custom sensors such as the actual VID requested of the VRM (Actual VID = VID sensor + DCLL * current)
That looks great! Thanks for all of the hard work, I know the dark mode must be a real pain -I used to develop software at many levels, thankfully on Linux and not windows :D . This is the most useful utility I must say!
Thanks for putting all the effort in the dark mode. I have some feedback:
1. Ability to enable or disable it
2. The white lines and boxes around every item is distracting and makes it hard to read the values. I would loose them. Alternate row shading should be sufficient.