Is it ok if my monitor's fps counter is exceeding my ingame fps counter?

[axaro1]

I know that with Freesync I have to avoid reaching the maximum refresh rate and cap for example at 237fps with a 240hz monitor.

However when I cap the fps ingame to something like 237 it often exceed this value and almost constantly show 240fps in the Monitor's OSD counter (it is much more precise when I'm in the 60fps menu and it drops to 60hz with basically no fps fluctuations).

I tried to lower the fps cap down to 230hz and I still keep reaching 240hz in the monitor's fps counter, is Freesync not working correctly or is it normal behaviour?

I had this exact same issue with my XG2402, capping at 135 and still exceeding the fps cap in monitor's fps counter.

[jorimt]

I know that with Freesync I have to avoid reaching the maximum refresh rate and cap for example at 237fps with a 240hz monitor.

However when I cap the fps ingame to something like 237 it often exceed this value and almost constantly show 240fps in the Monitor's OSD counter (it is much more precise when I'm in the 60fps menu and it drops to 60hz with basically no fps fluctuations).

I tried to lower the fps cap down to 230hz and I still keep reaching 240hz in the monitor's fps counter, is Freesync not working correctly or is it normal behaviour?

I had this exact same issue with my XG2402, capping at 135 and still exceeding the fps cap in monitor's fps counter.

There have been a lot of complaints about this; the monitor's refresh rate meter averages frames differently than system-side counters, and thus reflects more fluctuations and instability. It's honestly hard to say if these counters on FreeSync monitors are even accurate or worth looking at beyond confirming that VRR is active.

What do the system-side FPS counters show during these instances? Are they reflecting your set limit? If so, I'd say its probably safe to ignore the monitor's refresh rate meter.

I'll note here I've only ever had native G-SYNC monitors (w/module), and that when I started my original testing for the G-SYNC 101 article, my monitor's refresh rate meter was stable at -2 FPS, and never "spiked" past that, but after a Windows update, it started doing what you describe (to a lesser degree; it seems in-monitor FreeSync counters may be less reliable than in-monitor G-SYNC counters). That said, my tests showed that when these monitor refresh rate meter spikes occurred, it didn't affect actual input lag levels, so I'm guessing this is benign.

[axaro1]

What do the system-side FPS counters show during these instances? Are they reflecting your set limit? If so, I'd say its probably safe to ignore the monitor's refresh rate meter.

I'll note here I've only ever had native G-SYNC monitors (w/module), and that when I started my original testing for the G-SYNC 101 article, my monitor's refresh rate meter was stable at -2 FPS, and never "spiked" past that, but after a Windows update, it started doing what you describe (to a lesser degree; it seems in-monitor FreeSync counters may be less reliable than in-monitor G-SYNC counters). That said, my tests showed that when these monitor refresh rate meter spikes occurred, it didn't affect actual input lag levels, so I'm guessing this is benign.

The system side fps counter does respect the limit, whether I use an ingame fps limiter or 3d party fps cap.

There are no tearing or artifacts (or even input lag issues), I just want to make sure that everything is working correctly.

[jorimt]

The system side fps counter does respect the limit, whether I use an ingame fps limiter or 3d party fps cap.

There are no tearing or artifacts (or even input lag issues), I just want to make sure that everything is working correctly.

Then I'd say it's safe to ignore it for FPS monitoring-purposes. It's still useful for verifying VRR is engaged though; static: fixed refresh, fluctuating (not counting the "spikes" or possible misreads): VRR.

[masterkaj]

Noticed the same issue in Warzone. I realized some spiking over is fine but I did notice hitting 144Hz (monitor v-sync cap) quite a bit. The in-game fps monitor never showed above 139 but my monitor kept saying it was going to 144Hz every second or so. I did some troubleshooting and realized it was the Overwolf overlay that was causing it to spike to 144Hz. Once I turned that off I see the occasional spike to 141-142Hz but at least it isn't bouncing off 144Hz anymore.

Whether or not it had any impact to input lag and was actually causing v-sync lag, I'm not sure. Better safe than sorry I guess.

[TTT]

My old Predator 240hz monitor had the original built in gsync module, the monitor fps counter on that was always spot on no matter how high or low the fps was.

I've since upgraded it to the newer IPS version but it isn't a built in Gsync module anymore and the counter is as you describe, it isn't reliable.

In COD I have the menu screen locked to 60fps and the monitor counter could still be showing 100+.

Just ignore it, use ingame/RTSS or Nvidia overlay if you want a counter on your screen.