Prev ... Next

G-SYNC 101: Range

Published Jun 20, 2017 by in: G-SYNC

Blur Buster's G-SYNC 101: Range Chart

Exceeds G-SYNC Range

G-SYNC + V-SYNC “Off”:
G-SYNC disengages, tearing begins display wide, no frame delay is added.

G-SYNC + V-SYNC “On”:
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.

G-SYNC + Fast Sync*:
G-SYNC disengages, Fast Sync engages, 0-1 frame of delay is added**.
*Fast Sync is best used with framerates in excess of 2x to 3x that of the display’s maximum refresh rate, as its third buffer selects from the “best” frame to display as the final render; the higher the sample rate, the better it functions. Do note, even at its most optimal, Fast Sync introduces uneven frame pacing, which can manifest as recurring microstutter.
**Refresh rate/framerate ratio dependent (see G-SYNC 101: G-SYNC vs. Fast Sync).

Within G-SYNC Range

Refer to “Upper & Lower Frametime Variances” section below…

Upper & Lower Frametime Variances

G-SYNC + V-SYNC “Off”:
The tearing inside the G-SYNC range with V-SYNC “Off” is caused by sudden frametime variances output by the system, which will vary in severity and frequency depending on both the efficiency of the given game engine, and the system’s ability (or inability) to deliver consistent frametimes.

G-SYNC + V-SYNC “Off” disables the G-SYNC module’s ability to compensate for sudden frametime variances, meaning, instead of aligning the next frame scan to the next scanout (the process that physically draws each frame, pixel by pixel, left to right, top to bottom on-screen), G-SYNC + V-SYNC “Off” will opt to start the next frame scan in the current scanout instead. This results in simultaneous delivery of more than one frame in a single scanout (tearing).

In the Upper FPS range, tearing will be limited to the bottom of the display. In the Lower FPS range (<36) where frametime spikes can occur (see What are Frametime Spikes?), full tearing will begin.

Without frametime compensation, G-SYNC functionality with V-SYNC “Off” is effectively “Adaptive G-SYNC,” and should be avoided for a tear-free experience (see G-SYNC 101: Optimal Settings & Conclusion).

G-SYNC + V-SYNC “On”:
This is how G-SYNC was originally intended to function. Unlike G-SYNC + V-SYNC “Off,” G-SYNC + V-SYNC “On” allows the G-SYNC module to compensate for sudden frametime variances by adhering to the scanout, which ensures the affected frame scan will complete in the current scanout before the next frame scan and scanout begin. This eliminates tearing within the G-SYNC range, in spite of the frametime variances encountered.

Frametime compensation with V-SYNC “On” is performed during the vertical blanking interval (the span between the previous and next frame scan), and, as such, does not delay single frame delivery within the G-SYNC range and is recommended for a tear-free experience (see G-SYNC 101: Optimal Settings & Conclusion).

G-SYNC + Fast Sync:
Upper FPS range: Fast Sync may engage, 1/2 to 1 frame of delay is added.
Lower FPS range: see “V-SYNC ‘On'” above.

What are Frametime Spikes?

Frametime spikes are an abrupt interruption of frames output by the system, and on a capable setup running an efficient game engine, typically occur due to loading screens, shader compilation, background asset streaming, auto saves, network activity, and/or the triggering of a script or physics system, but can also be exacerbated by an incapable setup, inefficient game engine, poor netcode, low RAM/VRAM and page file over usage, misconfigured (or limited game support for) SLI setups, faulty drivers, specific or excess background processes, in-game overlay or input device conflicts, or a combination of them all.

Not to be confused with other performance issues, like framerate slowdown or V-SYNC-induced stutter, frametime spikes manifest as the occasional hitch or pause, and usually last for mere micro to milliseconds at a time (seconds, in the worst of cases), plummeting the framerate to as low as the single digits, and concurrently raising the frametime to upwards of 1000ms before re-normalizing.

G-SYNC eliminates traditional V-SYNC stutter caused below the maximum refresh rate by repeated frames from delayed frame delivery, but frametime spikes still affect G-SYNC, since it can only mirror what the system is outputting. As such, when G-SYNC has nothing new to sync to for a frame or frames at a time, it must repeat the previous frame(s) until the system resumes new frame(s) output, which results in the visible interruption observed as stutter.

The more efficient the game engine, and the more capable the system running it, the less frametime spikes there are (and the shorter they last), but no setup can fully avoid their occurrence.

Minimum Refresh Range

Once the framerate reaches the approximate 36 and below mark, the G-SYNC module begins inserting duplicate refreshes per frame to maintain the panel’s minimum physical refresh rate, keep the display active, and smooth motion perception. If the framerate is at 36, the refresh rate will double to 72 Hz, at 18 frames, it will triple to 54 Hz, and so on. This behavior will continue down to 1 frame per second.

Regardless of the reported framerate and variable refresh rate of the display, the scanout speed will always be a match to the display’s current maximum refresh rate; 16.6ms @60Hz, 10ms @100 Hz, 6.9ms @144 Hz, and so on. G-SYNC’s ability to detach framerate and refresh rate from the scanout speed can have benefits such as faster frame delivery and reduced input lag on high refresh rate displays at lower fixed framerates (see G-SYNC 101: Hidden Benefits of High Refresh Rate G-SYNC).

Prev ... Next

3776 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
olam
Member
olam

Hi, I would have two scenarios on which I’m not sure if I set it correctly in my case.

G-Sync + V-Sync are on

Game 1 – CS2 (FPS 99% exceeds refresh rate, Reflex available)
– FPS Limit 357 (I got 360 Hz)
– Reflex off (LLM also off)

Game 2 – PUBG (FPS rarely exceeding refresh rate, Reflex not available)
– FPS Limit 357
– Low Latency Mode -> On

Am I doing it right in this case?
If not, please correct me! Thanks in advance for your reply.
I just want to have the smoothest experience.

Like0Vote Down 
1 day 6 hours ago
jorimt
Author
jorimt

Am I doing it right in this case?

Unfortunately, what you’re asking is very situational…

VRR/this article predominately addresses “sync” latency (VRR on + V-SYNC on + minimum 3 FPS below physical refresh rate), while settings like LLM and Reflex address “render queue” latency separately.

In other words, you can have sync latency without render queue latency, visa-versa, or both.

So, in your #1 and #2 scenarios, you have sync latency handled. That leaves added render queue latency, which occurs whenever your GPU usage is 99%+, with or without VRR, and whether your framerate is above or below the refresh rate.

Added render queue latency due to maxed GPU usage reduction in order of overall effectiveness:

Reflex > manual FPS limit (at framerate slightly below achievable average that prevents 99%+ GPU usage at all times) > LLM “Ultra” > LLM “On”

As such, if your GPU usage is frequently reaching 99%+ and Reflex is available, use it. If Reflex isn’t available in the same scenario, a manual limit as described above is usually second best, but is typically required to be lower (as to account for the lowest possible framerate drops caused by maxed GPU usage) and is obviously a static, not dynamic limit like Reflex is.

If manual limit tuning with a reduced average framerate to prevent maxed GPU usage isn’t to your liking, and Reflex isn’t available, then you’ll have to resort to LLM “Ultra” for similar render queue latency reduction.

I don’t really recommend LLM “On” in any scenario, personally, and both it and “Ultra” can worsen frametime performance in certain scenarios when directly compared to Reflex or a manual limit.

So, to summarize, VRR is much more set-and-forget-friendly than settings involving render queue latency, as the latter entirely depends on your graphical settings + average framerate target and your particular GPU’s ability to achieve it without maxing out in the given game.

Like0Vote Down 
10 hours 4 minutes ago
sc719
Member
sc719

I play competitive COD, on a 280Hz OLED, with average frames 300, 1% lows 220 and 5% 250…

To summarize theres basically 3 options you are suggesting?

1. Lowest tear free: VRR + Vsync + Reflex/AntiLag (or turn this off and have in game limit)

2. Absolute lowest response time: Uncapped + Reflex/AntiLag

3. Last: Capped

So the 1st option at worst it adds 1-2ms of delay from your results?

When I run the 1st option with Anti Lag, it goes to exactly 280 with 90% usage when idle but will go below throughout the game, is that an issue? I think in the comments you suggested either use reflex or manually set limit, but if i use reflex it is not -3 below monitor like the manual limit, however will dip below 280 throughout the game

Just wondering if i have this right here, thanks

Like0Vote Down 
16 days 5 hours ago
jorimt
Author
jorimt

1. Lowest tear free: VRR + Vsync + Reflex/AntiLag (or turn this off and have in game limit)

My base VRR-specific recommendations are VRR on + V-SYNC on + minimum 3 frames within the physical refresh rate.

The above handles sync latency, while Reflex/Anti-Lag handle render queue latency due to GPU bound scenarios separate and distinct of what VRR handles.

2. Absolute lowest response time: Uncapped + Reflex/Anti-Lag

Yes.

3. Last: Capped

Assuming the average framerate never causes the GPU usage to reach/exceed 99%, yes (static version of Reflex, essentially).

So the 1st option at worst it adds 1-2ms of delay from your results?

It prevents any tearing that would reduce latency further; visible tearing = latency reduction; VRR + V-SYNC is the lowest possible tear-free method available for framerates within the given physical refresh rate.

When I run the 1st option with Anti Lag, it goes to exactly 280 with 90% usage when idle but will go below throughout the game, is that an issue?

Not familiar enough with Anti-Lag to say. What I can say is, if/when you’re using VRR, you need the framerate at least 3 frames lower than 280 at 280Hz to keep it engaged. Perhaps Anti-Lag doesn’t institute an automatic limit slightly below the physical refresh rate like Reflex does (in most cases, barring dev choices, API limitations, and/or bugs) with VRR on + V-SYNC on?

In that case, you’d need to set a (minimum -3 FPS) manual or in-game limit on top of that.

I think in the comments you suggested either use reflex or manually set limit, but if i use reflex it is not -3 below monitor like the manual limit, however will dip below 280 throughout the game

Again, VRR and settings like Reflex handle different forms of latency…

Reflex, in the case of VRR (as I’ve noted in the article and previous comments), does two things; 1) it prevents GPU usage from reaching 99%+ by setting a dynamic limit slightly below the currently achievable average framerate (with or without VRR enabled), and 2) whenever the average framerate could otherwise be sustained above the physical refresh rate without maxing GPU usage, Reflex sets an automatic limit a small percentage below said refresh rate to keep the average framerate safely within it, and thus ensure VRR remains engaged.

Like0Vote Down 
16 days 4 hours ago
sc719
Member
sc719

Not familiar enough with Anti-Lag to say. What I can say is, if/when you’re using VRR, you need the framerate at least 3 frames lower than 280 at 280Hz to keep it engaged. Perhaps Anti-Lag doesn’t institute an automatic limit slightly below the physical refresh rate like Reflex does (in most cases, barring dev choices, API limitations, and/or bugs) with VRR on + V-SYNC on?

In that case, you’d need to set a (minimum -3 FPS) manual or in-game limit on top of that.

Yes, others online are reporting the same thing regarding Anti Lag 2, it won’t limit the FPS below monitor rate like Reflex would.

So in this case, I will have to limit the frames myself in game, should AntiLag/Reflex still be on if we are limiting frames manually within the refresh rate of the monitor, or should they be turned off at this point?

CoD in game FPS limiter is bugged I think, the highest I can cap the frames to is 250, in fact setting the limit between 200-250 also just sets it at 250.. are external FPS limiters recommended at this stage, I know you have previously mentioned in game limits, I dont mind just limiting it to 250, its close enough to 280.

Lastly, is there a preference for Vsync on in AMD or in game?

Thank you

Like0Vote Down 
16 days 2 hours ago
jorimt
Author
jorimt

So in this case, I will have to limit the frames myself in game, should AntiLag/Reflex still be on if we are limiting frames manually within the refresh rate of the monitor, or should they be turned off at this point?

If you’re already ensuring the framerate is within the physical refresh rate with a manual in-game or external limit and you’re using VRR, then you have sync latency handled.

Question then is, is your GPU usage 99%+ at any point during your game session at your target graphical settings and average framerate?

If so, settings like Reflex/Anti-Lag will prevent the added latency at any point the GPU usage is maxed, if not, and it naturally remains below 99%, then they won’t do anything to reduce latency further, simple as that.

Again, render queue latency due to a busy GPU does not = the sync latency a framerate limit slightly below the physical refresh rate handles; you can have one, the other or both (they can stack).

are external FPS limiters recommended at this stage, I know you have previously mentioned in game limits, I dont mind just limiting it to 250, its close enough to 280.

Depends on 1) how functional the given in-game limiter is, and 2) how sensitive you are to frametime variances; external limiters tend to have steadier frametime performance than in-game, but of course, at the cost of slightly higher average latency, typically 1/2 to 1 frame (not much).

I did an LDAT test of in-game/Reflex and a few external limiters a while back, for reference:
https://forums.blurbusters.com/viewtopic.php?p=72633#p72182

Lastly, is there a preference for Vsync on in AMD or in game?

Historically, AMD CP V-SYNC only worked for OpenGL apps, but more recently, there have been multiple confirmed user reports here in the comments that it now works for most/all other APIs as well.

Some games have more quirks with their V-SYNC implementations than others; 99% of the time I recommend CP-level V-SYNC to rule those out, so you can start with that for the majority of games, but keep in mind that there may be a particular game that requires in-game V-SYNC (or visa-versa) to avoid certain anomalous behaviors.

Like0Vote Down 
15 days 9 hours ago
fishman099
Member
fishman099

Hey all, just wanted to post to say thanks for the guide. Implemented as described a long time ago (took several reads lol) but still works superbly well today.

Wanted to also post for those newly discovering this guide.

My set up:

LG Oled B3
Windows 11 (but worked on 10)
RTX4070ti super
Ryzen 5700x3d
32gb ram
2xNvMe

I have my control panel set to:

Gsync enabled for both full screen and borderless
Desktop/game res: 1440p/120hz
LLM: on
Max frame rate: 114fps
Gsync: on
Vsync: on

In game:

Vsync: off

From the getgo, I know gsync engages as the LG (when in game mode) shows the gsync symbol.

So I’m a nerd, been gaming for years but was a total noob when it came to VRR/Gsync. I either never had the kit that allowed me to even experiment or I read basic guides online that lacked context or understanding of how it worked.

However as I’ve upgraded my rig THIS guide has been a godsend.

I think it’s worth saying that this ‘process’ is NOT a magic bullet as jorimt and the mods state several times. It doesn’t make frames or increases FPS BUT what it does do, for me, is allow my games to run at a FPS below my refresh rate that minimises stutter and maximises smoothness.

Also worth bearing in mind is the point that is made repeatedly, that you may, at some points, have to compromise on either resolution OR eye candy. My 4070ti super is potent but I run EVERYTHING at 1440p. Some would say compromise, but I disagree. A relatively consistent 1440p@120hz with plenty of eye candy is much more preferable than a constant 4k@60hz but lowered settings for me (YMMV).

Similarly, in my experience, to gain the most advantage from VRR/gsync frame rates need to be as much past 60 as possible – hence the 1440p/120hz decision.

My test games were always Sensuas Saga (Hellblade2) and Alan Wake 2 primarily because they played v.nicely with Gsync and are v.graphically challenging.

I use both DLSS and/or Frame Gen if required when gaming and tbh it is a flawless experience when coupled with VRR/Gsync. Id hit 90- 114fps on AW2 but because of Gsync it would always run lovely and smooth. Also I’m quite sensitive to input latency but having followed this guide I can honestly say I’ve not noticed any significant increase!

Anyway apologies for the wall of text, thought it might help peeps who are new to this to see that even a Gsync novice can make this work as intended. Just temper those expectations and follow the guide 👍

Ps thanks to jorimt for effort in putting this guide together – awesome!!

Like1Vote Down 
26 days 4 hours ago
rubbahbandman
Member
rubbahbandman

One other thing, LLM should be disabled.

Like0Vote Down 
20 days 5 hours ago
rubbahbandman
Member
rubbahbandman

I may have misunderstood your comment, but I think your settings are not quite optimal based on the g-sync guide.

First, it is a minor difference, but there really isn’t a need to cap your max framerate to 114fps on a 120hz panel. You might as well increase it to 117fps.

Secondly, this is a bigger issue, but g-sync should not be enabled for borderless/windowed mode. This can hurt performance by 3-5%+ which isn’t the end of the world, but why take the performance hit for such a minor benefit. Maybe if you are a streamer frequently going between windows, but the guide recommends this setting remain unchecked.

Like2Vote Down 
20 days 6 hours ago
fishman099
Member
fishman099

@rubbahbandman – thanks for taking the time to respond 🙂

Fair points made but for clarity:

1. I engage LLM as some games don’t have reflex. My understanding of the guide jorimt has created is, if a game does have reflex and I enable it then it disengages the LLM setting in NVCP anyway? Also It’s worth noting that, as a rule, I don’t engage reflex when I set up my settings in game. In my experience there have been occasions where it causes more issues 8n game than it solves. However if I engage frame gen then the game will ordinarily auto engage reflex anyway.

2. Setting my refresh -6fps from my 120hz, for me, ensures that I never go above my refresh rate thus disengaging gsync. When I first set up using this guide I was set at 117/120 but occasionally my frames would bounce up to and sometimes over the 120? As per the guide I felt it better to guarantee that gsync stayed engaged by definitively setting it low enough to never breach my 120hz.

3. Borderless/windowed mode. I rarely play older stuff – sometimes games from the recent past. Where I am able, in those games, I select fullscreen this ensuring gsync is engaged. Conversely in most modern games I’ll select either fullscreen or borderless/windowed. As Jorimt states, the modern riff on this display selection in games means that gsync remains active, with little, if any, performance hit. (The better implementation of window/borderless was also a reason I moved over from W10 to W11).

Anyway, thanks for the input. It’s good to explore our settings and discuss them as, for me, it allows for better clarity on the subject!!

For better or worse I’m lazy so whilst I acknowledge that there are settings that should be engaged/disengaged per game I find it easier to set in NVCP and forget lol. I’ve yet to see a case in 18+ months where I’ve had to tweak anything but YMMV 🙂

Like3Vote Down 
18 days 18 hours ago
rubbahbandman
Member
rubbahbandman

@fishman099

Thanks for the clarification. I see where you’re coming from now and think you have a better understanding of the guide than myself. I leaned a bit too hard on some outdated information.

Out of curiosity, how did you notice your frames bouncing over 120 and which GPU model are you using? I have a 5090 and may take a more similar approach similar to yours in case my gsync is also disengaging at times (even with a 117 fps cap).

As for the borderless/windowed mode, I did not realize this was more of a legacy issue, and similarly, LLM seems to function well now (under GPU limited conditions), so this is good for me to know.

Thanks again for your response!

Like1Vote Down 
18 days 8 hours ago
fishman099
Member
fishman099

@rubbahbandman – Jorimt has answered your queries – better than I could 🤣🤣

But as layman I sorta played around with the frame rate limiter. I can’t remember if it was Jorimts guide or something I read elsewhere but my logic was that the difference (for me) between 117 and 114 was unmeasurable in real time terms – so thought I might as well ensure that the FPS doesn’t bounce?

In relation to Jorimts comment – I do actually use afterburner and understand that it’s entirely possible I was getting fakes positives but I also found it was potentially happening on a game by game basis!! Locking it to 114 just allowed me to not worry 😀😀

Btw – love the 5090 bro – what a monster of a gpu that is!!!

Like0Vote Down 
18 days 6 hours ago
jorimt
Author
jorimt

When I first set up using this guide I was set at 117/120 but occasionally my frames would bounce up to and sometimes over the 120?

I have a 5090 and may take a more similar approach similar to yours in case my gsync is also disengaging at times (even with a 117 fps cap).

If this is reflecting in system-side readouts (Afterburner, etc), it can be an actual overshoot of the average framerate due to sporadic frametimes, but if it’s only reflecting in a monitor-side refresh rate meter, it can usually be disregarded as a false-positive; said meters are approximated and can include LFC multiples in their readouts, and thus should not be relied on for this purpose.

LLM seems to function well now (under GPU limited conditions), so this is good for me to know.

I have my own views on LLM usage (especially LLM “On”), but those can be searched in the comments.

Suffice to say, in the cases Reflex isn’t available and the game is GPU-limited, a manual FPS limit set to an average framerate that avoids max GPU usage can be better than LLM “On” for reducing render queue-level latency.

Like0Vote Down 
18 days 7 hours ago
jorimt
Author
jorimt

there really isn’t a need to cap your max framerate to 114fps on a 120hz panel. You might as well increase it to 117fps.

Situational.

The only portion of my recommendations that must be adhered to for 100% tear-free VRR is VRR on + V-SYNC on + a minimum 3 frames (can be anything below as well) within the currently physical refresh rate; everything else can vary depending on the given system/game.

g-sync should not be enabled for borderless/windowed mode. This can hurt performance by 3-5%+

Also situational; the 3-5% performance issue applies primarily to legacy boderless/windowed modes, with the more modern modes, also sometimes labeled “borderless/windowed,” using newer flip-models that act more like exclusive fullscreen when focused and allow VRR to engage whether G-SYNC is set to “Enable for full screen mode” or “Enable for windowed and full screen mode” in the NVCP.

There are “situations,” however, where the legacy borderless/windowed mode is all that’s available in an older game, requiring the G-SYNC “Enable for windowed and full screen mode” option in the NVCP to be enabled, in which case, I recommend it be enabled per app via Nvidia Inspector (refer to Closing FAQ entry #5: https://blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/15/), instead of globally.

One other thing, LLM should be disabled.

In scenarios where the system/game isn’t GPU-limited and Reflex is available instead, yes.

Like1Vote Down 
19 days 23 hours ago
rubbahbandman
Member
rubbahbandman

Thanks for clarifying!

Like1Vote Down 
19 days 8 hours ago
ToKc1n
Member
ToKc1n

Good evening, I’ve been writing comments for ages, but I’m still struggling to figure it out. Perhaps it’s just my personal preference. I have a 180Hz monitor, 5070 RTX, and 13600K. How can I properly configure the G Sync+ Vidia panel with a frame rate cap?
The problem is that games don’t support 180Hz. Take RDR 2 or Black Ops 6, for example, and they jump from 123 to 156.
I’m not entirely sure how to track trends or if it makes sense. When I turn on low latency to ultra or on, I get micro-freezing and a sluggish feeling. If I just enable G Sync in the panel and nothing else, then in GTA 5, I get 0.1-0.2 ms latency and FPS spikes from 300 to 500, but if I set the FPS cap to 177 or 172, I get micro-stuttering.

Like0Vote Down 
27 days 10 hours ago
fishman099
Member
fishman099

I’m curious what res/graphics settings your running at?

Haven’t played either game for awhile but if the frame rate is jumping between 123 to 156 and your monitors refresh is 180hz then I assume your know where near hitting that.

As a novice (someone who’s used this guide successfully) I’ve just posted my settings but I run:

I have my control panel set to:

Gsync enabled for both full screen and borderless
Desktop/game res: 1440p/120hz
LLM: on
Max frame rate: 114fps
Gsync: on
Vsync: on

In game:

Vsync: off

If I’m able I also set NO in game frame limiter. In other words as my max refresh is 120hz I either select that is available or unlimited and let Gsync/NVCP do the rest.

The control panel settings, as far as I am concerned, are set and forget. When I do a fresh windows install I set the NVCP to those above and then every game I play turn off vsync immediately and either pick my monitors native refresh or unlimited.

Any game you play will allow you to select your native monitor refresh rate (if full screen). However I usually run window borderless which I understand to default to your desktop resolution/refresh anyway.

Have a play with my settings, see if they work as they are 1:1 with this guide. As I said in my post, this guide is amazing and does work. The hard part, for me, was trying to understand what each ‘setting’ did. Remember you can’t break anything and at worst have to reset your NVCP settings default 👍

Like0Vote Down 
26 days 4 hours ago
ToKc1n
Member
ToKc1n

Thanks for your reply and responses.
Unfortunately, this setup only makes things worse. It might be because of Adaptive Sync in the monitor; I had it fully enabled, but the G-Sync setting disappears.
For example, if I do something simple, I have standard sync enabled on the monitor, vertical sync in the panel, and games disabled. Using the Riva tuner, I estimate 120 fps, which holds up, but I thought games would be heavy and lag. If I don’t limit the frame rates and leave the monitor at 180 fps, the frame rates seem lower, but they go past the threshold and rise to 181-182 Hz. I think G-Sync doesn’t work at all in that case.
If I turn low-latency mode on or ultra in the control panel, nothing changes except for a frame rate drop of 3-4 Hz. And in the game itself, if I have Nvidia Reflex, I also didn’t notice a difference between on or ultra + boost.

Like0Vote Down 
24 days 12 hours ago
jorimt
Author
jorimt

How can I properly configure the G Sync+ Vidia panel with a frame rate cap?
The problem is that games don’t support 180Hz. Take RDR 2 or Black Ops 6, for example, and they jump from 123 to 156.

A framerate cap ensures a maximum limit, not an average limit.

As such, if your game can’t reach your target average framerate cap at all times, you must either 1) reduce your resolution and/or graphical settings until it can, or 2) reduce your average framerate target until the game/system can sustain it 99.9% of the time.

Other than that, your remaining choice is to let the average framerate run below your set maximum, and then dynamically reduce the render queue latency caused by maxed GPU usage in this scenario with Reflex, where available.

Regardless, none of the above has anything directly to do with G-SYNC or its configuration, which simply ensures there is no tearing for framerates within the refresh rate.

When I turn on low latency to ultra or on, I get micro-freezing and a sluggish feeling. If I just enable G Sync in the panel and nothing else, then in GTA 5, I get 0.1-0.2 ms latency and FPS spikes from 300 to 500, but if I set the FPS cap to 177 or 172, I get micro-stuttering.

This is also not directly related to VRR, and is instead due to the achievable frametime performance in the given game on your particular system, which can vary heavily from app to app.

Like0Vote Down 
27 days 9 hours ago
petran79
Member
petran79

I have an Asus Rog p348q monitor at 100 hz. Set frame rate cap at 97. I notice an issue with the updated Vulkan renderer in some applications. In Snes9x emulator for example, the games run at 48 fps instead of 60. I have to set Vulkan/OpenGL present method to Native.
While on Retroarch, on top of that step, I also have to enable “Application controlled refresh rate” option, same for Dolphin emulator where I have to disable max frame rate.

Recently I noticed a 2d game where I had to set nvidia panel frame rate to 120 in order for game to run at 60 fps instead of 48.

Like0Vote Down 
1 month 1 day ago
jorimt
Author
jorimt

Emulator VRR has always been touchy, and can depend on the core, API, and flip model being used. The particular monitor model and its VRR support (how it behaves with LFC, etc), and even differences in the emu app and driver versions can be factors as well.

As such, I don’t have specific recommendation for emulators beyond my basic VRR on + V-SYNC on + minimum -3 frames within the physical refresh rate.

Like0Vote Down 
27 days 9 hours ago
wpDiscuz

Related Content

Featured Content

Blur Buster Forums

Blur Busters Forums

TestUFO Motion Tests

TestUFO Motion Tests