G-SYNC 101: G-SYNC Ceiling vs. FPS Limit


How Low Should You Go?

Blur Busters was the world’s first site to test G-SYNC in Preview of NVIDIA G-SYNC, Part #1 (Fluidity) using an ASUS VG248QE pre-installed with a G-SYNC upgrade kit. At the time, the consensus was limiting the fps from 135 to 138 at 144Hz was enough to avoid V-SYNC-level input lag.

However, much has changed since the first G-SYNC upgrade kit was released; the Minimum Refresh Range wasn’t in place, the V-SYNC toggle had yet to be exposed, G-SYNC did not support borderless or windowed mode, and there was even a small performance penalty on the Kepler architecture at the time (Maxwell and later corrected this).

My own testing in my Blur Busters Forum thread found that just 2 FPS below the refresh rate was enough to avoid the G-SYNC ceiling. However, now armed with improved testing methods and equipment, is this still the case, and does the required FPS limit change depending on the refresh rate?

Blur Buster's G-SYNC 101: Input Latency & Optimal Settings
Blur Buster's G-SYNC 101: Input Latency & Optimal Settings
Blur Buster's G-SYNC 101: Input Latency & Optimal Settings
Blur Buster's G-SYNC 101: Input Latency & Optimal Settings
Blur Buster's G-SYNC 101: Input Latency & Optimal Settings
Blur Buster's G-SYNC 101: Input Latency & Optimal Settings

As the results show, just 2 FPS below the refresh rate is indeed still enough to avoid the G-SYNC ceiling and prevent V-SYNC-level input lag, and this number does not change, regardless of the maximum refresh rate in use.

To leave no stone unturned, an “at” FPS, -1 FPS, -2 FPS, and finally -10 FPS limit was tested to prove that even far below -2 FPS, no real improvements can be had. In fact, limiting the FPS lower than needed can actually slightly increase input lag, especially at lower refresh rates, since frametimes quickly become higher, and thus frame delivery becomes slower due to the decrease in sustained framerates.

As for the “perfect” number, going by the results, and taking into consideration variances in accuracy from FPS limiter to FPS limiter, along with differences in performance from system to system, a -3 FPS limit is the safest bet, and is my new recommendation. A lower FPS limit, at least for the purpose of avoiding the G-SYNC ceiling, will simply rob frames.



273 Comments For “G-SYNC 101”

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Sort by:   newest | oldest | most liked
Phroster
Member
Phroster

Why is it, that in most games, borderless fullscreen + gsync, gives worse results then exclusive full screen mode? (uneven frametimes, micro stutters)
Using a frame limiter to set the framerate -3 below the refresh rate makes it even worse when using borderless fullscreen.

I did find that G-sync + Fast sync + borderless fullscreen seems to give better results in some games. Still limiting the frame rate in borderless fullscreen, introduces microstutters.

Why is borderless fullscreen so unreliable with gsync enabled?

jdawg
Member
jdawg

Hey, so I didn’t know about turning on V-sync in NVCP only, but before I did that I was getting the occasional stutter even though the action on screen wasn’t that intense. I have RTSS showing a graph of FPS and I notice there are several little dips happening every second. The game moves smooth but then I get the stutter occasionally. I’ve closed everything unnecessary but maybe there’s more to close…not sure what other processes I can close in Windows 10 and I haven’t done any optimizations like in Windows 7.

Fast forward to setting it up as recommended here (141 FPS limit in game for my 144Hz monitor, G-sync on, V-sync ON in NVCP only, V-sync OFF in-game) and I noticed that the dips on the graph are even deeper…however I haven’t seen a stutter yet and the game plays very smooth with no lag. Any explanation for those dips in the graph though?

metalpizza123
Member
metalpizza123

Hi hi, Just a quick heads up for users with several displays of varying refresh rates. Windows will sometimes only report the lowest refresh rate monitor as the system-wide V-Sync target. After testing on driver ver 436.02, with 3 different monitors, here are my findings. I testeed with 3 games, all had similar behaviour. I used the recommended settings as per the guide.
NVCP V-sync ON
Gsync Enabled
Ingame FPS Limiter or RTSS used
Ingame Vsync/buffering disabled

Main monitor :G-Sync, 144hz.
Second Monitor 60 Hz
In game Framerate 60~

Main monitor :G-Sync, 144hz
Second monitor 75 Hz
In game Framerate 75~

Main monitor G-sync,144hz
Second monitor, 60hz
third monitor, 75hz
In game framerate 60~

Only main monitor: G-Sync 144hz
In game frame rate 140~

There’s probably a way to disable this, but for now I’ve resorted to just unplugging my other monitors. Just a note for any multi monitor users. I wish I could test more, but I just wanna play games.

kucki
Member
kucki

Should we use the “Low Latency Mode” On or Ultra with G-Sync?

Chief Blur Buster
Admin

Possibly beneficial for uncapped GSYNC + VSYNC ON. Will need to be tested.

This will reduce lag differential of below-Hz (GSYNC behavior) versus match-Hz (VSYNC ON behavior).

Creakffm
Member
Creakffm

Hello Guys, really Intresting Article/Guide but i wanna know something from you.

i Playing Games since 20 Years i know in Old Times with 60 HZ Monitors i play Competitive Games with VSYNC off to get most FPS ingame.

So back to 2019.

Im Using a Nvidia Geforce 1080 TI and my Monitor is 240 HZ DELL Alienware AW2518HF with GSYNC on Displayport Cable.

i wanna Optimizing all to Play Competitive. Actual i play with Ingame Fortnite Framerate Limit 240 HZ because see this by a lot of People.

When i wanna get less Inputlag i set in Nvidia Inspector Framerate Limiter to 245,244 ( more FPS than HZ or less and than which one is best? )

thanks for Answering

wpDiscuz