Accurate way of determining if FPS is ongoing outside of VRR range

[Blackops786187]

Hi,

I have followed the standard blurbuster guide for enabling g sync. (Enable g sync, enable v sync and capping fps to 138 via rivatuner on 144hz display to prevent refresh rate from exceeding 144hz and subsequently enabling v sync)

Is there an accurate way of determining if the fps is occasionally dipping above 144hz and thus triggering v sync? My tv fps counter seems to indicate it’s hitting 144 occasionally but the games fps counter says otherwise?

[jorimt]

My tv fps counter seems to indicate it’s hitting 144 occasionally but the games fps counter says otherwise?

Your TV counter is approximated and not as reliable or accurate as system-side readouts. Ignore it; as long as it is fluctuating, VRR is working as intended.

[Blackops786187]

Cool. I’ll scrap looking at the tv counter. Is there anything in RTSS I need to do to make sure the FPS it’s showing is also accurate as much as possible? Just want to confirm the fps is rock solid below the refresh rate and v sync isn’t being triggered which adds input lag.

[Chief Blur Buster]

The TV counter is useful for troubleshooting whether VRR is currently operating, but it's not as accurate as RTSS.
The TV counter algorithm only a very simple approximator.

[jorimt]

Is there anything in RTSS I need to do to make sure the FPS it’s showing is also accurate as much as possible?

Default settings.