Nvidia’s new GeForce driver includes highly-requested max frame rate feature

So the take away is the NVIDIA control panel FPS limiter does nothing better than RTSS and also only does whole numbers.

RTSS has the advantage of doing thousandths. This is important if you are running a display with say strobing or BFI. Example: with RTSS on a 120 Hz BFI display like the LG 48" CX OLED, you can set the FPS cap in RTSS to 119.993 and keep V-Sync on. This prevents screen tear, prevents the V-Sync-on input lag penalty, is very frametime smooth and minimizes any visible stuttering.

Setting the FPS cap with a whole number such as in NVIDIA control panel (IE:119 to prevent the V-Sync input lag penalty), you get a noticeable stutter once per second.
 
So the take away is the NVIDIA control panel FPS limiter does nothing better than RTSS and also only does whole numbers.

RTSS has the advantage of doing thousandths. This is important if you are running a display with say strobing or BFI. Example: with RTSS on a 120 Hz BFI display like the LG 48" CX OLED, you can set the FPS cap in RTSS to 119.993 and keep V-Sync on. This prevents screen tear, prevents the V-Sync-on input lag penalty, is very frametime smooth and minimizes any visible stuttering.

Setting the FPS cap with a whole number such as in NVIDIA control panel (IE:119 to prevent the V-Sync input lag penalty), you get a noticeable stutter once per second.

Set it to 115 or 117. Do you get stutter?
 
So the take away is the NVIDIA control panel FPS limiter does nothing better than RTSS and also only does whole numbers.

RTSS has the advantage of doing thousandths. This is important if you are running a display with say strobing or BFI. Example: with RTSS on a 120 Hz BFI display like the LG 48" CX OLED, you can set the FPS cap in RTSS to 119.993 and keep V-Sync on. This prevents screen tear, prevents the V-Sync-on input lag penalty, is very frametime smooth and minimizes any visible stuttering.

Setting the FPS cap with a whole number such as in NVIDIA control panel (IE:119 to prevent the V-Sync input lag penalty), you get a noticeable stutter once per second.

In actual usage in that video, they are essentially identical in performance.

With either it is recommended to set the limit 3 fps below the limit of your monitor. So I am not getting what the benefit of fractional FPS values.
 
That does not really make sense. The point of setting your limit to 163 is not to hitting 165. This is done to prevent VSYNC from kicking in from what i understand.

When i set is to 144 in the NV control panel, it never goes above 144. Why cant it hold it at 163?

I suspect it has something to do with the game engine itself, but im no expert in this topic.

I did some digging and found these to be pretty informative:



Also, Blurbusters updated settings for GSYNC and new drivers/RTSS

https://www.blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/14/


If you want to guarantee it doesn't go above your cap you have to sacrifice input lag or allow stuttering. That's just how the math works.
 
This is great because the old option you had access to via nvinspector had a lot of input lag compared to RTSS (it was like 2-3 frames while RTSS is 1 IIRC). This is on par with RTSS and without requiring an external application. Awesome!

It's true that it is missing the 0.001 frame accuracy of RTSS though, meaning I still need to keep it on my laptop that doesn't have VRR. And probably on my desktop until we get HDMI 2.1 GPUs, for the 48" OLED.
 
Set it to 115 or 117. Do you get stutter?

Yes, any FPS cap below the monitors refresh rate (non-VRR) with V-Sync on will cause an intermittent stutter. The reason going 0.007 Hz refresh rate below that is it makes the stutter so tiny and far spaced you can't even notice it really.

In actual usage in that video, they are essentially identical in performance.

With either it is recommended to set the limit 3 fps below the limit of your monitor. So I am not getting what the benefit of fractional FPS values.

That applies only if VRR is on. I'm specifically talking about scenarios that you want to lock an FPS close to the monitors refresh rate that don't use VRR. IE: non VRR display, strobing backlight or BFI.
 
Yes, any FPS cap below the monitors refresh rate (non-VRR) with V-Sync on will cause an intermittent stutter. The reason going 0.007 Hz refresh rate below that is it makes the stutter so tiny and far spaced you can't even notice it really.



That applies only if VRR is on. I'm specifically talking about scenarios that you want to lock an FPS close to the monitors refresh rate that don't use VRR. IE: non VRR display, strobing backlight or BFI.

These features exist for VRR. What you are describing is Vsync.
 
These features exist for VRR. What you are describing is Vsync.

Are you reading only half of his messages or something? :p

He very clearly said he was talking about v-sync. For the record BFI/strobing can't be combined with VRR properly just yet, hence why he's talking about v-sync.
 
Last edited:
Are you reading only half of his messages or something? :p

He very clearly said he was talking about v-sync. For the record BFI/strobing can't be combined with VRR properly just yet, hence why he's talking about v-sync.

Doesn't change the fact that these features are for VRR, not Vsycn.

Trying to create a Vsync like option, that isn't really vsync is absurd.

As soon as you drop a fractional amount below native, you are going to miss a frame.

The monitor doesn't care if you 2 ms late, or 0.002 ms late. Late is Late.

It sounds more like with RTSS he is turning off vsync and thus living with screen tears, and it's vsync on in NVidias, and causes more judders. Turn off vsync for NVidias solution (if it allows) and it should be about the same.
 
Last edited:
No, he is talking about the low-lag v-sync trick: https://www.blurbusters.com/howto-low-lag-vsync-on/

Basically if you cap your framerate very slightly below the refresh rate with v-sync on, you greatly reduce the v-sync lag, while still not having tearing and with slight, mostly imperceptible & regular micro-stutters (if you do it right, it requires some fine tuning and reading your exact refresh rate).

Yes, this is NOT for VRR. It's something you can do with RTSS, but not with the nvidia frame limiter. That's what he's been talking about the entire time.
 
No, he is talking about the low-lag v-sync trick: https://www.blurbusters.com/howto-low-lag-vsync-on/

Basically if you cap your framerate very slightly below the refresh rate with v-sync on, you greatly reduce the v-sync lag, while still not having tearing and with slight, mostly imperceptible & regular micro-stutters (if you do it right, it requires some fine tuning and reading your exact refresh rate).

Sure you can do that, but you obviously going to disable vsync, and go with screen tearing instead. Because otherwise running slightly below frequency, is a frame miss.

I'll be the biggest difference is running with Vsync on with the NVidia solution while it's off for the RTSS solution.
 
... I rest my case.

giphy.gif
 
Back
Top