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.

G-SYNC Activation

“Enable for full screen mode” (exclusive fullscreen functionality only) will automatically engage when a supported display is connected to the GPU. If G-SYNC behavior is suspect or non-functioning, untick the “Enable G-SYNC, G-SYNC Compatible” box, apply, re-tick, and apply.

Blur Buster's G-SYNC 101: Control Panel

G-SYNC Windowed Mode

“Enable for windowed and full screen mode” allows G-SYNC support for windowed and borderless windowed mode. This option was introduced in a 2015 driver update, and by manipulating the DWM (Desktop Windows Manager) framebuffer, enables 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.

Note: this setting may require a game or system restart after application; the “G-SYNC Indicator” (Nvidia Control Panel > Display > G-SYNC Indicator) can be enabled to verify it is working as intended.

G-SYNC Preferred Refresh Rate

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

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 control panel’s “Vertical sync” entry is automatically engaged to “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

3057 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
majkool
Member
majkool

Hello @jorimt,
Great article! Have a questions (game CSGO low settings, 144Hz monitor, my fps mostly reach or exceed refresh rate):

    1. In terms of input lag it’s better to use VSYNC (double buffered) in-game because GSYNC is native double buffered or better use it in NVCP?

    2. When using G+VSYNC in NVCP and fps_max 140 I have often fps spikes above it but when I use LLM(Ultra) it’s really stable and there is no spikes above 138fps. Because of that there could be tearing, stuttering or more input lag?

    3. What is best for input lag – G+VSYNC OFF + fps_max 999 or G+VSYNC+fps_max 140?
    Thanks in advance for answer.

Greets!

Like0Vote Down 
2 years 6 months ago
jorimt
Author
jorimt

1. In terms of input lag it’s better to use VSYNC (double buffered) in-game because GSYNC is native double buffered or better use it in NVCP?

The NVCP V-SYNC option is also double buffer.

2. When using G+VSYNC in NVCP and fps_max 140 I have often fps spikes above it but when I use LLM(Ultra) it’s really stable and there is no spikes above 138fps. Because of that there could be tearing, stuttering or more input lag?

One of the games I specifically tested in this article was CS:GO, and at fps_max 142 144Hz it never exceeded the G-SYNC range or increased input lag in my tests (over a lower limit), so if you’re looking at your monitor’s built-in refresh rate meter, ignore it. Mine does that too; FPS “spikes” only occur when the framerate drops to 0 momentarily. This is probably what the meter is reflecting.

That, and the LLM Ultra limiter has steadier frametimes than the in-game limiter, but it also has up to 1 frame more latency.

3. What is best for input lag – G+VSYNC OFF + fps_max 999 or G+VSYNC+fps_max 140?
Thanks in advance for answer.

Technically, always no sync + uncapped (assuming your GPU usage doesn’t max out at any point at those framerates, which will create render queue input lag separate of syncing methods).

G-SYNC + V-SYNC is the lowest tear-free syncing method possible, and its frame delivery speed is directly limited by the scanout time of the max refresh rate; the higher the refresh rate, the closer G-SYNC and no sync latency becomes.

Any faster frame delivery requires no sync, which decreases delivery time more than otherwise possible at the given refresh rate by tearing (what you see below the tearlines is your literal latency reduction over synced).

At 144Hz+, at crosshair-level, there’s virtually no difference in average latency between G-SYNC + V-SYNC and no sync at the same framerate within the refresh rate (note that my tests were done with first on-screen reactions, as opposed to middle screen; if I recounted the results at crosshair-level, the min/avg/max numbers would effectively be equal across all three scenarios):
https://blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/6/

comment image

It’s only once your system can sustain a framerate multiple times above the refresh rate that you start to see a genuine “advantage,” but at the expense of tearing:
https://blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/9/

comment image

Like2Vote Down 
2 years 6 months ago
majkool
Member
majkool

The NVCP V-SYNC option is also double buffer.

So it’s better to use NVCP V-SYNC option because we do not know what else is applied in-game V-SYNC option.

…it never exceeded the G-SYNC range or increased input lag in my tests (over a lower limit), so if you’re looking at your monitor’s built-in refresh rate meter, ignore it.

I’m looking at cl_showfps 5 and often see spikes even more than 144fps.

That, and the LLM Ultra limiter has steadier frametimes than the in-game limiter, but it also has up to 1 frame more latency.

There is no possibility to remove that 1 frame latency? Maybe updated Nvidia drivers?

Technically, always no sync + uncapped (assuming your GPU usage doesn’t max out at any point at those framerates, which will create render queue input lag separate of syncing methods).

CSGO is not a fps stable game because of grenades mostly smokes. So it’s really hard to achieve stable fps. So if I achieve fps that will not go below 150fps it’s better to play on nosync+uncapped fps than G+V-SYNC+fps_max140 only because less input lag but still smooth w/o stutters/tearing will be better with G-SYNC set? I think difference of 6ms in input lag is not worth vs. smoothest gameplay and with 240Hz it’s even better when we get stable 240fps in competetive 5on5 game.

Like0Vote Down 
2 years 6 months ago
jorimt
Author
jorimt

So it’s better to use NVCP V-SYNC option because we do not know what else is applied in-game V-SYNC option.

It can be, but 99% of the time, it’s safe to use either the NVCP V-SYNC or in-game V-SYNC option with G-SYNC. It can be game-dependent.

For CS:GO in particular, I’ve measured no differences between the two.

I’m looking at cl_showfps 5 and often see spikes even more than 144fps.

And? Are the numbers higher than 144 FPS or are they lower, and why do you think it matters in regards to G-SYNC directly?

Such readouts can be up to interpretation.

There is no possibility to remove that 1 frame latency? Maybe updated Nvidia drivers?

I have answered this in my article, but the short answer is no, external limiters intercept frames once they’re already rendered, whereas in-game limiters intercept them during render. There’s no way to “fix” that when using an external limiter, as it isn’t part of the engine.

That said, I have found the latest versions of RTSS and Nvidia Max Frame Rate only add up to 1/2 frame of latency over some game’s limiters. It can vary.

CSGO is not a fps stable game because of grenades mostly smokes. So it’s really hard to achieve stable fps. So if I achieve fps that will not go below 150fps it’s better to play on nosync+uncapped fps than G+V-SYNC+fps_max140 only because less input lag but still smooth w/o stutters/tearing will be better with G-SYNC set?

It depends on if you can’t tolerate tearing. If you can’t, use G-SYNC, if you can, use no sync. G-SYNC is ultimately optional.

What I can say is if your system can’t sustain the framerate far above the refresh rate in that game, again, latency difference between G-SYNC and no sync with framerates within the refresh rate at 144Hz+ is minuscule (virtually zero at crosshair-level).

Like1Vote Down 
2 years 6 months ago
majkool
Member
majkool

And? Are the numbers higher than 144 FPS or are they lower, and why do you think it matters in regards to G-SYNC directly?

It’s often above my fps_max 142. Numbers are different 170, 267 etc.
Where I can find test that fps_max command is really stable in CSGO?

I have answered this in my article, but the short answer is no, external limiters intercept frames once they’re already rendered, whereas in-game limiters intercept them during render. There’s no way to “fix” that when using an external limiter, as it isn’t part of the engine.

Sorry for my question I missed that from text.

It depends on if you can’t tolerate tearing. If you can’t, use G-SYNC, if you can, use no sync. G-SYNC is ultimately optional.

I can’t tolerate tearing when my fps in action drops below 100fps it’s much more better with GSYNC.

Btw. when I’m using G+VSYNC+fps_max 999 my game still runs GSYNC it’s not changing to adaptive GSYNC. It’s capping fps to 138.

Like0Vote Down 
2 years 6 months ago
jorimt
Author
jorimt

It’s often above my fps_max 142. Numbers are different 170, 267 etc.
Where I can find test that fps_max command is really stable in CSGO?

“cl_showfps 5” shows render time, not the framerate.

The fact that you’re seeing higher than 144 FPS numbers in that readout actually means you’re getting less latency, not more. That’s part of how the in-game limiter reduces latency over external limiters, by utilizing lower frametimes.

In other words, what you’re seeing in that readout does not mean the framerate is exceeding the G-SYNC range, or increasing G-SYNC latency, so long as you have fps_max set to ~142 FPS or under at 144Hz.

Btw. when I’m using G+VSYNC+fps_max 999 my game still runs GSYNC it’s not changing to adaptive GSYNC. It’s capping fps to 138.

You must have Low Latency Mode set to “Ultra”; with G-SYNC + NVCP V-SYNC + LLM “Ultra” it will auto limit the FPS to 138 at 144Hz.

Set LLM to “On” to remove the auto limit.

Like1Vote Down 
2 years 6 months ago
majkool
Member
majkool

The fact that you’re seeing higher than 144 FPS numbers actually means you’re getting less latency, not more. That’s part of how the in-game limiter reduces latency over external limiters.

Thanks that’s new for me!

You must have Low Latency Mode set to “Ultra”; with G-SYNC + NVCP V-SYNC + LLM “Ultra” it will auto limit the FPS to 138 at 144Hz.

No no, just G+VSYNC and LLM is OFF and there is no difference fps_max 142 and 999 in the game. It’s like V-SYNC just enabling LLMU by default but it’s not showing in NVCP.

Like0Vote Down 
2 years 6 months ago
jorimt
Author
jorimt

Thanks that’s new for me!

Yes, the “cl_showfps 5” is not the same as a simple average framerate counter, for future reference.

No no, just G+VSYNC and LLM is OFF and there is no difference fps_max 142 and 999 in the game. It’s like V-SYNC just enabling LLMU by default but it’s not showing in NVCP.

Hmm, G-SYNC + V-SYNC + LLM “Off” + fps_max 999 shouldn’t have an auto 138 FPS limit at 144Hz. Don’t know what to tell you further without seeing what’s going on in person.

That said, if you want “adaptive” G-SYNC, use G-SYNC on + V-SYNC off (both in-game and in the NVCP). This should allow G-SYNC to disengage and the screen to tear when the framerate exceeds the refresh rate.

G-SYNC + V-SYNC + FPS above the refresh rate = normal V-SYNC behavior, hence the need for an FPS limit slightly below the refresh rate.

Like0Vote Down 
2 years 6 months ago
Vel0X
Member
Vel0X

I have one question and I hope it has not been asked so far. I get that G sync generally is best with the settings you suggest us here.
When I go for the SIM value in OW I get better input lag with your settings, nvcp v sync off, reflex on, uncapped (400) fps than with your suggested settings.

Does that SIM value matter?

Because the picture looks better with your settings but SIM value is like 1ms worse.

Like0Vote Down 
2 years 6 months ago
jorimt
Author
jorimt

“SIM” is directly tied to average framerate in that game; the higher the framerate, the lower the SIM number.

G-SYNC obviously only works when the framerate is within the refresh rate, which means it’s highest framerate is limited to just under the max refresh rate of the display.

G-SYNC is the lowest lag no-tear method; any lower lag would require tearing.

Like4Vote Down 
2 years 6 months ago
pineapplefirestorm
Member
pineapplefirestorm

Hello, love this guide a ton! I have an issue with G-sync I hope you might know what to do with since you’re the G-sync guru around here.

So I play a game called MapleStory, & the best resolution it can really run at is 1366×768 unfortunately. No way around it. It does run at 165Hz though. (There’s a beta 1080p option but it’s bad & as I later describe, the issue is more of a resolution change issue with G-sync. I tried 1080p and saw no difference.)

I also tried other fullscreen games, and the issue I later describe also applies to them when running at non-native desktop resolution – so it is NOT a MapleStory-specific issue to be clear.

I use the Dell S2721DGF with a RTX 3080, single monitor at 2560×1440, DP 1.4 at 165Hz.

As you can figure, 1366×768 is pitifully small to look at on a 1440p screen, so I use fullscreen. And with that, I alt+tab a ton.

And here’s the issue: ONLY with G-sync enabled – whether it is fullscreen+windowed or just fullscreen G-sync – there is a 3-5 second delay when alt+tabbing, likely caused by the resolution change.

To reiterate: it ONLY happens with G-sync enabled. If I simply just disable G-sync, it immediately begins to alt+tab instantly with zero delay.

I have the desktop scaling set to GPU & override, and have restarted multiple times, and used DDU to clean install the latest NVIDIA drivers. HDR is disabled in Windows and at the monitor level.

Any idea on this? Is this a normal/buggy/monitor issue with G-sync? Obviously I’d prefer to play with G-sync enabled, but the 3-5 second alt+tabbing drives me nuts.

Thank you.

Like0Vote Down 
2 years 6 months ago
jorimt
Author
jorimt

The best way I can answer is testing it myself.

I’ve downloaded the game and will try to replicate it when I get the time (no ETA). I’ll ultimately reply here with my findings…

Like1Vote Down 
2 years 6 months ago
pineapplefirestorm
Member
pineapplefirestorm

As noted actually, I tried other fullscreen games, and the issue does occur in other games as well, so it’s not exactly a MapleStory-specific problem.

For example, it happens in the free NVIDIA G-sync Pendulum Demo if I set it to a non-1440p resolution (e.g. 1920×1080, 1366×768, etc.), then launch and/or alt+tab it. Gives that darn 3-5 sec alt+tab blank out period when the resolution change triggers – only when G-sync is enabled. Disable G-sync, and then the launch/alt+tab resolution change becomes instant.

I just used MapleStory as an example game because it doesn’t offer a 1440p resolution option, so that takes out “just set it to 1440p” as a possible solution 🙁

Thanks again! I appreciate the reply.

Like0Vote Down 
2 years 6 months ago
jorimt
Author
jorimt

I just tested the Pendulum demo on my PG279QM (1440p 240Hz native G-SYNC monitor), and with the demo set to 1366×768, with or with scaling enabled in the NVCP and G-SYNC on, my alt+tab was instantaneous.

So we’re looking at a couple of possibilities:

1. You have globally forced fullscreen optimizations off via a regedit or the like (which could possibly cause something like this).

Or

2. It’s specific to that monitor model and/or it being a FreeSync display that is G-SYNC Compatible.

I looked up that model, but did not find any immediate results involving alt+tab issues of this particular kind.

You could try to disable the monitor overclock temporarily (165Hz to 144Hz), as well as switch between your monitor OSD scaling options (if it has them), and see if either have any effect on this.

Like1Vote Down 
2 years 6 months ago
pineapplefirestorm
Member
pineapplefirestorm

Alright, so…went through a ton of new stuff thanks to your suggestions.

Unfortunately, tl;dr is that I’m believing it’s a monitor-level issue. Maybe not model, but appears to be at least my monitor.

First off – with global fullscreen optimizations. I checked the registry & in Computer\HKEY_CURRENT_USER\System\GameConfigStore -> GameDVR_FSEBehaviorMode was at the setting of 2.

I swear that I’ve never touched that registry key before, but it looks like value of 2 meant that fullscreen optimizations were disabled. Cue happiness that this was most likely the culprit, since fullscreen optimizations are supposed to help with faster alt+tabbing!!

…but alas, it wasn’t the issue. Changed it to 0, restarted, still same thing. Looked around a significant number of websites, changed GameDVR_HonorUserFSEBehaviorMode & GameDVR_DXGIHonorFSEWindowsCompatible both to 1, restarted several times, still no dice.

Tried going down to 144Hz as well, no change at all…

Still don’t know how the FSEBehaviorMode was set to 2, but that’s…probably unrelated? Because the fullscreen optimizations were clearly working. So I reverted the registry keys back to 2, restarted, then I manually disabled fullscreen optimizations in VRR64.exe (the Pendulum Demo EXE file) and MapleStory.exe & saw that when I pressed the volume keys on my keyboard, the Windows Volume OSD did not show up, which meant fullscreen optimizations were off. Cool.

So then I unchecked the “disable fullscreen optimizations” & tried Pendulum Demo & MapleStory again…and the Volume OSD was there, indicating fullscreen optimizations were on despite FSEBehaviorMode being a value of 2. So it’s like the registry key is being ignored. Huh. My issue is that it only happens with G-sync enabled, so probably unrelated but weird.

So I got thinking…I do have a LG 27GL850 on another computer, mainly for another member of the family to use…I need to try that!

And what do you know? G-sync is enabled. And switching between resolutions works instantly. But that’s not even how I first realized it. When I first checked the “Adjust desktop size and position” scaling options after plugging in the monitor, I realized something. When I switched from Display to GPU scaling, override, etc…on the 27GL850, when I hit Apply, it switched scaling immediately. On the Dell S2721DGF, when I hit Apply, it acted as if I did alt+tab, giving a 3-5 sec blank screen delay. Heck, when I move between the different GPU scalings (Aspect Ratio, Fullscreen) on the S2721DGF, it does that 3-5 sec blank screen delay too! But it doesn’t do that for the 27GL850!

I did check the monitor OSD settings and fiddled with basically all of them (including the auto-resize, tried force 16:9 and force 4:3 and auto-resize), but nothing ever ended up working out.

tl;dr unknown if it’s a model issue or my monitor’s specific issue, but it doesn’t occur on a 27GL850. Also, I tried using the same DisplayPort cable on both & a new one on both, didn’t make any difference on either case.

144Hz vs 165Hz isn’t a big deal to me, so I’ll just swap them out. The other monitor isn’t used for any gaming, so should be cool.

Thanks for your assistance! It got me to this point of thinking & figuring out what the issue is from, though unfortunately the conclusion is to basically use another monitor, lol…

Like1Vote Down 
2 years 6 months ago
jorimt
Author
jorimt

Yeah, I only mentioned FSO because it’s known to reduce alt+tab time in exclusive fullscreen apps. It was just one of several possibilities. I’ve never disabled it in the registry, so your guess is as good as mine as to why it was set that way without intervention.

Good to hear you had the 27GL850 to fall back on, and that it doesn’t have the same issue.

As for the S2721DGF, it’s possible it’s that particular unit of that model, or it’s possible the scaler/firmware of that model simply does that when switching to and from non-native resolutions. Hard to say without you trying another unit of that same model.

Like1Vote Down 
2 years 6 months ago
pineapplefirestorm
Member
pineapplefirestorm

So one of my friends was gracious enough to bring over their Dell S2721DGF monitor (relatively easy since they have a VESA stand) for testing – and it occurs on their monitor too.

So, based on a sample of 2, it appears that it’s a monitor model thing. I couldn’t find anything on Google or Reddit on any comments about slow alt+tabbing either on Dell S2721DGFs, so that’s weird. Oh well.

Like0Vote Down 
2 years 6 months ago
jorimt
Author
jorimt

Well, at least you were able to confirm it was the model at fault.

Not to open another can of worms, but, curious; does it happen on your friends computer with that monitor as well?

Like0Vote Down 
2 years 6 months ago
pineapplefirestorm
Member
pineapplefirestorm

Forgot to mention that. Yep, it happens on their machine as well when we tested changing resolutions in multiple games, etc, the full testing deal. They have an Intel i7-4790 and a GTX 1060 6GB card, so it’s quite a different system compared to mine.

Like0Vote Down 
2 years 5 months ago
jorimt
Author
jorimt

Thanks for the confirmation. Then yeah, it’s definitely the monitor model. Probably something to do with the firmware in combo with its scaler.

Like0Vote Down 
2 years 5 months ago
Zehdah
Member
Zehdah

Hey Jorimt. Do these settings apply for a monitor using adaptive sync if I have a Nvidia GPU? So can I copy the recommended settings as if I have Gsync? Heard it works the same as Gsync but thought I’d ask to be sure.

Like0Vote Down 
2 years 6 months ago
jorimt
Author
jorimt

Such as FreeSync monitors or OLED TVs that are “G-SYNC Compatible?” If so, yes, the same general recommended settings apply.

Like1Vote Down 
2 years 6 months ago
Zehdah
Member
Zehdah

Yep. Thank you for confirming!

Like0Vote Down 
2 years 6 months ago
jorimt
Author
jorimt

No worries.

Like0Vote Down 
2 years 6 months ago
blaskovic
Member
blaskovic

Hi jorimt. I have a question for you. Sometime in older games (2011 – 2013) I have a drop frame from 144 to 140 or 144 to 135 and I notice this microstutter with G-sync but in other games if I have this drops (for example in Dirty Rally) I don’t see anything. My question is this: Why in some case (games) G-Sync seems works but in other circumstances (games) i see this microstutter? G-Sync shouldn’t avoid Microstutter? Thank you

Like0Vote Down 
2 years 7 months ago
jorimt
Author
jorimt

G-SYNC fixes V-SYNC stutter only. It can’t and won’t do anything for system-side stutter, which will show regardless of sync or no sync.

Like1Vote Down 
2 years 7 months ago
blaskovic
Member
blaskovic

Thank you for your answer. I have just another question. Sometime because a game has got problems (system-side stutter) people give the advice to put a fps cap. For a monitor 144hz I know the advice is 141 but in some games this cap doesn’t work and the best options are setting 100 fps, 72 fps, or other. What I would ask you if there is some ” magic formula” to put in fps cap when I meet this game that doesn’t work well.
For example I tried Deus Ex Human Revolution and i Have put all g-sync setting of your guide (NVCP v-sync ON – G-Sync ON – FPS CAP 141 – V-sync in game OFF) but in this game doesn’t work ( there is too much stuttering). I set FPS CAP 100 fps, the same problem. The best setting was 72 fps (few stuttering) but I’ don’t understand why. Is there a right proportion ?( for example monitor 144hz must use 72 fps cap, monitor 165 must use 82 fps cap, ecc) Thank you

Like0Vote Down 
2 years 7 months ago
jorimt
Author
jorimt

First off, even interval capping (72 FPS for 144Hz monitor, 60 FPS for 120Hz, and so on) does not apply to G-SYNC, it only applies to standard V-SYNC (aka G-SYNC off + V-SYNC on). G-SYNC will deliver frames evenly, regardless of the framerate limit to refresh rate ratio, so long as the framerate is within the refresh rate.

My -3 FPS recommendation is only to keep the framerate within the refresh rate to maintain G-SYNC functionality where the framerate can otherwise exceed the refresh rate if left uncapped.

The recommendation is not for preventing any form of stutter, or taking into consideration the achievable average framerate, which is going to vary heavily per system and game, and thus can’t be calculated into a single, blanketed limit.

As for the “magic formula” to limiting, there isn’t one in this particular case. Again, it’s highly dependent on your system and the game it’s running.

The stutter you’re experience is likely due to frametime spikes, which means one or more new frames don’t show for more than one refresh cycle, forcing the previous frame to repeat until they do. This is usually caused by the render of the affected frames taking longer at these times due to background asset streaming (when you reach a new area, and/or something loads in), shader compilation, auto saving, etc.

G-SYNC can’t fix this because it can only sync the frames that are coming in. It does not create them. As such, when there isn’t a new frame or frames coming in and the previous frame is repeating, all G-SYNC can do is sync that frame to prevent tearing until the next frame is finally ready. When a previous frame displays more than once, it creates the appearance of stutter.

The reason a lower FPS limit with G-SYNC is causing less stutter for you, is it’s taking strain off your system (as opposed to running at a higher framerate).

Also, when your GPU usage maxes out, pre-rendered frames in the render queue increase, causing more input lag. To prevent this, as well as (in some cases) decrease the occurrence of system-side stutter, play your game uncapped for a while and see what your lowest average framerate is. Once you find that, cap slightly below it to ensure your system isn’t strained and your GPU usage doesn’t reach 99%. This will prevent GPU input lag (unrelated to G-SYNC) and give a more consistent framerate.

The necessary limit will obviously vary by game.

Like1Vote Down 
2 years 7 months ago
blaskovic
Member
blaskovic

Thanks a lot

Like1Vote Down 
2 years 6 months ago
jorimt
Author
jorimt

You’re welcome.

Like0Vote Down 
2 years 6 months ago
wpDiscuz

Related Content

Featured Content

Blur Buster Forums

Blur Busters Forums

TestUFO Motion Tests

TestUFO Motion Tests