G-SYNC 101: G-SYNC vs. V-SYNC OFF w/FPS Limit


At the Mercy of the Scanout

Now that the FPS limit required for G-SYNC to avoid V-SYNC-level input lag has been established, how does G-SYNC + V-SYNC and G-SYNC + V-SYNC “Off” compare to V-SYNC OFF at the same framerate?

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

The results show a consistent difference between the three methods across most refresh rates (240Hz is nearly equalized in any scenario), with V-SYNC OFF (G-SYNC + V-SYNC “Off,” to a lesser degree) appearing to have a slight edge over G-SYNC + V-SYNC. Why? The answer is tearing…

With any vertical synchronization method, the delivery speed of a single, tear-free frame (barring unrelated frame delay caused by many other factors) is ultimately limited by the scanout. As mentioned in G-SYNC 101: Range, The “scanout” is the total time it takes a single frame to be physically drawn, pixel by pixel, left to right, top to bottom on-screen.

With a fixed refresh rate display, both the refresh rate and scanout remain fixed at their maximum, regardless of framerate. With G-SYNC, the refresh rate is matched to the framerate, and while the scanout speed remains fixed, the refresh rate controls how many times the scanout is repeated per second (60 times at 60 FPS/60Hz, 45 times at 45 fps/45Hz, etc), along with the duration of the vertical blanking interval (the span between the previous and next frame scan), where G-SYNC calculates and performs all overdrive and synchronization adjustments from frame to frame.

The scanout speed itself, both on a fixed refresh rate and variable refresh rate display, is dictated by the current maximum refresh rate of the display:

Blur Buster's G-SYNC 101: Scanout Speed DiagramAs the diagram shows, the higher the refresh rate of the display, the faster the scanout speed becomes. This also explains why V-SYNC OFF’s input lag advantage, especially at the same framerate as G-SYNC, is reduced as the refresh rate increases; single frame delivery becomes faster, and V-SYNC OFF has less of an opportunity to defeat the scanout.

V-SYNC OFF can defeat the scanout by starting the scan of the next frame(s) within the previous frame’s scanout anywhere on screen, and at any given time:

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

This results in simultaneous delivery of more than one frame scan in a single scanout (tearing), but also a reduction in input lag; the amount of which is dictated by the positioning and number of tearline(s), which is further dictated by the refresh rate/sustained framerate ratio (more on this later).

As noted in G-SYNC 101: Range, G-SYNC + VSYNC “Off” (a.k.a. Adaptive G-SYNC) can have a slight input lag reduction over G-SYNC + V-SYNC as well, since it will opt for tearing instead of aligning the next frame scan to the next scanout when sudden frametime variances occur.

To eliminate tearing, G-SYNC + VSYNC is limited to completing a single frame scan per scanout, and it must follow the scanout from top to bottom, without exception. On paper, this can give the impression that G-SYNC + V-SYNC has an increase in latency over the other two methods. However, the delivery of a single, complete frame with G-SYNC + V-SYNC is actually the lowest possible, or neutral speed, and the advantage seen with V-SYNC OFF is the negative reduction in delivery speed, due to its ability to defeat the scanout.

Bottom-line, within its range, G-SYNC + V-SYNC delivers single, tear-free frames to the display the fastest the scanout allows; any faster, and tearing would be introduced.



3857 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
asari7k
Member
asari7k

im still a bit confused. so i want to play dbfz at the lowest latency possible bc its a fighting game capped at 60 fps and im playing on a 240hz monitor. so whats better g sync + v sync (in ncvp) on with low latency mode on ultra or just disable g sync and v sync but low latency stil on ultra . bc ive seen some videos on youtube that tested capped 60fps games at higher refres rate and it gives lower latency so when i use g sync is automaticly caps it at 60hz so doesnt that just completly ruin the g sync vs v sync setup ?

user2422
Member
user2422

Thanks for the comprehensive guide.

I have some questions on two topics:

1. If i have a 320Hz monitor with G-Sync enabled and play let’s say Apex Legends capped at 240 fps and can’t notice any obvious screen tearing, is there any reason to still use V-Sync in this scenario? From my understanding the latency in this scenario should be roughly the same whether V-Sync is enabled or disabled, so could it potentially have any other up or downsides? Also regarding this question, the increase in smoothness that is often shown with the optimal G-Sync configuration, is that due to the VRR or is it caused by the combination of G-Sync + V-Sync?

2. There seems to be a lot of situational use for some of these settings, so with all your knowledge and own personal experience over all those years now, what are you personally using when it comes to settings like LLM, Reflex, Windows VRR toggle, in-game vs driver V-Sync, what framerate limiters to use and what value to cap to?

Iriodus
Member
Iriodus

So, 2 separate but related questions:

1) For games that use the Vulkan renderer, like Doom Eternal, should we be using borderless fullscreen or exclusive fullscreen?

2) Not sure if you’d know the answer to this one, but since Proton on Linux uses a DirectX-to-Vulkan translation layer, should people use the recommendation for question 1 above, or say if a game is DirectX11 before taking into account the DX-to-Vulkan translation do use Fullscreen/Exclusive Fullscreen as if we were on Windows.

For reference, I’ve replicated the optimal G-Sync setup on my Linux machine, and since switching I’ve just been doing “If it’s originally DX11 or lower? Fullscreen/Exclusive Fullscreen. If it’s originally DX12? I use borderless fullscreen”

ksydew
Member
ksydew

Sorry for posting so much but I have one last question, I just bought the acer Nitro XV275U F5BIIPPRX, it’s a free sync premium Pro monitor but isn’t g sync certified. It should still work with g sync no problem right? I have it turned on same usual settings, g sync indicator is working and on in the top right corner, but just want to make sure it’s fine? It seems like it is but I’m not the expert

ksydew
Member
ksydew

With the newest drivers nvidia has now gotten rid of the nvidia control panel. Does this change anything for how to implement g sync? Has it changed any behavior to your knowledge? I keep g sync on, v sync on and use a frame rate limiter of RTSS. I also use v sync globally. I just had to use DDU due to sudden instability after installing the newest drivers and that’s when I found out nvcp was missing.

wpDiscuz