Search results

That is what I thought, it's all rather confusing. Perhaps I'm misunderstanding Unwinder's replies (going off his most recent comment that may be the case), but he seems to think the issue is that the frametimes are being read by another application which is misrepresenting the data perhaps? Or...

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...

Sadly I did retest this several times on a new PC and it does seem that when I do a clean install of a new GPU driver or if I use DDU to uninstall the driver entirely then reinstall the GPU temperature decimal place value gets reset each time to 1 from 0. When the next GPU driver update rolls...

Thank you very much, this is everything I needed to know, much appreciated!

Thank you again for your replay that really helped me out -- by default I see the global poling period is set to 2000 ms / 100 cycles / emb controller 1 cycle. Does this mean that for most sensors (cpu temp / usage / ram usage / gpu vram usage and frequency, etc) that they are polled every 2...

Thank you very much, that’s helpful!

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...

Thank you very much, that’s helpful!

I'd like to show the FPS, Frametime, and 1% low values if possible in the HWiNFO64+RTSS overlay, but I'm not sure if this is possible. Thanks!

Thanks that's good to know! In that case should I just close HWiNFO when I update my GPU driver? Or do you think this is fixable on the HWiNFO end? No worries either way, thanks for your help and time.

When I closed HWiNFO then did a clean install of the latest driver the GPU Temperature Decimal value did NOT reset to 1. I did the following: 1) Closed HWiNFO from the system tray 2) Opened GeForce Experience and reinstalled the latest driver (clean install) 3) After it completed I reopened...

I will try that out and get back to you soon. Good idea

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...

@Martin Just an update, I think I may have narrowed further what causes the GPU Temp to reset its decimal place precision -- I did not update HWiNFO this time (as a stable build has not yet released since I made this original post), but I just did a clean install of Nvidia's latest GPU driver...

HWiNFO -> OSD (RTSS) -> "GPU Temperature" I modify the decimal precision under the "Custom" tab -> Decimal digits here: (set to 0) I perform the update always using the exe installer found here: https://www.hwinfo.com/download/ Thanks for your time, sorry to spam you. You do great work mate...

Thank you very much, my apologies. As an aside I did notice one other issue that only occcurs when I update HWiNFO — I have a custom overlay where I change the decimal precision of GPU and CPU temps to just be rounded off to the closest whole number (e.g. 73.4 would display as 73, etc)...

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...