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

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
Tavo
Member
Tavo

Hi! Thanks for always replying. I apologize in advance if this question has already been asked, but it’s something I can’t seem to clarify. I have a stock 10700k, RTX 3070 Ti, and a GSYNC-compatible 165Hz monitor. I mainly use it to play World of Warcraft retail. I use G-Sync On + NVCP V-Sync On. My question is: should I use RTSS as an FPS limiter if I use Reflex in the game? Which Reflex option do you recommend? thanks u so much!

Like1Vote Down 
10 months 23 days ago
jorimt
Author
jorimt

My question is: should I use RTSS as an FPS limiter if I use Reflex in the game?

Not enough information to answer. What is your goal?

Reflex + G-SYNC + NVCP V-SYNC already sets an FPS limit below the refresh rate to ensure VRR remains engaged, so if that’s all you’re using an FPS limiter for, Reflex will suffice in that scenario, and it will also prevent extra render queue latency (separate of the sync latency VRR prevents) whenever your GPU usage is 99%+.

If, however, you’re targeting a specific average framerate, and your system can’t reach it at all times, then you may want to set a manual limit with an internal or external FPS limiter that your system can sustain most of the time instead.

I.E. WoW is jumping anywhere from 75-165 FPS, but you prefer a constant 80, etc.

Like0Vote Down 
10 months 23 days ago
anthony3192
Member
anthony3192

I’m looking for a dry and precise answer, if I set the reflex active, with gsync and vsync from the ncp, how should I keep the low latency mode active from the ncp? I keep it on ultra. I ask you this because for games that don’t have reflex cameras I’m forced to set the fps cap to obtain the lowest possible latency? Or is it also okay to enable gsync+vsync+ultra low latency? Another question, I read that you wrote that ultra low latency mode could have worse performance for 1%L, how do you recommend setting it? How did you set it all up? I would like a permanent setting so I can forget about it.

Like0Vote Down 
10 months 28 days ago
jorimt
Author
jorimt

I’m looking for a dry and precise answer

I can’t promise that, since some of your questions require more complex branching answers.

if I set the reflex active, with gsync and vsync from the ncp, how should I keep the low latency mode active from the ncp? I keep it on ultra.

Barring any driver and/or game-specific bugs that may occur, Reflex, when enabled in-game, overrides NVCP LLM settings, regardless of what it’s set to.

I ask you this because for games that don’t have reflex cameras I’m forced to set the fps cap to obtain the lowest possible latency?

If Reflex isn’t available, and your system can’t reach your target average framerate without the GPU usage reaching 99%+, for a second-best option, you will need to set a manual limit that prevents it instead.

I.E. VRR handles sync latency (for framerates within the refresh rate), while keeping your GPU usage below 99% via automatic methods like Reflex, or manual methods like FPS limiters, handles GPU-bound latency separate of the sync latency VRR addresses (which I’ve explained dozens of times in the comments here).

Or is it also okay to enable gsync+vsync+ultra low latency?

Another question, I read that you wrote that ultra low latency mode could have worse performance for 1%L, how do you recommend setting it?

LLM is inferior to both Reflex and a manual FPS limit where reducing GPU-bound latency is concerned, and, again, frametime issues are possible with LLM, whereas they aren’t as much with the other two methods.

How did you set it all up?

My personal settings vary by game, but I almost never use LLM; I have it off globally. I instead use Reflex or a manual FPS limit to prevent GPU-bound scenarios.

I would like a permanent setting so I can forget about it.

There really isn’t one, unless you are okay with accepting that some games may have specific issues that won’t work with your set-and-forget configuration.

Like0Vote Down 
10 months 28 days ago
anthony3192
Member
anthony3192

I’m sorry but for games that don’t have Reflex by deactivating LLM you don’t have much input lag? that’s what I don’t understand

Like0Vote Down 
10 months 28 days ago
jorimt
Author
jorimt

Reflex and ULLM each do two things when activated:

  1. Engage an automatic limiter that reduces the framerate below the refresh rate when combined with G-SYNC + V-SYNC to keep VRR engaged (in supported games/engines).
  2. Engage logic that reduces pre-rendered frames in the render queue whenever the GPU usage is 99%+.

#1 and 2 aren’t related to each other at all, and whenever VRR is disabled, Reflex and ULLM will only engage #2, and only whenever GPU usage is 99%+.

How Reflex and ULLM handle #2 differ.

Reflex does it by monitoring the GPU usage, and then dynamically limiting the framerate just below the achievable average to prevent 99% GPU usage.

ULLM, however, attempts to reduce the amount of pre-rendered frames in the render queue by delivering them “just-in-time,” but it can occasionally mistime this mechanic, potentially causing more stutter, since it will trigger a repeat frame if it misses the “just-in-time” window.

That, and since Reflex is at the engine-level and uses a dynamic framerate limiter instead of trying to manipulate the render queue directly, it can essentially prevent GPU-bound scenarios before they occur, resulting in 0 added latency from otherwise maxed GPU usage.

ULLM can only reduce GPU-bound latency by 1 to 1 1/2 frames in the best of cases, and again, with the risk of increased stutter.

That’s why I say a manual FPS limit that prevents maxed GPU usage is better than ULLM, as the manual limit mimics Reflex behavior, just with a static instead of dynamic limit.

Finally, to be very clear, the #2 behavior of Reflex and ULLM will not reduce latency further whenever GPU usage is naturally below 99%.

Like0Vote Down 
10 months 28 days ago
hentfreaka
Member
hentfreaka

Just to be sure: does it still not matter if i choose to Limit my fps via Nvidia (576.88) or RTSS?

Are both performing the same?

PS: I sometimes read Nvidia App might also cause frame time spikes. Any thoughts on that? I mainly use it for RTX HDR.

Like1Vote Down 
11 months 3 days ago
jorimt
Author
jorimt

Are both performing the same?

RTSS and NVMFR should still be similar to each other in both latency levels and frametime performance, but the behavior of each may vary by game/engine.

I.E. one could work without a “hitch” in x game, but then the other could wig out in the same game for some obscure reason or visa-versa.

I sometimes read Nvidia App might also cause frame time spikes. Any thoughts on that?

Never used it, so can’t speak specifically on that, but there’s always a possibility that external overlays and background processes may affect frametime performance.

Like2Vote Down 
11 months 3 days ago
Krazzeekane
Member
Krazzeekane

I can’t find any mention of what to do with the ‘Triple Buffering’ option in NVCP/NVPI. I know to disable any in-game triple buffering options, but bo I set it the NVCP option to on or off? I read it only works for OpenGL games which I do play sometimes as I like older games. Just wasn’t sure if it would make any difference one way or the other, and I can’t find anything recent on about it.

I use a g-sync capable display (LG-27GR83Q-B), and have followed all the other options you listed and everything is running great. Just unsure about the Triple Buffering option.

Like1Vote Down 
11 months 4 days ago
jorimt
Author
jorimt

Leave it off when using VRR.

Like3Vote Down 
11 months 4 days ago
tomatojuice
Member
tomatojuice

Why do you recommend disabling in game vsync in favour of Nvidia’s?

Like1Vote Down 
11 months 6 days ago
jorimt
Author
jorimt

The answer has been here since the article was first published in 2017:
https://blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/14/
 

Nvidia Control Panel V-SYNC vs. In-game V-SYNC

While NVCP V-SYNC has no input lag reduction over in-game V-SYNC, and when used with G-SYNC + FPS limit, it will never engage, some in-game V-SYNC solutions may introduce their own frame buffer or frame pacing behaviors, enable triple buffer V-SYNC automatically (not optimal for the native double buffer of G-SYNC), or simply not function at all, and, thus, NVCP V-SYNC is the safest bet.

There are rare occasions, however, where V-SYNC will only function with the in-game option enabled, so if tearing or other anomalous behavior is observed with NVCP V-SYNC (or visa-versa), each solution should be tried until said behavior is resolved.

Like4Vote Down 
11 months 6 days ago
wpDiscuz

Related Content

Featured Content

Blur Buster Forums

Blur Busters Forums

TestUFO Motion Tests

TestUFO Motion Tests