Page 1 of 1

Optimal FPS cap with frame generation?

Posted: 22 Nov 2026, 02:24
by hammelgammler
For normal non-framegen, there is a formula to which you need to cap your FPS for optimal latency with VRR, like:

Refresh - (Refresh × Refresh / 3600)

This results in the following FPS caps for a given refresh rate:

120Hz = 116 FPS
240Hz = 224 FPS
360Hz = 324 FPS
540Hz = 459 FPS

As you can see from this, the higher the Hz, the more safety margin you seemingly need. Only 4Hz @ 120Hz margin compared to 81Hz @ 540Hz.

My question now is: Wouldn’t frame gen allow to use more of the display Hz range?

Say I’m using 6x frame gen, with 540Hz, you only need 90 FPS. Lets assume that base FPS = Hz when using frame gen, that would result in the following fps caps:

Multiplier: 540/X = FPS cap * X = VRR Hz
6x: 90 FPS/Hz = 88 FPS * 6 = 528 Hz
5x: 108 FPS/Hz = 105 FPS * 5 = 525 Hz
4x: 135 FPS/Hz = 130 FPS * 4 = 520 Hz
3x: 180 FPS/Hz = 171 FPS * 3 = 513 Hz
2x: 270 FPS/Hz = 250 FPS * 2 = 500 Hz

Given that the safety margin gets larger to account for the not perfectly precise frametime limiting, am I right to assume that you should be able to limit your FPS as shown above?

If yes, then you could get around 69 Hz more motion clarity compared to non-framegen, with the trade-off of more latency of course. But given that modern titles are nowhere near 1% low 459 FPS even with the fastest PC you can buy, frame gen sounds like a very good option, especially considering you need good 1% lows to reduce VRR flicker.

Thanks!

Re: Optimal FPS cap with frame generation?

Posted: 22 Nov 2026, 04:44
by RealNC
Nothing changes with FG. The output frame rate needs to not reach the vsync ceiling, otherwise latency goes up. With FG especially, that latency is huge.

So make sure the output FPS does not go near the maximum refresh rate when vsync is eanbled. (If you use FG without vsync, then this doesn't apply, which is also no different compared to not using FG.)

Edit:

I believe the formula nvidia uses is: 3600 * Hz / (Hz + 3600)