G-SYNC 101: Optimal G-SYNC Settings & Conclusion


Optimal G-SYNC Settings*

*Settings tested with a single G-SYNC display (w/hardware module) on a single desktop GPU system; specific DSR, SLI, and multi-monitor behaviors, as well as G-SYNC laptop display and “G-SYNC Compatible” display implementation, may vary.

Nvidia Control Panel Settings:

  • Set up G-SYNC > Enable G-SYNC, G-SYNC Compatible > Enable for full screen mode.
  • Manage 3D settings > Vertical sync > On (Why?).

In-game Settings:

  • Use “Fullscreen” or “Exclusive Fullscreen” mode (some games do not offer this option, or label borderless windowed as fullscreen).
  • Disable all available “Vertical Sync,” “V-SYNC,” “Double Buffer,” and “Triple Buffer” options.
  • If an in-game or config file FPS limiter is available, and framerate exceeds refresh rate:
    Set (a minimum of) 3 FPS limit below display’s maximum refresh rate (57 FPS @60Hz, 97 FPS @100Hz, 117 FPS @120Hz, 141 FPS @144Hz, etc).

RTSS Settings:

  • If an in-game or config file FPS limiter is not available and framerate exceeds refresh rate:
    Set (a minimum of) 3 FPS limit below display’s maximum refresh rate (see G-SYNC 101: External FPS Limiters HOWTO).

OR

Nvidia “Max Frame Rate” Settings*:

*Introduced in Nvidia driver version 441.87

  • If an in-game or config file FPS limiter is not available and framerate exceeds refresh rate:
    Set “Max Frame Rate” to “On,” and adjust slider to (a minimum of) 3 FPS limit below display’s maximum refresh rate.

Reflex* Settings:

*This setting is considered Low Latency Mode’s replacement, and will override it, regardless of what LLM is set to in the NVCP.

  • If framerate does not always reach or exceed refresh rate, and Reflex is available:
    Set Reflex to “On” or “On + Boost” (“Boost” ensures the GPU doesn’t drop below its base boost clocks, similar to NVCP “Prefer maximum performance”). When combined with G-SYNC + NVCP V-SYNC, this engine-level limiter will 1) automatically limit the framerate to ~59 FPS @60Hz, ~97 FPS @100Hz, ~116 FPS @120Hz, ~138 FPS @144Hz, ~224 FPS @240Hz (etc) whenever the framerate can be sustained above the refesh rate, and 2) dynamically monitor and limit the framerate whenever it can’t be sustained above the refresh rate to prevent the extra pre-rendered frames that would be generated in an otherwise GPU-bound scenario.

Low Latency Mode* Settings:

*This setting is not currently supported in DX12 or Vulkan.

  • If an FPS limiter (such as in-game, config file, RTSS, and/or Nvidia “Max Frame Rate”) is not desired or available, Reflex is not available, and framerate exceeds refresh rate:
    Set “Low Latency Mode” to “Ultra” in the Nvidia Control Panel. When combined with G-SYNC + NVCP V-SYNC, this setting will automatically limit the framerate (in supported games) to ~59 FPS @60Hz, ~97 FPS @100Hz, ~116 FPS @120Hz, ~138 FPS @144Hz, ~224 FPS @240Hz, etc.
  • If an FPS limiter is already in use (such as in-game, config file, RTSS, and/or Nvidia “Max Frame Rate”), Reflex is not available, and framerate does not always reach or exceed refresh rate:
    Set “Low Latency Mode” to “On.” Unlike “Ultra,” this will not automatically limit the framerate, but like “Ultra,” “On” (in supported games that do not already have an internal pre-rendered frames queue of “1”) will reduce the pre-rendered frames generated in GPU-bound situations where the framerate falls below the set FPS limit.

Windows “Power Options” Settings:

Windows-managed core parking can put CPU cores to sleep too often, which may increase frametime variances and spikes. For a quick fix, use the “High performance” power plan, which disables OS-managed core parking and CPU frequency scaling. If a “Balanced” power plan is needed for a system implementing adaptive core frequency and voltage settings, then a free program called ParkControl by Bitsum can be used to disable core parking, while leaving all other power saving and scaling settings intact.

Blur Buster's G-SYNC 101: Input Lag & Optimal Settings

Mouse Settings:

If available, set the mouse’s polling rate to 1000Hz, which is the setting recommended by Nvidia for high refresh rate G-SYNC, and will decrease the mouse-induced input lag and microstutter experienced with the lower 500Hz and 125Hz settings at higher refresh rates.

mouse-125vs500vs1000

Refer to The Blur Busters Mouse Guide for complete information.

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.

Maximum Pre-rendered Frames*: Depends

*As of Nvidia driver version 436.02, “Maximum pre-rendered frames” is now labeled “Low Latency Mode,” with “On” being equivalent to MPRF at “1.”

A somewhat contentious setting with very elusive consistent documentable effects, Nvidia Control Panel’s “Maximum pre-rendered frames” dictates how many frames the CPU can prepare before they are sent to the GPU. At best, setting it to the lowest available value of “1” can reduce input lag by 1 frame (and only in certain scenarios), at worst, depending on the power and configuration of the system, the CPU may not be able to keep up, and more frametime spikes will occur.

The effects of this setting are entirely dependent on the given system and game, and many games already have an equivalent internal value of “1” at default. As such, any input latency tests I could have attempted would have only applied to my system, and only to the test game, which is why I ultimately decided to forgo them. All that I can recommend is to try a value of “1” per game, and if the performance doesn’t appear to be impacted and frametime spikes do not increase in frequency, then either, one, the game already has an internal value of “1,” or, two, the setting has done its job and input lag has decreased; user experimentation is required.

Conclusion

Much like strobing methods such as LightBoost & ULMB permit “1000Hz-like” motion clarity at attainable framerates in the here and now, G-SYNC provides input response that rivals high framerate V-SYNC OFF, with no tearing, and at any framerate within its range.

As for its shortcomings, G-SYNC is only as effective as the system it runs on. If the road is the system, G-SYNC is the suspension; the bumpier the road, the less it can compensate. But if set up properly, and run on a capable system, G-SYNC is the best, most flexible syncing solution available on Nvidia hardware, with no peer (V-SYNC OFF among them) in the sheer consistency of its frame delivery.

Feel free to leave a comment below, resume the discussion in the Blur Busters Forums, or continue to the Closing FAQ for further clarifications.



2761 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
rec0veryyy
Member
rec0veryyy

hi, i have been playing cs2 for several weeks, my monitor is 1440p 144hz with gsync compatible, in the nvcp i have gsync on + vsync on, i also limit the fps to 141 inside the nvcp, then inside the game vsync off and the nvidia reflex off, i get 138fps as expected and everything works fine, but i have a question, should i play like this or disable the vsync in the nvcp for cs2 to go to 200 or 300fps? because as I understand the more fps the less frametime in ms, now I would have about 7.2ms but if I unlimit it and I go to 250fps I would have 4ms, is this really so and would it make any difference?

HarmVJ
Member
HarmVJ

So windows 10 has something called VRR in the graphics setting. Should it be used in tandem with G-Sync + NVCP Vsync. Some sources and review just say to turn it on along with g-sync.

newbieguys
Member
newbieguys

I have a 144hz monitor asus vp24qgr with Adaptive-Sync (FreeSync™) elmb with vga 1660 is it better to use G-SYNC + NVCP V-SYNC + LLM Ultra + cap 141hz in valorant to reduce low input?

rawaimer
Member
rawaimer

Thanks a lot for the research! I’m using a FreeSync monitor and an amd graphics card. In the driver settings, you can select 4 options for setting up vertical synchronization: 1) Always on 2) on if not specified by the application 3) off if not specified by the application 4) always off. If I enable freesync in the driver, enable vsink in the game, then which option should I select in the driver? Well, the opposite situation: if I want to disable vsync in the game and want to enable it in the driver, how should I enable it? 1) always enable? or 2) enable if not specified by the application? Well, I still wanted to clarify which option is preferable in your opinion, to enable vsink in the game or in the driver settings? Battle(non)sense says it’s better to enable it in the game, because there may be some optimizations inside the engine

БэглSmagle
Member
БэглSmagle

Hello everyone, I have a question about the range of g-sync (I write through a translator, so I apologize for my English :)). The operating range of my g-sync monitor is 48-165 Hz, but by turning on the g sync pendulum program, and turning on the Hz display indicator built into the monitor, I noticed that the actual operating range of g-sync is 56-165 Hz, if the fps drops below 56, then frames begin to split in two, no matter how much I searched for information on this matter, I did not find anything, does anyone have an answer on this issue? And yet, g-sync does not work if you turn on the monitor refresh rate of 60Hz, BUT using the program
Custom Resolution Utility (CRU), I changed the range of g-sync to 22-165hz, and g-sync started working at 60hz, not an understandable anomaly. Sorry if the question is off topic, but it’s interesting to know how it works

wpDiscuz