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


Identical or Fraternal?

As described in G-SYNC 101: Range, G-SYNC doesn’t actually become double buffer V-SYNC above its range (nor does V-SYNC take over), but instead, G-SYNC mimics V-SYNC behavior when it can no longer adjust the refresh rate to the framerate. So, when G-SYNC hits or exceeds its ceiling, how close is it to behaving like standalone V-SYNC?

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

Pretty close. However, the G-SYNC numbers do show a reduction, mainly in the minimum and averages across refresh rates. Why? It boils down to how G-SYNC and V-SYNC behavior differ whenever the framerate falls (even for a moment) below the maximum refresh rate. With double buffer V-SYNC, a fixed frame delivery window is missed and the framerate is locked to half the refresh rate by a repeated frame, maintaining extra latency, whereas G-SYNC adjusts the refresh rate to the framerate in the same instance, eliminating latency.

As for “triple buffer” V-SYNC, while the subject won’t be delved into here due to the fact that G-SYNC is based on a double buffer, the name actually encompasses two entirely separate methods; the first should be considered “alt” triple buffer V-SYNC, and is the method featured in the majority of modern games. Unlike double buffer V-SYNC, it prevents the lock to half the refresh rate when the framerate falls below it, but in turn, adds 1 frame of delay over double buffer V-SYNC when the framerate exceeds the refresh rate; if double buffer adds 2-6 frames of delay, for instance, this method would add 3-7 frames.

“True” triple buffer V-SYNC, like “alt,” prevents the lock to half the refresh rate, but unlike “alt,” can actually reduce V-SYNC latency when the framerate exceeds the refresh rate. This “true” method is rarely used, and its availability, in part, can depend on the game engine’s API (OpenGL, DirectX, etc).

A form of this “true” method is implemented by the DWM (Desktop Window Manager) for borderless and windowed mode, and by Fast Sync, both of which will be explained in more detail further on.

Suffice to say, even at its worst, G-SYNC beats V-SYNC.



3072 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
HopelessNinersFan
Member
HopelessNinersFan

Hi!

Thank you for the guide, it’s definitely made life much easier for me. I do have some confusion though. I have a 4080 SUPER, 32 GB RAM, i9 13980HX, and 240 HZ display – I’m quite proud of it. It mentions to enable Reflex if available or Low-Latency mode if FPS doesn’t always exceed the refresh rate, but how does that fit with setting a FPS limiter to limit the FPS regardless? I apologize in-advance if I’m misinterpreting, I’m still relatively new to PC gaming on a more advanced level. Furthermore, is Reflex even worth it if my 4080 isn’t ever anywhere near getting pinned? I heard Reflex only has an impact if your GPU is at 99%. Thanks again!

Regards,

Herconomicon
Member
Herconomicon

Do you recommend v-sync set to ON globally or per application ?

Vizima
Member
Vizima

So, I’ve been doing a lot of testing over the past few weeks. My PC specs are: Intel Core i7-13700k and my monitor is an Asus 240Hz OLED. First off, I want to thank you for the guide, it started my hyperfocus of testing a lot stuff xD. I stumbled upon something peculiar while playing Apex Legends.

When I cap my framerate (I use RTSS for this) and enable both G-Sync and V-Sync in the NVIDIA Control Panel, and then select Reflex in-game, my framerate gets capped at 225, as the guide suggests. It feels incredibly smooth, but I noticed something strange – I could NOT bunny hop anymore (on controller). Turning off V-Sync allows me to bunny hop again, but I dislike the drop in smoothness, so I decided to try some other options.

The first thing I tried was disabling Reflex altogether. Despite expecting Reflex to reduce input delay, its absence actually allowed me to bunny hop again (which I consider an indicator of low input delay). Then, I decided to re-enable everything – G-Sync, V-Sync in NCP, and Reflex in-game – and capped my framerate in RTSS to 200. To my surprise, I found that I could bunny hop once again, experiencing low input delay and maintaining very smooth gameplay. Can anyone explain what’s happening here? Because with the exact same settings at 225, I couldn’t achieve the same result.

Here are my MSI Afterburner benchmark results while playing in-game:

200 FPS (capped in RTSS)
Average FPS: 198
1% Low FPS: 185
0.1% Low FPS: 166

Thanks a lot!

toby23
Member
toby23

If I have a 120 Hz monitor with G-Sync and can achieve 115fps average in a game, is there any negative to locking the framerate to 59fps with RTSS to lower power consumption and smooth out Frametime?
Running unlocked in MSFS results in the Frametime jumping around all over the place but locking to 59 fps makes it steady.

PS Super article, thank you so much for keeping it updated.

Ryan Le
Member
Ryan Le

In Sea of Thieves, I have V-Sync turned off, but there is also an option to set the buffering to either double or triple, and there’s no off option. I set it to double buffering, but do I still need to enable V-Sync in NVCP? Would the in-game double buffering option (with in-game V-Sync off) conflict with NVCP V-Sync since it’s also running on double buffering?

wpDiscuz