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.

Low Latency Mode* Settings:

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

  • If an in-game or config file FPS limiter is not available, RTSS is prohibited from running, a manual framerate limit is not required, and framerate exceeds refresh rate:
    Set “Low Latency Mode” to “Ultra” in the Nvidia Control Panel. When combined with G-SYNC + 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 in-game or config file FPS limiter, and/or RTSS FPS limiter is available, or Nvidia’s “Max Frame Rate” limiter is in use, 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 queue in GPU-bound situations where the framerate falls below the set (in-game, RTSS, or Nvidia “Max Frame Rate”) 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.



2035 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
domfak
Member
domfak

Hello,

Want to thank you for all the info in this page.
Also I have couple of questions:

I got RTX 3080 + 165hz monitor, I am having those tearing lines on my low side of display if I play with GSync + uncapped fps. Sometimes it feels like stuttering. So I decided to try your method.
But where are some issues in game COD: Warzone:

1) GSync On + Vsync ON + LLM (Ultra) + Reflex On + Boost – caps my FPS in game at 60. Why?

2) GSync On + Vsync FAST + LLM Ultra + Reflex On+ Boost – I can cap myself at 161fps as you proposed. And FPS are dipping from 140 to 161. Also with thise method I found that blur line in the bottom of the screen still exist.

What is difference between VSync ON / VSync Fast?
Will I get more input delay in this case?
Also can I feel that option with Gsync + Vsync has more input delay on my mouse or it is only placebo?

Thanks for an answer.

majkool
Member
majkool

1. So with 390Hz monitor input lag with GSYNC + VSYNC and 386fps game limitter is nearly the same like with GSYNC/VSYNC off and fps_max 0 in CSGO.
2. I know that with 240Hz monitor there is a few ms delay with these options but I think it’s still better to accustom to it and play on a pro level?

AgentDaumer
Member
AgentDaumer

G-SYNC reverts to V-SYNC behavior when it can no longer adjust the refresh rate to the framerate, 2-6 frames (typically 2 frames; approximately an additional 33.2ms @60 Hz, 20ms @100 Hz, 13.8ms @144 Hz, etc) of delay is added as rendered frames begin to over-queue in both buffers, ultimately delaying their appearance on-screen.

I’m surprised that a framerate limit just 2-3 FPS below the monitor’s refresh rate can actually prevent G-Sync from hitting that threshold and reverting to V-Sync behaviour. Using RTSS I noticed that a 140 FPS cap (in-game) will still allow the framerate to fluctuate and reach pretty high values, often higher than 160 FPS. Even a 120 FPS cap still exceeds 144 every couple seconds.
It happens intermittently of course, the frametimes are constantly fluctuating (as they should) and the average framerate is still respecting the limit.
However, wouldn’t those big spikes mean that G-Sync is frequently engaging and disengaging all the time? Am I missing something?

Unneverseen
Member
Unneverseen

How is the latency for competitive fps games with 141fps limit (i have 144hz monitor) and Gsync and nvcp vsync on? should i disable fps limit and nvcp vsync for less latency? also do you set Max Frame Rate, low latency mode, and vsync globally or per game basis? also i heard that fps limit improving latency depends on the game, some it might give worse latency some its better latency. thanks for the article

YormFatigue
Member
YormFatigue

Hello Jorimt, thanks for your article, it’s great, now I know more about this kind of Technology and am less confused of it.
But anyway, I want to confirm something, and hope you will answer it.
I use Freesync monitor 144HZ, based on what I learn, so it’s just the same as G-sync. When I play games, one thing I absolutely want to get rid of is microsutter, even after using VRR, I still have it to this day, when reading your article, I think I know the cause, and I know it may be unavoidable, but I want to be clear to it. So, these are my cases:
– When I play some games, I suffer occasional microsutter and sometime occasional tearing, of course I turn Freesync on, but it still remains as is, turning on V-sync will make that “occasional tearing” become microsutter as well, using fps limiter to limit the fps which is far lower than what point my specs can archive. My question is what makes that behavior? Is It the game’s problem that creates great frametimes variance and frametimes spikes? And additional info, some games I played have are kind of weird, that the lower fps is, the smoother the game is,
– There are also games that will present microstutter no matter what fps is, take an example of The Witcher 3, my specs can reach 60+ fps, so good idea that I should cap it just to 60 (I do it in almost game anyway) and it still has microstutter, then I tried to apply the weird way I state above, tried lowering fps, as low as I can play (well – 30fps), and still no good, microstutter is still there. So is it my system’s fault or the game’s fault?
And one last thing I want to share, based on what I’ve experienced so far (not read or learn), is I am pretty sure that fps limiter can somehow help Freesync in terms of smoothness, even it is below the targeted fps. I am talking about AMD framerate target control – FRTC for short, which is the smoothest framerate limiter (and It comes with the biggest latency), on my test, In the same game, in the same place of the game, I used 4 fps limiter: In-game, Chill with max-min equal, RTSS, FRTC, I saw that with FRTC, there is almost no microstutter no matter what fps, Chill and RTSS are pretty same as each other – comes with microsutter, but Chill does have less than RTSS and RTSS seems to have little smoother images when rotating camera, in-game is the father of microstutter.
I find that interesting, and I turn off Freesync to see what would happen. Well, with FRTC, tearing would present as one line tear which is incredibly stable, if fps can reach the target, even below tearing is still pretty stable. With Chill, tearing at almost time will present as two pretty small tearing at two position of the monitor, one upper and one lower. With RTSS, tearing gathers its power at one position of monitor and “dances” at that point. This behavior applies to almost all games, or so I’ve seen so far, and with that information, I think it is not silly to assume that fps limiters somehow affect or help Freesync or G-sync.
Thanks for taking your time to go through my long comment, there are maybe mistakes as English is not my primary Language, hope I did not make too much of it.
And Happy New Year.

wpDiscuz