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.

NVIDIA Control Panel Retirement

As of NVIDIA driver version 610.47, the NVIDIA Control Panel has officially reached EOL:

“After 20 years of dedicated service, the classic NVIDIA Control Panel is officially retiring for Game Ready and Studio Drivers. For NVIDIA RTX PRO users, the NVIDIA Control Panel will continue to be supported until we have migrated professional features to the NVIDIA app

Existing installs of the NVIDIA Control Panel will remain on users’ systems, unless they perform a clean installation, and users who still need the NVIDIA Control Panel can continue to download it from the Microsoft Store, but we won’t be adding features, fixes, or other changes.”

While the original NVIDIA Control Panel settings locations will be retained below, the NVIDIA App settings locations are now also included for a more up-to-date reference.

G-SYNC Activation

“Full screen” / “Enable for full screen mode” (exclusive fullscreen-type functionality only) is automatically selected when a supported display is connected to the GPU. If G-SYNC behavior is suspect or non-functioning, tick off, apply, tick on, and apply.

G-SYNC Windowed Mode

“Full screen and windowed” / “Enable for windowed and full screen mode” allows G-SYNC support for legacy windowed and borderless windowed modes. This option was introduced in a 2015 driver update, and by manipulating the DWM (Desktop Windows Manager) framebuffer, allows 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. As such, per-profile application of this mode is optimal vs. global. See Closing FAQ #5 for instructions.

Note: this setting may require a game or system restart after application; “Show indicator” / “G-SYNC Indicator” can be enabled to verify it is working as intended.

G-SYNC Preferred Refresh Rate

“Highest available” is automatically selected when G-SYNC is initially 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-type modes. For games being run in legacy borderless or windowed modes, the desktop always dictates the refresh rate.

  • NVIDIA App
    Settings location

    The NVIDIA App does not expose the legacy “Preferred refresh rate” setting.

    While it is no longer directly accessible in the app, like with the NVIDIA Control Panel, it is still automatically selected when G-SYNC is initially enabled, just internally, and can alternatively be accessed via the NVIDIA Profile Inspector (download here):

    Blur Buster's G-SYNC 101: Control Panel

  • NVIDIA Control Panel
    Settings location (legacy)

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 “Vertical Sync” entry is automatically set to “Use 3D app setting” / “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.”



3849 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
anthony3192
Member
anthony3192

I have a problem with vrr flickering, in games like oblivion remastered in the evening, it becomes practically unplayable. I have a 9800x3d and a 5090, connected to a 240hz MSI 321URX monitor. the flickering is more present when I use frame generation or when I go to capture the fps. how can I do it? advice?

polce24
Member
polce24

Can/should I use an RTSS frame cap while using Reflex (ON) in-game?

Build = 9800X3D, 5080, MSI X870E
LG OLED 32″ 240HZ monitor with GSYNC/VRR

I’ve been putting a lot of hours into ARC Raiders and noticed that even with steady FPS (i.e., 225), panning the camera around was not smooth. I never got actual freezes, it just seemed like the image was not “solid” – trees would jitter around, etc.

Settings = GSYNC On (full screen only), VSYNC On NVCP (off in-game), Reflex On, No Cap
^ This is typically how I run most games, letting the FPS stay uncapped but using Reflex so it never goes over 225.

I’ve come to learn that this “jitter” even at high FPS is due to frame pacing and then learned that an RTSS a-sync cap is one of the best ways to to achieve great frame pacing.

I then changed my settings above to include an RTSS async cap of 200 FPS – panning the camera around was much smoother.

The issue is, I still notice some stutter now and then and wonder if that is because I have Reflex set to ON.

Should I just use SYNC On (full screen only), VSYNC On NVCP (off in-game) + RTSS async cap in every game and ignore Reflex?

olam
Member
olam

Hi, I would have two scenarios on which I’m not sure if I set it correctly in my case.

G-Sync + V-Sync are on

Game 1 – CS2 (FPS 99% exceeds refresh rate, Reflex available)
– FPS Limit 357 (I got 360 Hz)
– Reflex off (LLM also off)

Game 2 – PUBG (FPS rarely exceeding refresh rate, Reflex not available)
– FPS Limit 357
– Low Latency Mode -> On

Am I doing it right in this case?
If not, please correct me! Thanks in advance for your reply.
I just want to have the smoothest experience.

sc719
Member
sc719

I play competitive COD, on a 280Hz OLED, with average frames 300, 1% lows 220 and 5% 250…

To summarize theres basically 3 options you are suggesting?

1. Lowest tear free: VRR + Vsync + Reflex/AntiLag (or turn this off and have in game limit)

2. Absolute lowest response time: Uncapped + Reflex/AntiLag

3. Last: Capped

So the 1st option at worst it adds 1-2ms of delay from your results?

When I run the 1st option with Anti Lag, it goes to exactly 280 with 90% usage when idle but will go below throughout the game, is that an issue? I think in the comments you suggested either use reflex or manually set limit, but if i use reflex it is not -3 below monitor like the manual limit, however will dip below 280 throughout the game

Just wondering if i have this right here, thanks

fishman099
Member
fishman099

Hey all, just wanted to post to say thanks for the guide. Implemented as described a long time ago (took several reads lol) but still works superbly well today.

Wanted to also post for those newly discovering this guide.

My set up:

LG Oled B3
Windows 11 (but worked on 10)
RTX4070ti super
Ryzen 5700x3d
32gb ram
2xNvMe

I have my control panel set to:

Gsync enabled for both full screen and borderless
Desktop/game res: 1440p/120hz
LLM: on
Max frame rate: 114fps
Gsync: on
Vsync: on

In game:

Vsync: off

From the getgo, I know gsync engages as the LG (when in game mode) shows the gsync symbol.

So I’m a nerd, been gaming for years but was a total noob when it came to VRR/Gsync. I either never had the kit that allowed me to even experiment or I read basic guides online that lacked context or understanding of how it worked.

However as I’ve upgraded my rig THIS guide has been a godsend.

I think it’s worth saying that this ‘process’ is NOT a magic bullet as jorimt and the mods state several times. It doesn’t make frames or increases FPS BUT what it does do, for me, is allow my games to run at a FPS below my refresh rate that minimises stutter and maximises smoothness.

Also worth bearing in mind is the point that is made repeatedly, that you may, at some points, have to compromise on either resolution OR eye candy. My 4070ti super is potent but I run EVERYTHING at 1440p. Some would say compromise, but I disagree. A relatively consistent 1440p@120hz with plenty of eye candy is much more preferable than a constant 4k@60hz but lowered settings for me (YMMV).

Similarly, in my experience, to gain the most advantage from VRR/gsync frame rates need to be as much past 60 as possible – hence the 1440p/120hz decision.

My test games were always Sensuas Saga (Hellblade2) and Alan Wake 2 primarily because they played v.nicely with Gsync and are v.graphically challenging.

I use both DLSS and/or Frame Gen if required when gaming and tbh it is a flawless experience when coupled with VRR/Gsync. Id hit 90- 114fps on AW2 but because of Gsync it would always run lovely and smooth. Also I’m quite sensitive to input latency but having followed this guide I can honestly say I’ve not noticed any significant increase!

Anyway apologies for the wall of text, thought it might help peeps who are new to this to see that even a Gsync novice can make this work as intended. Just temper those expectations and follow the guide 👍

Ps thanks to jorimt for effort in putting this guide together – awesome!!

rubbahbandman
Member
rubbahbandman

One other thing, LLM should be disabled.

rubbahbandman
Member
rubbahbandman

I may have misunderstood your comment, but I think your settings are not quite optimal based on the g-sync guide.

First, it is a minor difference, but there really isn’t a need to cap your max framerate to 114fps on a 120hz panel. You might as well increase it to 117fps.

Secondly, this is a bigger issue, but g-sync should not be enabled for borderless/windowed mode. This can hurt performance by 3-5%+ which isn’t the end of the world, but why take the performance hit for such a minor benefit. Maybe if you are a streamer frequently going between windows, but the guide recommends this setting remain unchecked.

fishman099
Member
fishman099

@rubbahbandman – thanks for taking the time to respond 🙂

Fair points made but for clarity:

1. I engage LLM as some games don’t have reflex. My understanding of the guide jorimt has created is, if a game does have reflex and I enable it then it disengages the LLM setting in NVCP anyway? Also It’s worth noting that, as a rule, I don’t engage reflex when I set up my settings in game. In my experience there have been occasions where it causes more issues 8n game than it solves. However if I engage frame gen then the game will ordinarily auto engage reflex anyway.

2. Setting my refresh -6fps from my 120hz, for me, ensures that I never go above my refresh rate thus disengaging gsync. When I first set up using this guide I was set at 117/120 but occasionally my frames would bounce up to and sometimes over the 120? As per the guide I felt it better to guarantee that gsync stayed engaged by definitively setting it low enough to never breach my 120hz.

3. Borderless/windowed mode. I rarely play older stuff – sometimes games from the recent past. Where I am able, in those games, I select fullscreen this ensuring gsync is engaged. Conversely in most modern games I’ll select either fullscreen or borderless/windowed. As Jorimt states, the modern riff on this display selection in games means that gsync remains active, with little, if any, performance hit. (The better implementation of window/borderless was also a reason I moved over from W10 to W11).

Anyway, thanks for the input. It’s good to explore our settings and discuss them as, for me, it allows for better clarity on the subject!!

For better or worse I’m lazy so whilst I acknowledge that there are settings that should be engaged/disengaged per game I find it easier to set in NVCP and forget lol. I’ve yet to see a case in 18+ months where I’ve had to tweak anything but YMMV 🙂

rubbahbandman
Member
rubbahbandman

@fishman099

Thanks for the clarification. I see where you’re coming from now and think you have a better understanding of the guide than myself. I leaned a bit too hard on some outdated information.

Out of curiosity, how did you notice your frames bouncing over 120 and which GPU model are you using? I have a 5090 and may take a more similar approach similar to yours in case my gsync is also disengaging at times (even with a 117 fps cap).

As for the borderless/windowed mode, I did not realize this was more of a legacy issue, and similarly, LLM seems to function well now (under GPU limited conditions), so this is good for me to know.

Thanks again for your response!

fishman099
Member
fishman099

@rubbahbandman – Jorimt has answered your queries – better than I could 🤣🤣

But as layman I sorta played around with the frame rate limiter. I can’t remember if it was Jorimts guide or something I read elsewhere but my logic was that the difference (for me) between 117 and 114 was unmeasurable in real time terms – so thought I might as well ensure that the FPS doesn’t bounce?

In relation to Jorimts comment – I do actually use afterburner and understand that it’s entirely possible I was getting fakes positives but I also found it was potentially happening on a game by game basis!! Locking it to 114 just allowed me to not worry 😀😀

Btw – love the 5090 bro – what a monster of a gpu that is!!!

wpDiscuz