Next

G-SYNC 101: Control Panel

Published Jun 20, 2017 by in: G-SYNC

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.”

Next

3852 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
Shadeless
Member
Shadeless

So when using GSync on a 165Hz monitor with FPS capped at 160 FPS (ingame limiter) and GSync + Vsync ON (in Nvidia driver, off in game), is using low latency mode “on” or “ultra” better to decrease input lag?

I’d guess using ultra would result in less input lag but the battlenonsense video made me question if that would actually be the case considering my GPU usage is lower than 95% almost all the time and based on his testing “on” resulted in lower lag than “ultra”…

Just wondering if it’s similar with Gsync or if ultra is better for the lowest latency there like at > 95% GPU usage when you use no sync.

I feel like low latency “ultra” gives me a slightly snappier response when using GSync but that could just be placebo…

Like0Vote Down 
6 years 9 months ago
jorimt
Author
jorimt

It depends on how well your system is able to sustain the framerate above the set FPS limit, and if the set FPS limit is preventing the GPU from maxing out.

As for Low Latency Mode “On” vs. “Ultra,” “On” is equivalent to “Maximum pre-rendered frames” at “1,” and contrary to popular belief, that override isn’t necessarily respected in every game, and there isn’t really an obvious way to tell when it is.

“Ultra” on the other hand, according to Nvidia, basically uses a predictive function they describe as (and I quote) “‘just in time’ frame scheduling, submitting frames to be rendered just before the GPU needs them”

So, if you’re using G-SYNC with an FPS limiter, whether or not the framerate exceeds the limit at all times, or hovers below it at points, “On” is probably the safest to use, as, with what little data is available, the extra timing functionality in “Ultra” appears to possibly have a minor detrimental effect on input lag when compared to “Off” in non-GPU-bound situations, at least according to Battle(non)sense’s results.

To sum-up, the answer heavily depends on the given system, game, and whether you’re GPU-bound at any given point.

That said, the new Low Latency Mode settings (and pre-rendered queue settings in general) are really only useful in GPU-bound situations (at which point they can reduce input lag by 1 frame, at most), so if you’re playing games using G-SYNC with the framerate sustained above your set FPS limit, and your set FPS limit is preventing your GPU from maxing out, these settings don’t really matter all that much.

Like2Vote Down 
6 years 9 months ago
Shadeless
Member
Shadeless

Ok, thank you!

Like1Vote Down 
6 years 9 months ago
jorimt
Author
jorimt

No problem 😉

Like0Vote Down 
6 years 9 months ago
tanzimfh
Member
tanzimfh

Hi, this was undoubtedly answered either in the article (which is exceptionally written btw) or the FAQ, but I can’t seem to understand the point of an FPS limiter fully.

I know that going over the frame rate of the monitor turns G-Sync off, but since V-Sync kicks in, shouldn’t we still get tear-free frames at the monitor’s frame rate? I can’t think of why there would be stuttering either since there is always a frame ready by each scan out.

I’m on a 144hz display with FreeSync, and for Rainbow Six Siege specifically, my 2060 can pump out around 250 fps, and I’m wondering if using G-Sync with an FPS limiter will give me any benefit over simply using V-Sync. I actually just got the monitor and my Displayport cable is yet to arrive, and I’m not sure if I should try to use G-Sync or stick to V-Sync and graphics settings that allow for >144 FPS at all times. Is there any real input lag when doing this (except the latest partway rendered “tear” frame that V-Sync avoids), and if so, why? I feel like I see an input lag much higher than just one frame, which makes me want to try adaptive sync, but I’m not sure. Thanks in advance!

Like1Vote Down 
6 years 9 months ago
jorimt
Author
jorimt

Hi, this was undoubtedly answered

Indeed it has been. If you don’t want to read the entire article, I suggest you (at minimum) read the third FAQ entry on the below page:
https://blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/15/

I’m on a 144hz display with FreeSync

I assume it’s G-SYNC compatible then, which means there can be differences between it and G-SYNC “proper” (with a hardware module), but the general rules are the same (V-SYNC option paired with G-SYNC for zero tearing + FPS limit below the refresh rate).

I’m wondering if using G-Sync with an FPS limiter will give me any benefit over simply using V-Sync

G-SYNC with an appropriate FPS limit will always give you an input lag (and frame pacing) benefit over standalone V-SYNC inside its range; at 144Hz, G-SYNC typically has about 3-4 frames of input lag reduction over uncapped V-SYNC.

Like2Vote Down 
6 years 9 months ago
tanzimfh
Member
tanzimfh

Thank you for the prompt and informational reply. I have actually read the entire article; I’m simply having trouble understanding. If you don’t mind, I’m just confused about why V-Sync creates that 3-4 frame input lag when it’s being fed twice as many frames as it needs to adjust to. I understand G-Sync providing much better input lag and frame pacing in its range, but I don’t understand why V-Sync would create an input lag when our FPS is higher than the monitor’s refresh rate, when the technology exists for this very purpose. If G-Sync can cut down the input lag by 3-4 frames (using the technology I don’t quite understand despite reading that part), why doesn’t V-Sync use that technology, or does that require the G-Sync module? Also, my monitor isn’t “G-Sync compatible” either; it’s simply compatible in the sense that it has adaptive sync. I don’t care if I don’t have that 3-4 frame input lag benefit over regular V-Sync at 144hz since I intend to cap it at 141 FPS anyway, but does the fact that I don’t have the G-Sync module add input lag, or am I fine as long as there are no artifacts? Thank you for your help.

Like0Vote Down 
6 years 9 months ago
jorimt
Author
jorimt

Also, how does G-Sync provide that 3-4 frame benefit when it simply uses V-Sync at 144hz? Does this require the official G-Sync module?

Oh, and no, a G-SYNC module isn’t required for the input lag benefit with any form of adaptive-sync/VRR.

As I stated in the first part of this article:

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.

In other words, The GPU having to wait on the display (V-SYNC) causes the additional sync-induced input lag. In swapping this scenario around (display synced to the GPU), sync-induced input lag is reduced.

Like2Vote Down 
6 years 9 months ago
jorimt
Author
jorimt

I actually answered this specific question in the comments here a while back. Quoting below:

…Even though [standalone V-SYNC or G-SYNC + V-SYNC without an FPS limit] visibly “caps” the framerate to the refresh rate, double buffer V-SYNC (with or without G-SYNC) doesn’t prevent delayed frame delivery like a framerate limiter does, but, in fact, causes it.

For instance, at a sustained 200 FPS, each frame is rendered in 5ms. However at 144Hz with G-SYNC and/or V-SYNC, the fastest each frame can be delivered tear-free to the display is 6.9ms. So, with 144Hz G-SYNC + V-SYNC at 200 FPS with no FPS limiter (which effectively behaves like standalone V-SYNC at that point, as G-SYNC can no longer adjust the refresh rate to the framerate), each frame will be rendered in 5ms, but each will be delayed 1.9ms before being delivered as to match the max 144Hz scanout cycle of 6.9ms per. This delay adds up over a period of frames, eventually over-queuing the buffers, and thus causes the extra input lag.

A framerate limiter, however (in-game or external), ensures that the maximum render time of each frame is within the maximum delivery time of the given refresh rate, preventing this issue entirely.

Standalone V-SYNC OFF is the only thing that is going to give you the benefit of higher framerates above your refresh rate, and it has to be pretty high above the refresh rate to make any significant input lag difference (at crosshair-level) when compared to G-SYNC within its range, and even then, you still have to deal with the constant tearing (if that bothers you):
https://blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/9/

Like2Vote Down 
6 years 9 months ago
tanzimfh
Member
tanzimfh

That was great, thank you. Now I understand the input lag (and I’m guessing a stutter when it skips a frame once that 1.9ms adds up to 7.6ms over 4 frames?) In that example, however, couldn’t the card simply wait a little less than 1.9ms after a 5ms frame render (and keep adjusting the wait duration after each frame to hit the target) and render a more up-to-date frame and thus avoid the lag? Or would that be impossible to achieve with such precision? Either way, the benefits of G-Sync in its range over V-Sync even outside its range is very clear to me now, and I’ll be using G-Sync when my cable arrives. Thank you for writing this amazing article and answering my questions! This was very helpful especially because not many people seem to use adaptive sync or understand its benefits to this extent.

Like0Vote Down 
6 years 9 months ago
jorimt
Author
jorimt

The problem with quick and easy answers is they aren’t always complete ones; that V-SYNC scenario is just to start giving you an idea on how it causes input lag.

Bottom-line, is uncapped V-SYNC is based on older input reads, and G-SYNC is based on newer input reads. The higher the FPS is above the refresh rate with V-SYNC, the worse the input lag is, as your inputs are being read at lower and lower render times, but being forced to be shown at the same intervals of the current max refresh rate regardless.

Now I understand the input lag (and I’m guessing a stutter when it skips a frame once that 1.9ms adds up to 7.6ms over 4 frames?) In that example, however, couldn’t the card simply wait a little less than 1.9ms after a 5ms frame render (and keep adjusting the wait duration after each frame to hit the target) and render a more up-to-date frame and thus avoid the lag?

Long story short, is that the only result of the card waiting will be more input lag, unfortunately.

As for V-SYNC skipping/repeating frames, that only occurs with framerates below the refresh rate (another thing G-SYNC fixes). With framerates above the refresh rate, V-SYNC looks exactly the same as G-SYNC does within its range, V-SYNC just has much higher input lag (due to the aforementioned reasons).

Standalone V-SYNC can have close to the same amount of input lag that G-SYNC does if you also cap it below the refresh rate (it only requires 1 frame below, and optimally a fraction of a frame via RTSS), but again, since the GPU is a slave to the fixed delivery intervals of the display with V-SYNC, you’ll continually skip up to a frame (as described in the article), which will incur extra input lag (and occasional stutter) over G-SYNC.

And that’s only if you can maintain your framerate above the set limit 99% of the time with V-SYNC. If your system drops below it at any point, you get the framerate locked to half of your refresh with double buffer, and if you use triple buffer, that extra buffer causes more lag, and you still get stutter due to repeat frames below the refresh rate.

Basically, when it comes to standalone V-SYNC, you can have perfect frame pacing (V-SYNC + framerates above the refresh rate), but with lots of extra input lag, or lower input lag, but with imperfect frame pacing (V-SYNC + FPS below the refresh rate).

G-SYNC gives you both perfect frame pacing and lower input lag (virtually the same as V-SYNC OFF at the same framerate within the refresh rate), and with any framerate (variable or not) within its range.

Like1Vote Down 
6 years 9 months ago
tanzimfh
Member
tanzimfh

I’ll have to do more digging to understand V-Sync completely, but thanks for making the basics a lot clearer for me. As for now I’ll be using G-Sync to avoid the input lag. Also, do you recommend running games at a higher-than-refresh-rate FPS at all times with a cap at 141, or should I turn the graphics up so that I get around 120-140 FPS? Will those <20 frames make a noticeable impact since G-Sync is on anyway?

Like0Vote Down 
6 years 9 months ago
jorimt
Author
jorimt

You definitely want the FPS limiter to be the framerate’s limiting factor, where possible; if you make the GPU the limiting factor, you will then be adding GPU-induced input lag, which is obviously a whole other subject.

Optimally, for the lowest input lag, you don’t want to max out your GPU usage either.

So not only does a framerate limiter reduce sync-induced input lag AND keep G-SYNC within it’s range (when the framerate can otherwise exceed the refresh rate), it also reduces system-induced input lag, so long as it is preventing the GPU usage from maxing out (<99%).

This article only covers one "link" in the "chain" that is input lag:

comment image

Like1Vote Down 
6 years 9 months ago
tanzimfh
Member
tanzimfh

My cable arrived and there is a massive difference with adaptive sync. In fact, I can’t go back after only a few rounds. I’ll be setting a limiter on all my games and playing everything with G-Sync on. Thank you.

Like1Vote Down 
6 years 9 months ago
jorimt
Author
jorimt

Great to hear 😉

Like1Vote Down 
6 years 9 months ago
primeknight
Member
primeknight

Hello so I looked through the whole FAQ and comments and didnt seem to have any answer to the issue I’m having so here it is.

So I’m using a 240hz monitor the ASUS ROG Swift PG258Q and I have g-sync enabled for windowed and fullscreen mode. I have Vsync enabled in the NVCP and totally off in the game I’m playing which is Apex Legends. I also have Low latency mode on Ultra and preferred refresh rate on highest available. Since I often go above 240 fps in game I also have RTSS set to 237. My problem is with vsync on in the NVCP my fps is being capped at 60 for some reason and when it’s off it goes to the normal 200+ fps. Just wondering why this is happening? Also with RTSS set to 237 my fps still fluctuates above that into the 240s even though when I see other streamers using it, it sits at a static number and doesnt budge.

Thanks in advance for any help!

Like0Vote Down 
6 years 9 months ago
jorimt
Author
jorimt

I assume you’re using the game’s “+fps_max unlimited” command then? Because otherwise, I believe the game caps to a max of 144 FPS.

Your issue could be caused by a variety of factors (one of them being a multi-monitor setup). Apex Legends in particular has also been known to act strangely above its default 144 FPS cap (especially when it was first released).

That said, this comments section isn’t intended for long-form troubleshooting, so if you would create a new thread in our forums, I (and others) will be happy to help you try and narrow down the issue there:
https://forums.blurbusters.com/viewforum.php?f=2

Like1Vote Down 
6 years 9 months ago
primeknight
Member
primeknight

Thx for the reply. I will post on the forums but they removed that 144 fps cap long ago and that fps command is no longer needed and like I said I have no problem getting to 240 fps normally

Like0Vote Down 
6 years 9 months ago
jorimt
Author
jorimt

Yeah, I haven’t really played Apex Legends since its initial release, so if they’ve updated anything regarding the original 144 FPS hard in-game cap, I wouldn’t know about it.

I’ll check your thread in the forums.

Like0Vote Down 
6 years 9 months ago
Thorulfr
Member
Thorulfr

Hello – I’m following your guide and just want to confirm I’m doing the right thing with my 144Hz monitor – the game doesn’t really reach 144 frames per second.
Heroes of the Storm:
G-sync on
Nvidia Gysnc On
Fullscreen
In-game V-sync off
Refresh Rate (in windows) set to 144hz
Refresh Rate (in game option) set to 144hz
In-Game framerate limiter set to 87 through a command-line option.
Maximum Pre-rendered frames set to 1 in Nvidia Control Panel.

In game I get 90fps, sometimes 89 and sometimes 91.] My graphics card can push between 90-144 frames in Heroes at 1440p but it’s pretty variable so I chose 90 as a good target at the low end.

Feels ok but just wanted to be sure I have this correct for maximum frames and lowest input lag. In your section 13 about hidden benefits you explained that limiting to 60fps on a 144hz monitor reduced input lag, but that the monitor is producing scans at 144hz even though only 60 are ‘new’. I thought G-Sync actually dropped the monitor’s refresh rate to match the frame rate (so in my case, 90?)>

Just wondering if I should set my refresh rate to 90Hz to get optimal frame pacing.

Like0Vote Down 
6 years 9 months ago
jorimt
Author
jorimt

I forgot to add, regarding this:

In-Game framerate limiter set to 87 through a command-line option.

The -3 FPS limit is relative to the current max physical refresh rate of your display, and is only required to keep the FPS within the G-SYNC range.

At 144Hz, you effectively have a 0-141 FPS G-SYNC range, so unless you’re capping at 87 FPS for consistency reasons, you can raise the FPS limit to 90, because with an 87 FPS limit @144Hz, you’re already at -57 FPS (no reason for a -3 offset of your desired FPS limit when you’re well within the G-SYNC range).

Like0Vote Down 
6 years 9 months ago
jorimt
Author
jorimt

You’re settings look good to me.

As for dropping your physical refresh rate to 90Hz with G-SYNC on a 144Hz monitor, don’t, it will increase input lag.

G-SYNC “adjusts” the refresh rate by controlling how many times the scanout (the process that physically draws each frame, pixel by pixel, left to right, top to bottom on-screen) is repeated per second, but G-SYNC can’t change the delivery “speed” of each individual scanout cycle.

This “speed” is dictated by the current physical refresh rate; at 144Hz, the delivery speed of each frame is 6.9ms, at 90Hz, it’s 11.1ms, regardless of framerate.

With G-SYNC, dropping your physical refresh rate to 90Hz will not improve your frame pacing when compared to 90 FPS @144Hz. In fact, not only will the scanout now be slower at the same framerate, but you’ll need to limit your FPS to 87 @90Hz to avoid the G-SYNC ceiling (V-SYNC input lag).

So to sum up, it you’re looking for the lowest input lag, and the most consistent experience (some prefer lower fixed framerates to higher variable framerates with G-SYNC), keep your monitor at its max physical refresh rate, and limit the FPS to your system’s lowest average in the given game.

Like0Vote Down 
6 years 9 months ago
Thorulfr
Member
Thorulfr

Thank you for your detailed answer! Most interesting.

So, next question, and this one is a little more complicated – does the interval at which this pacing occurs matter do you think? I.e if the frame pacing is 6.94ms because of the 144Hz refresh rate, and with a frameratecap at 90 (11.11ms) – won’t every third/fourth scannout (roughly) be repeated?
Essentially at 22.22ms the GPU will have delivered the second frame, but the monitor only just started it’s fourth scannout and won’t be able to actually deliver the frame until the fifth scannout. Would it look better if this pacing was even?

I guess it’s moot because it looks totally fine – maybe I should just do some testing!

Like1Vote Down 
6 years 9 months ago
jorimt
Author
jorimt

That’s precisely what G-SYNC was created to address; it synchronizes the display’s VRR (variable refresh rate) to the GPU’s render rate, which prevents the frame pacing issues you’re describing entirely.

Like1Vote Down 
6 years 9 months ago
Phroster
Member
Phroster

Why is it, that in most games, borderless fullscreen + gsync, gives worse results then exclusive full screen mode? (uneven frametimes, micro stutters)
Using a frame limiter to set the framerate -3 below the refresh rate makes it even worse when using borderless fullscreen.

I did find that G-sync + Fast sync + borderless fullscreen seems to give better results in some games. Still limiting the frame rate in borderless fullscreen, introduces microstutters.

Why is borderless fullscreen so unreliable with gsync enabled?

Like1Vote Down 
6 years 10 months ago
jorimt
Author
jorimt

I’m afraid I currently have no clear, definitive answer for that; borderless fullscreen G-SYNC mode is already kind of a DWM hack to begin with.

I personally don’t use it often (in fact, only when there’s no other option), but I’ve found frametime performance in that mode is usually game (sometimes even system) specific. You also want to verify that G-SYNC is actually functioning, as there’s a chance it might not in certain games, even with that mode enabled.

You can also try enabling/disabling fullscreen optimizations per game, as that can occasionally have an unexpected effect on G-SYNC functionality as well.

Whether these issues are down to Nvidia’s driver, Windows itself, or a mix of both, I, for one, am simply not sure.

Like0Vote Down 
6 years 10 months ago
wpDiscuz

Related Content

Featured Content

Blur Buster Forums

Blur Busters Forums

TestUFO Motion Tests

TestUFO Motion Tests