G-SYNC 101: Control Panel


G-SYNC Module

The G-SYNC module is a small chip that replaces the display’s standard internal scaler, and contains enough onboard memory to hold and process a single frame at a time.

The module exploits the vertical blanking interval (the span between the previous and next frame scan) to manipulate the display’s internal timings; performing G2G (gray to gray) overdrive calculations to prevent ghosting, and synchronizing the display’s refresh rate to the GPU’s render rate to eliminate tearing, along with the delayed frame delivery and adjoining stutter caused by traditional syncing methods.

G-SYNC Demo

The below Blur Busters Test UFO motion test pattern uses motion interpolation techniques to simulate the seamless framerate transitions G-SYNC provides within the refresh rate, when directly compared to standalone V-SYNC.

G-SYNC Activation

“Enable for full screen mode” (exclusive fullscreen functionality only) will automatically engage when a supported display is connected to the GPU. If G-SYNC behavior is suspect or non-functioning, untick the “Enable G-SYNC, G-SYNC Compatible” box, apply, re-tick, and apply.

Blur Buster's G-SYNC 101: Control Panel

G-SYNC Windowed Mode

“Enable for windowed and full screen mode” allows G-SYNC support for windowed and borderless windowed mode. This option was introduced in a 2015 driver update, and by manipulating the DWM (Desktop Windows Manager) framebuffer, enables G-SYNC’s VRR (variable refresh rate) to synchronize to the focused window’s render rate; unfocused windows remain at the desktop’s fixed refresh rate until focused on.

G-SYNC only functions on one window at a time, and thus any unfocused window that contains moving content will appear to stutter or slow down, a reason why a variety of non-gaming applications (popular web browsers among them) include predefined Nvidia profiles that disable G-SYNC support.

Note: this setting may require a game or system restart after application; the “G-SYNC Indicator” (Nvidia Control Panel > Display > G-SYNC Indicator) can be enabled to verify it is working as intended.

G-SYNC Preferred Refresh Rate

“Highest available” automatically engages when G-SYNC is enabled, and overrides the in-game refresh rate selector (if present), defaulting to the highest supported refresh rate of the display. This is useful for games that don’t include a selector, and ensures the display’s native refresh rate is utilized.

“Application-controlled” adheres to the desktop’s current refresh rate, or defers control to games that contain a refresh rate selector.

Note: this setting only applies to games being run in exclusive fullscreen mode. For games being run in borderless or windowed mode, the desktop dictates the refresh rate.

G-SYNC & V-SYNC

G-SYNC (GPU Synchronization) works on the same principle as double buffer V-SYNC; buffer A begins to render frame A, and upon completion, scans it to the display. Meanwhile, as buffer A finishes scanning its first frame, buffer B begins to render frame B, and upon completion, scans it to the display, repeat.

The primary difference between G-SYNC and V-SYNC is the method in which rendered frames are synchronized. With V-SYNC, the GPU’s render rate is synchronized to the fixed refresh rate of the display. With G-SYNC, the display’s VRR (variable refresh rate) is synchronized to the GPU’s render rate.

Upon its release, G-SYNC’s ability to fall back on fixed refresh rate V-SYNC behavior when exceeding the maximum refresh rate of the display was built-in and non-optional. A 2015 driver update later exposed the option.

This update led to recurring confusion, creating a misconception that G-SYNC and V-SYNC are entirely separate options. However, with G-SYNC enabled, the “Vertical sync” option in the control panel no longer acts as V-SYNC, and actually dictates whether, one, the G-SYNC module compensates for frametime variances output by the system (which prevents tearing at all times. G-SYNC + V-SYNC “Off” disables this behavior; see G-SYNC 101: Range), and two, whether G-SYNC falls back on fixed refresh rate V-SYNC behavior; if V-SYNC is “On,” G-SYNC will revert to V-SYNC behavior above its range, if V-SYNC is “Off,” G-SYNC will disable above its range, and tearing will begin display wide.

Within its range, G-SYNC is the only syncing method active, no matter the V-SYNC “On” or “Off” setting.

Currently, when G-SYNC is enabled, the control panel’s “Vertical sync” entry is automatically engaged to “Use the 3D application setting,” which defers V-SYNC fallback behavior and frametime compensation control to the in-game V-SYNC option. This can be manually overridden by changing the “Vertical sync” entry in the control panel to “Off,” “On,” or “Fast.”



3059 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
Zehdah
Member
Zehdah

Hey Jorimt. Do these settings apply for a monitor using adaptive sync if I have a Nvidia GPU? So can I copy the recommended settings as if I have Gsync? Heard it works the same as Gsync but thought I’d ask to be sure.

blaskovic
Member
blaskovic

Hi jorimt. I have a question for you. Sometime in older games (2011 – 2013) I have a drop frame from 144 to 140 or 144 to 135 and I notice this microstutter with G-sync but in other games if I have this drops (for example in Dirty Rally) I don’t see anything. My question is this: Why in some case (games) G-Sync seems works but in other circumstances (games) i see this microstutter? G-Sync shouldn’t avoid Microstutter? Thank you

stadiofriuli
Member
stadiofriuli

I’ve got a question. Got the Dell S2721DGF(A) which is G-Sync compatible, I’m running the monitor at 165Hz.

So what I basically did is to set a FPS cap @161 with RTSS.

Enabled G-Sync fullscreen in NVCP.

Enabled V-Sync in NVCP.

According to the guide V-Sync within the G-Sync range should still act like for native G-Sync monitors when it’s an official supported G-Sync compatible monitor.

What happens for me though is.

When V-Sync is enabled FPS cap at 158, not 161 as set in RTSS.

When I then disable V-Sync and have only G-Sync running it’s capped at 161 again.

So my question really is why this weird behaviour?

Should I activate or deactivate V-Sync in my case?

SvenL
Member
SvenL

Hi,
First of all, thank you so much for creating such an amazing guide. After reading through a few more questions arose.

I’m playing Warzone (FPS game) on a 1080p 144hz free sync monitor with an RTX 2080Ti graphics card. (I achieve 170-180 fps in game uncapped, which is above the refresh rate of my monitor)

My goal is to have a 100% tear-free gaming experience with the least amount of input lag to achieve the best possible accuracy.

First, I took over the following settings from you
NVCP: G-Sync & V-Sync: On

But when it comes to the FPS limiter, I’m still unsure which is best in my case. (Warzone also supports reflex)

In-Game FPS Limiter (141 FPS cap)
Reflex: On / On + Boost
RTSS / NVIDIA’s Max Frame Rate (141 FPS cap)

The question is which of these options has the lowest input lag and at the same time the most constant possible frame time. (I assume these 2 factors are especially important for FPS games)
Or what you think would be the best sweet spot out of all of these options.

With reflex activated (On + Boost), I noticed that the frame rate varies (around 138 fps). I’m not sure whether this will have a negative impact on my frame time or input delay, as I could easily achieve a constant 141 FPS with my graphics card. Should I then prefer the in-game FPS limiter or RTSS / NVIDIA’s Max Frame Rate over reflex?

Thank you very much

RoseGoldCrobat
Member
RoseGoldCrobat

I signed up here since you seem to know a lot about this. I have a very strange issue.

I have a monitor that is Gsync compatible and Gsync is on in fullscreen mode.

When I play certain games, the current ones I’ve seen it in are Red Dead Redemption 2 and Hitman 3 I would like to have gsync on and vsync on. The problem is when both settings are on at the same time my FPS caps to 72 fps, half of my monitor’s refresh rate. I don’t understand why this is happening. Could I be missing a setting?

wpDiscuz