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.



3756 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
petran79
Member
petran79

I have an Asus Rog p348q monitor at 100 hz. Set frame rate cap at 97. I notice an issue with the updated Vulkan renderer in some applications. In Snes9x emulator for example, the games run at 48 fps instead of 60. I have to set Vulkan/OpenGL present method to Native.
While on Retroarch, on top of that step, I also have to enable “Application controlled refresh rate” option, same for Dolphin emulator where I have to disable max frame rate.

Recently I noticed a 2d game where I had to set nvidia panel frame rate to 120 in order for game to run at 60 fps instead of 48.

Razvan Badaluta
Member
Razvan Badaluta

Hello!

Without a fps cap i am getting around 800 fps in fortnite creative but when i turn v sync on( even in the Nvidia apps) i am getting a limit at 438 or sometimes 425 ( i have the xg27aqdpg 500 Hz monitor) i want a fast frametime and fps as close as I can get to the monitor refresh rate but i do not want tearing. I tried playing around with Nvidia low latency but i did not notice any difference. All this happened with g sync on. I did something wrong? any tips?

Noidy
Member
Noidy

Hello!

Im getting lost in the sauce… I Have an AMD gpu with a freesync premium pro display (msi maq 1440p oled 240hz). I play mainly overwatch but I like to play with a tear free screen. So with -3 fps limit, Freesync + v-sync i only add 1 ms of delay compared to freesync/vsync off and fps unlimited?

wttrbb
Member
wttrbb

Hey man thanks for the detailed guide! I’m sorry if this is been mentioned anywhere I just couldn’t find it. What would your recommended settings for frame generation in games be? Is there anything to keep in mind when using that?
Kind regards

schustez
Member
schustez

does using reflex on + boost or ultra low latency always cap your fps below the max refresh rate of your monitor when you can sustain a higher fps or only when you are gpu bound?

wpDiscuz