G-SYNC 101: G-SYNC vs. V-SYNC OFF


Beyond the Limits of the Scanout

It’s already been established that single, tear-free frame delivery is limited by the scanout, and V-SYNC OFF can defeat it by allowing more than one frame scan per scanout. That said, how much of an input lag advantage can be had over G-SYNC, and how high must the framerate be sustained above the refresh rate to diminish tearing artifacts and justify the difference?

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

Quite high. Counting first on-screen reactions, V-SYNC OFF already has a slight input lag advantage (up to a 1/2 frame) over G-SYNC at the same framerate, especially the lower the refresh rate, but it actually takes a considerable increase in framerate above the given refresh rate to widen the gap to significant levels. And while the reductions may look significant in bar chart form, even with framerates in excess of 3x the refresh rate, and when measured at middle screen (crosshair-level) only, V-SYNC OFF actually has a limited advantage over G-SYNC in practice, and most of it is in areas that one could argue, for the average player, are comparatively useless when something such as a viewmodel’s wrist is updated 1-3ms faster with V-SYNC OFF.

This is where the refresh rate/sustained framerate ratio factors in:

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 shown in the above diagrams, the true advantage comes when V-SYNC OFF can allow not just two, but multiple frame scans in a single scanout. Unlike syncing solutions, with V-SYNC OFF, the frametime is not paced to the scanout, and a frame will begin scanning in as soon as it’s rendered, regardless whether the previous frame scan is still in progress. At 144Hz with 1000 FPS, for instance, this means with a sustained frametime of 1ms, the display updates nearly 7 times in a single scanout.

In fact, at 240Hz, first on-screen reactions became so fast at 1000 FPS and 0 FPS, that the inherit delay in my mouse and display became the bottleneck for minimum measurements.

So, for competitive players, V-SYNC OFF still reigns supreme in the input lag realm, especially if sustained framerates can exceed the refresh rate by 5x or more. However, while at higher refresh rates, visible tearing artifacts are all but eliminated at these ratios, it can instead manifest as microstutter, and thus, even at its best, V-SYNC OFF still can’t match the consistency of G-SYNC frame delivery.



3099 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
dandyjr
Member
dandyjr

Hello there! I recently bought a 500Hz G-sync monitor and it’s the first time I’ve owned a true G-sync monitor with a module. The exact model is the AW2524H. One of the first things I noticed with this monitor is that the frames never hit the max range of the monitor as if the module has it’s own way to prevent leaving the G-Sync range. The monitor is technically a 480Hz panel but it has a factory overclock you can set to 500Hz. In stock form (with all of the proper G-sync settings in the control panel) the frames automatically are capped at 477 and never will hit 480. Overclocked to 500Hz, The frames will never go above 496. I tested multiple games just to make sure and they all produced the same results. What I’m wondering is if this is an effect of this specific model or if this is true for all G-Sync native monitors. Does this mean that I never have to cap my fps because the monitor won’t allow the frames to hit the ceiling anyway? I noticed that if I enable reflex in supported games, the frames will be capped at 438 instead of 496. My guess is that Nvidia set such a low limit to be safe for G-Sync compatible monitors that happen to be 500Hz (since I’ve heard they are less accurate and will leave range more often). What are your thoughts on this? I’d be stoked to hear that I don’t have to cap my fps anymore but it seems too good to be true haha!

IggyRex
Member
IggyRex

Hello, you probably get asked this a lot, but I game on a lg c1 at 120hz, and I was wondering what would be best for my setup. I am currently using Vsync – on in the control panel, but I am unsure if I should set low latency to ultra or if setting to On would be the better option for me. Having it set to ON would require me to set an fps limit on a game basis correct? So something like elden ring would work better being capped to 59 or 57fps as opposed to it set to ultra which would do it for me. What are the benefits of either option? Sorry, and please let me know. I just want to get the most out of my hardware and out of gsync.

Kaffik
Member
Kaffik

Hi!
I have 165 Hz G-Sync Compatible (ls27ag500nuxen) monitor.
I used all your tips for this type of display but something irritates me a lot.
60 fps on my screen looks like 30-35 at best, I need to have like 95-100 fps to make it look like smooth 60.
For example my boyfriend has 144 Hz VRR TV and 60 fps looks like 60 fps.
I have DP 1.4 and VRR on.
Do I really need a G-Sync module to make it better?

Indignified
Member
Indignified

Hello, is there any point of having gsync or reflex on if fps is uncapped?

ChillyWilly219
Member
ChillyWilly219

Hello, on my LG Ultragear OLED 45GR95QE-B monitor I have experienced flickering in games like Lords of the Fallen or Hellbalde, even in Warzone. A slight flicker mainly in the menus and loading areas. Is there a solution to this problem? Many people say to turn off g sync directly. What do you recommend me?. Greetings.

wpDiscuz