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.



3890 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
user2422
Member
user2422

In an earlier comment you mentioned that ULLM is somewhat inefficient compared to Reflex or a manual limit, if i were to use Gsync + Vsync + ULLM, would that starving of the max queued frames and the potential stutters that come with it even apply considering that ULLM is auto limiting the fps in this configuration? Like does it limit low enough to prevent this from even happening?

Also when using Gsync + Vsync and then only enabling ULLM via Inspector without setting max pre-rendered frames to 1 (which ULLM would’ve otherwise done if it was applied via NVCP or NVApp), would this then be just an auto limiter without the other effects of ULLM? I’ve tried this configuration in-game and the auto limit still applies but I’m unsure whether or not ULLM will have any other impact in this configuration.

eonjr
Member
eonjr

Hi, thank you for the guides! But I have something to ask. My laptop has a 300hz refresh rate that is also GSync compatible. I have it capped at 285 using a formula that I saw on a Reddit post a while ago (via NVIDIA APP > Max Frame Rate).

I unfortunately get this gray flickering during gaming but I can get used to it. However, what I cannot stand is, when I tried using editing software (like Adobe Premiere Pro), the flickering was also present despite me having turned off GSync specifically for that app (via NVIDIA App). Is there something I am doing wrong? What can be done to completely eliminate flickering for non-game apps?

HagenKL
Member
HagenKL

Hey, the article talks about GSync with the Module. Is the Behaviour the same for GSync Compatible (aka Freesync monitors?)

Apache3m
Member
Apache3m

Naturally, with MFG enabled, Reflex limits my FPS from 240 to 224; however, if I disable V-Sync in the Nvidia Control Panel, I hit 240 FPS with MFG on.

Mark Rejhon
Admin

It bears worth noting that 224 vs 240 is extremely small (1/224)-(1/240) = 0.3ms frametime difference. It’s more about geometrics (e.g. 200fps vs 400fps vs 1000fps) that is much more noticeable. It’s possible to have a much smoother 224fps and a much worse 240fps that looks rougher-motion than 224fps. It’s all in the microstutter/tearing mechanics, and how you prioritize visual fidelity. A great test is to strafe in CP2077 and watch for microstuttering/tearing. This is one of the ways to compare framepacing quality of VRR and capping mechanisms.

Those using VRR and framegen are often looking to improve smoothness without prioritizing on esports latency, so this is often prioritized for solo games like Witcher and CP2077. Turning off Reflex and still using VSYNC ON is another way to get 240fps with smoothness, but that increases latency dramatically on top of the latency that framegen gives, so it can veer into distraction territory.

Reflex + framegen + VRR is a good “acceptable-for-solo latency” compromise, and lagfeel can actually still feel similar to the original pre-framegen framerate (with latency countermeasured turned off).

Apache3m
Member
Apache3m

Hi – I have a setup with a 9800X3D and an RTX 5080, along with an MSI 321URX QD-OLED monitor.
Could you tell me what I should do when gaming with NVIDIA’s Frame Gen (MFG) enabled? Should I stick with the G-Sync + V-Sync + Reflex settings, or do you recommend something else?

wpDiscuz