As reported here in more detail (and with the RTSS author's sort of reply): https://forums.guru3d.com/threads/help-request-frametime-displays-wrong-value-when-capped-with-rtss-but-not-the-driver-limiter.443730/#post-6031941, the Frametime value imported from RTSS displays the incorrect value...
In this image, I would love to be able to have the "CPU:" / "GPU:" / "RAM:" / "FPS:" labels be a different color from the actual percentage/mhz/temp values, but at this time it doesn't seem like this is possible.
For further context, I'm referring to these custom labels you can make here -- I'd...
Going off of this thread here: https://forums.guru3d.com/threads/does-hardware-polling-software-like-rtss-hwinfo64-have-a-discernible-impact-on-performance.443665/#post-6030426
It sounds like you don’t really want to run sensors you’re not using as they can take up a bit of CPU time.
I only...
I have an Nvidia 2080 Super -- I finally figured out what was going on. At first I thought it was when I updated HWiNFO64 that caused the decimal digit to reset, but it's actually whenever the GPU Driver itself gets updated.
I use the GPU Temp field in my custom overlay, but whenever the gpu...
To get around this I've had to create a custom startup task for both RTSS and HWiNFO64 so that RTSS always starts before HWiNFO64. It would be nice if this wasn't necessary.
For example, if HWiNFO64 periodically checked for RTSS when RTSS FPS/Frame Time values are used in the OSD, something in...
HWiNFO UI -> gear icon -> custom tab -> RTSS -> Framerate -> Unit section (top right).
In the past/prior updates I could rename this to whatever I wanted (e.g. change FPS to F or / or whatever) -- I would just type it in under the Unit heading and hit Rename.
After the latest update this no...