RTSS and PresentMon

[electricnic]

Two issues, not sure if they're related:

HWiNFO polling RTSS (standalone, not with MSI Afterburner) is limited to 1000ms, even if the rest of HWiNFO is set to 500ms. Every other sample greys out, but as of v7.63-5215, the greyed out values are reporting as zero (it used to just repeat the previous value). This is causing really ugly line graphs.

PresentMon similarly updates every 1000ms, regardless of global settings being set to 500ms, and seems to have the same behavior - every other reading is zero.

Ideally, I could get FPS, Frametime, 1% Low, and 0.1% Low every 500ms, but if this isn't possible, it'd make a better looking line plot to simply repeat the previous value as it did in previous versions of HWiNFO.

Thanks

 

[Martin]

The limit of 1000 ms in RTSS seems to be an internal limit/setting in RTSS which determines the averaging period. Perhaps in can be changed in RTSS.
Every other value greys out because RTSS doesn't update counters faster, hence HWiNFO evaluates this as if the 3D application would be stopped.
I assume the zero values you see are not shown in the sensors window but it's what other plugins or applications get from HWiNFO via Shared Memory. This is an intentional feature as otherwise if you stop or close the 3D application, the FPS counter would keep showing the last FPS read.
I can't reproduce the zeroing of values in PresentMon though.
As explained here https://www.hwinfo.com/forum/threads/presentmon.9170/ currently the PresentMon cycle doesn't match the polling period in HWiNFO.

 

[electricnic]

I assume the zero values you see are not shown in the sensors window but it's what other plugins or applications get from HWiNFO via Shared Memory. This is an intentional feature as otherwise if you stop or close the 3D application, the FPS counter would keep showing the last FPS read.

I would prefer to see the last FPS read from RTSS instead of a null value, which external applications are reading as zero.

PresentMon in more recent updates gives a nice reading of FPS, but it's missing 1% low and 0.1% low - are these planned for future updates to PresentMon? I'd be just as happy to ditch RTSS altogether if PresentMon does it all.

 

[Martin]

1% low and 0.1% low are planned but this requires more math to calculate it, hence it might result in even higher load.