G-SYNC 101: Range


Blur Buster's G-SYNC 101: Range Chart

Exceeds G-SYNC Range

G-SYNC + V-SYNC “Off”:
G-SYNC disengages, tearing begins display wide, no frame delay is added.

G-SYNC + V-SYNC “On”:
G-SYNC reverts to V-SYNC behavior when it can no longer adjust the refresh rate to the framerate, 2-6 frames (typically 2 frames; approximately an additional 33.2ms @60 Hz, 20ms @100 Hz, 13.8ms @144 Hz, etc) of delay is added as rendered frames begin to over-queue in both buffers, ultimately delaying their appearance on-screen.

G-SYNC + Fast Sync*:
G-SYNC disengages, Fast Sync engages, 0-1 frame of delay is added**.
*Fast Sync is best used with framerates in excess of 2x to 3x that of the display’s maximum refresh rate, as its third buffer selects from the “best” frame to display as the final render; the higher the sample rate, the better it functions. Do note, even at its most optimal, Fast Sync introduces uneven frame pacing, which can manifest as recurring microstutter.
**Refresh rate/framerate ratio dependent (see G-SYNC 101: G-SYNC vs. Fast Sync).

Within G-SYNC Range

Refer to “Upper & Lower Frametime Variances” section below…

Upper & Lower Frametime Variances

G-SYNC + V-SYNC “Off”:
The tearing inside the G-SYNC range with V-SYNC “Off” is caused by sudden frametime variances output by the system, which will vary in severity and frequency depending on both the efficiency of the given game engine, and the system’s ability (or inability) to deliver consistent frametimes.

G-SYNC + V-SYNC “Off” disables the G-SYNC module’s ability to compensate for sudden frametime variances, meaning, instead of aligning the next frame scan to the next scanout (the process that physically draws each frame, pixel by pixel, left to right, top to bottom on-screen), G-SYNC + V-SYNC “Off” will opt to start the next frame scan in the current scanout instead. This results in simultaneous delivery of more than one frame in a single scanout (tearing).

In the Upper FPS range, tearing will be limited to the bottom of the display. In the Lower FPS range (<36) where frametime spikes can occur (see What are Frametime Spikes?), full tearing will begin.

Without frametime compensation, G-SYNC functionality with V-SYNC “Off” is effectively “Adaptive G-SYNC,” and should be avoided for a tear-free experience (see G-SYNC 101: Optimal Settings & Conclusion).

G-SYNC + V-SYNC “On”:
This is how G-SYNC was originally intended to function. Unlike G-SYNC + V-SYNC “Off,” G-SYNC + V-SYNC “On” allows the G-SYNC module to compensate for sudden frametime variances by adhering to the scanout, which ensures the affected frame scan will complete in the current scanout before the next frame scan and scanout begin. This eliminates tearing within the G-SYNC range, in spite of the frametime variances encountered.

Frametime compensation with V-SYNC “On” is performed during the vertical blanking interval (the span between the previous and next frame scan), and, as such, does not delay single frame delivery within the G-SYNC range and is recommended for a tear-free experience (see G-SYNC 101: Optimal Settings & Conclusion).

G-SYNC + Fast Sync:
Upper FPS range: Fast Sync may engage, 1/2 to 1 frame of delay is added.
Lower FPS range: see “V-SYNC ‘On'” above.

What are Frametime Spikes?

Frametime spikes are an abrupt interruption of frames output by the system, and on a capable setup running an efficient game engine, typically occur due to loading screens, background asset streaming, network activity, and/or the triggering of a script or physics system, but can also be exacerbated by an incapable setup, inefficient game engine, poor netcode, low RAM/VRAM and page file over usage, misconfigured (or limited game support for) SLI setups, faulty drivers, specific or excess background processes, in-game overlay or input device conflicts, or a combination of them all.

Not to be confused with other performance issues, like framerate slowdown or V-SYNC-induced stutter, frametime spikes manifest as the occasional hitch or pause, and usually last for mere micro to milliseconds at a time (seconds, in the worst of cases), plummeting the framerate to as low as the single digits, and concurrently raising the frametime to upwards of 1000ms before re-normalizing.

G-SYNC eliminates traditional V-SYNC stutter caused below the maximum refresh rate by repeated frames from delayed frame delivery, but frametime spikes still affect G-SYNC, since it can only mirror what the system is outputting. As such, when G-SYNC has nothing new to sync to for a frame or frames at a time, it must repeat the previous frame(s) until the system resumes new frame(s) output, which results in the visible interruption observed as stutter.

The more efficient the game engine, and the more capable the system running it, the less frametime spikes there are (and the shorter they last), but no setup can fully avoid their occurrence.

Minimum Refresh Range

Once the framerate reaches the approximate 36 and below mark, the G-SYNC module begins inserting duplicate refreshes per frame to maintain the panel’s minimum physical refresh rate, keep the display active, and smooth motion perception. If the framerate is at 36, the refresh rate will double to 72 Hz, at 18 frames, it will triple to 54 Hz, and so on. This behavior will continue down to 1 frame per second.

Regardless of the reported framerate and variable refresh rate of the display, the scanout speed will always be a match to the display’s current maximum refresh rate; 16.6ms @60Hz, 10ms @100 Hz, 6.9ms @144 Hz, and so on. G-SYNC’s ability to detach framerate and refresh rate from the scanout speed can have benefits such as faster frame delivery and reduced input lag on high refresh rate displays at lower fixed framerates (see G-SYNC 101: Hidden Benefits of High Refresh Rate G-SYNC).



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