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

3749 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
Deus_nsf
Member
Deus_nsf

Please take a look at this, we may have a solution for the windowed mode nightmare that doesn’t require owning an adaptive sync display!!! https://steamcommunity.com/app/993090/discussions/0/3053989078739351832/?ctp=4

Like0Vote Down 
4 years 4 months ago
biggydeen
Member
biggydeen

Hi,

First I like to thank you for this awesome guide. I’m sure you helped tens of thousands of people to get the best out of their g-sync/freesync screen.

I do have a question no one else could anwser. Maybe you know what is going on with my system and if it is related to g-sync/freesync.

My current settings:

  • 144hz screen (LG 27GL850 Ultragear, G-sync compatible)
  • G-sync (fullscreen mode) on
  • V-sync on in NVCP
  • Framelimit 140 in RTSS
  • Core park on
  • Turned off vsync ingame and any buffers if they are available
  • Low latency mode is set to “on”.

    • Basically, exactly what you mention as the optimal settings. I’m not using any overlays like g-force exp. and RTSS.

    My problem:

    I’m expieriencing some kind of (micro)stuttering when my frames drop below 140. But it’s application dependent. For example:

    When i’m playing Battlefield V on the smaller snowmap (without the train) I constantly get 140 fps. This map runs butter smooth as I would expect with free-sync. Other smaller maps also run butter smooth. When playing the bigger snow map (with the train) and fps sometimes dips below 140 (like 135) i’m expierincing some kind of stuttering. It’s just not smooth like the smaller maps. Now this confuses me because it’s only dipping 5 frames or so below my FPS cap. But the difference for me is night and day. I have the same expierence on all maps in BF V where the frames drop just a bit below my limit.

    When I run the Timespy benchmark, everything is butter smooth. But i’m no where near my fps cap. In the first demo the FPS is going all over the place dipping to 60 and all the way up to 120 but everything looks butter smooth.

    When playing Sea of Thieves I have the same problem as BF 5. When FPS goes down the smoothness is gone. Eventhough FPS is above 100.

    It’s definitely not a hardware problem (unless my screen is the problem). I’ve had the same issue with completely other hardware. I already have a new cpu, gpu and ram. Same issue’s.

    To give you an idea what i’m expierencing:

    I did expierence the same thing when I was still using a 60hz screen + vsync. If FPS dropped below 60, even if it’s 1 frame, the smoothness is gone. That would be expected with a 60hz + vsync but I would not expect this with free-sync only dropping a few frames and way above 130 fps.

    The strange thing is, this does not always happen. Like the timespy example, everything is butter smooth but the FPS is not even near the fps cap. So, free-sync is working just fine.

    Do you have any idea what i’m facing here? Could it be CPU related because BF5 is very CPU heavy and basically always hits 100% cpu use ( i’m running the 5800x). But some cores are actually running 100% on the small now map (I checked) but on that map everything is butter smooth.

    Like0Vote Down 
    4 years 4 months ago
    jorimt
    Author
    jorimt

    Yes, your listed G-SYNC configuration is sufficient.

    Refer to:
    https://blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/2/#spikes-101

    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, background asset streaming, 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.

    Beyond frametime spikes, there’s an off chance your particular unit could be experiencing frame skipping in VRR mode, but since you claim gameplay is sometimes “butter smooth,” frame skipping is unlikely, as it would occur no matter the situation. Regardless, you can test for that here:
    https://testufo.com/frameskipping

    Also, you didn’t mention whether this “micro-stutter” was continuous (i.e. regularly occurring in 1 sec intervals, for instance), or if it was more infrequent and spread out, such as the frametime spikes that were explained in my quote.

    Finally, yes, a maxed CPU can cause stutter, and a maxed GPU can cause a feeling of sluggishness due to an increase of pre-rendered frames in the render queue. However, neither those, frametime spikes, nor micro-stutter are directly related to G-SYNC operation (which is solely responsible for hiding the tearline), and would occur with or without it enabled.

    Like0Vote Down 
    4 years 4 months ago
    biggydeen
    Member
    biggydeen

    Thanks for you quick reply!

    I did the test but there is no frameskipping captured.

    Well, it just occured to me the “stuttering” is only happening when I move the mouse around. When I just walk straight, everything seems smooth untill I pan the camera in either direction (not even fast, can also notice it when turning slowly). These “stutters” are consistent when the FPS is below 140.

    I’m not sure if stuttering is the right word. It just does not feel smooth. But there is no tearing for sure.

    The weird thing is, all Timespy benchmarks are butter smooth regardless of FPS.

    Ill try to capture the frametimes and see if there are any drops.

    Like0Vote Down 
    4 years 4 months ago
    jorimt
    Author
    jorimt

    I did the test but there is no frameskipping captured.

    Yeah, didn’t think so.

    Well, it just occured to me the β€œstuttering” is only happening when I move the mouse around. When I just walk straight, everything seems smooth untill I pan the camera in either direction (not even fast, can also notice it when turning slowly). These β€œstutters” are consistent when the FPS is below 140.

    Your mouse model, DPI and polling rate?

    I’m not sure if stuttering is the right word. It just does not feel smooth. But there is no tearing for sure.

    It is difficult to remotely visualize and pinpoint your exact issue with the generally vague description thus far, yes. What I can say, is if you’re still experiencing similar issues with G-SYNC disabled (you didn’t say), it’s not G-SYNC.

    The weird thing is, all Timespy benchmarks are butter smooth regardless of FPS.

    Timespy is non-interactive, so there’s nothing to “feel” in regards to the feedback you’re getting from the display from continuous voluntary mouse movements during gameplay. That very distinction may make the issue in the Timespy benchmark much less apparent, if present.

    Like0Vote Down 
    4 years 4 months ago
    biggydeen
    Member
    biggydeen

    Mouse: Logitec g502, DPI 500, polling rate 1000hz. Although I removed the bloatware from Logitic controlling these setting as I was feeling this software makes my performance worse. Just a feeling though.

    I never actually tried running g-sync off. I just did some games and this is exactly the issue I’m seeing. When running g-sync off, I get 140 fps but it’s just not smooth. When I turn G-sync on again, everything is smooth untill fps drops below 140. Then I see the exact same thing as with G-sync off. Just not smooth.

    I also noticed that the OSD on my display is putting out different HZ not coresponding with the FPS. For example, I limmited the FPS to 130 but the OSD in my screen jumps up to 144hz multiple times. And also dropping below 130hz (like 116hz) while the FPS (according to the battlefield ingame drawoverlay) is steady 130.

    Is there something wrong with my screen perhaps?

    Like0Vote Down 
    4 years 4 months ago
    jorimt
    Author
    jorimt

    Mouse: Logitec g502, DPI 500, polling rate 1000hz.

    Yeah, you’re mouse is fine then.

    I never actually tried running g-sync off. I just did some games and this is exactly the issue I’m seeing. When running g-sync off, I get 140 fps but it’s just not smooth. When I turn G-sync on again, everything is smooth untill fps drops below 140. Then I see the exact same thing as with G-sync off. Just not smooth.

    If “just not smooth,” means a general feeling of sluggishness when it drops below your 140 FPS limit, like your mouse is being dragged through molasses, and not more stutter and/or tearing, what you’re likely experiencing is render queue input lag, which isn’t directly related to G-SYNC, and is something G-SYNC cannot and will not fix.

    Render queue input lag occurs primarily whenever your GPU usage is maxed (99% >). This results in the CPU creating more pre-rendered frames as it waits for the GPU to catch up and be ready for the next. This can usually result in up to 2 more frames of input lag.

    There are multiple ways to reduce this (ordered from least effective to most effective):

    1. LLM “On”: with G-SYNC, this will reduce the maximum amount of pre-rendered frames in this situation to 1 (default is usually 3), so whenever the GPU becomes maxed, the CPU can’t prepare more than 1 frame in advance at a time. However, LLM doesn’t work in every game, and it doesn’t work in DX12 or Vulkan at all. It also doesn’t eliminate the render queue in GPU-bound scenarios, just reduces it.

    2. Set an FPS limit at your system’s 99% average: this is typically fool-proof, but it does require that you limit your FPS at the lowest average your system can maintain in the given game. It will ensure the set FPS cap is the limiting factor, and prevent the GPU from ever being maxed, as the system can sustain the limit at all times.

    3. Reflex. This setting replaces LLM entirely, and unlike option #2, it sets a dynamic FPS limit just below your achievable average framerate to prevent max GPU usage, which effectively eliminates render queue input lag, even when your system can’t sustain the FPS at your originally set limit of 140.

    If that still doesn’t reduce or remove the feeling for you, I’m out of ideas. There’s only so many causes.

    I also noticed that the OSD on my display is putting out different HZ not coresponding with the FPS. For example, I limmited the FPS to 130 but the OSD in my screen jumps up to 144hz multiple times. And also dropping below 130hz (like 116hz) while the FPS (according to the battlefield ingame drawoverlay) is steady 130.

    Is there something wrong with my screen perhaps?

    Anything is possible, but it’s unlikely. That OSD readout on FreeSync displays in G-SYNC Compatible mode is infamously unreliable.

    Try this RTSS add-on instead:
    https://forums.guru3d.com/threads/does-someone-know-how-to-enable-the-g-sync-indicator-in-nvcp-through-reg-or-other-means.433672/#post-5823497

    Like0Vote Down 
    4 years 4 months ago
    biggydeen
    Member
    biggydeen

    Thanks for the help.

    LLM is already set to on. Just did some other tests:

  • 200 fps (ingame cap) without gsync -> stuttering
  • 144 ingame fps cap with gsync -> stuttering (RTSS off)
  • 140 RTSS cap with gsync -> butter smooth
  • Everything below the cap feels like without g-sync activated.

    • My gpu usage is never above 60% usage at any given time (3080ti) in the game I tested.

    Used the G-sync display indicator (and the tool you mentioned) from NVCP but g-sync seems to be running just fine.

    Reflex is not supported so can’t test that at this moment.

    I do feel things improved when swithching to ultimate power plan instead of balanced. But after so many testing im not even sure anymore…

    I will do some more testing. If nothing works I’ll try setting a much lower fps cap (like 120 or so).

    Like0Vote Down 
    4 years 4 months ago
    jorimt
    Author
    jorimt

    I found your forum thread and followed-up there:
    https://forums.blurbusters.com/viewtopic.php?f=2&t=8935&p=70128#p70128

    Like0Vote Down 
    4 years 4 months ago
    jorimt
    Author
    jorimt

    it’s hard determine from your descriptions thus far whether it’s stutter, micro-stutter, or input lag.

    If what you’re describing isn’t render queue input lag or frametime spikes/recurring stutter from something like a maxed CPU and/or GPU, I’d have to experience it in person to say for certain.

    Are you saying it feels “right” at 140, but as soon as it drops only one frame (139 or lower), it just feels “wrong” with G-SYNC? Because it’s entirely known that, say, 80 FPS feels “worse” than 120 or 140 FPS. But that’s because there are less refresh cycles, or “updates” per second. E.g. G-SYNC can’t make a lower framerate feel like a higher one.

    That said, the difference between, say, 139 FPS and 140 FPS G-SYNC at 144Hz should be indiscernible.

    Regardless, this is starting to not sound like a G-SYNC-exclusive issue.

    If you’d like to continue the troubleshooting in longer form, please create a thread in our forums, or provide a link here to a thread you have previously created about this, if applicable:
    https://forums.blurbusters.com/

    Like0Vote Down 
    4 years 4 months ago
    wellroman
    Member
    wellroman

    Hi, I’m here for an advice and I hope I’ll get one from smart people. I bought 165hz monitor with g-sync and I want to use it but I really do care about my input delay so I want to know what option is going to be the best in my situation:

    1. 165 hz monitor + 162 in game fps lock + g-sync on + v-sync on
    2. 165 hz monitor + 162 in game fps lock + g-sync on + v-sync off
    3. 165 hz monitor + 180 in game fps lock + g-sync off + v-sync off

    So the questions are:

    β€’ Does the v-sync even make sense with g-sync and will I get less input delay by turning v-sync on or by turning it off (while with g-sync)?

    β€’ Should I even use g-sync? Is there a big difference in the input delay between the option 1 and option 3 in my list?

    I hope you got my questions right and will help me))

    Like0Vote Down 
    4 years 4 months ago
    jorimt
    Author
    jorimt

    The article you’re commenting in already contains the answers to your questions, but as a quick summary…

    Does the v-sync even make sense with g-sync and will I get less input delay by turning v-sync on or by turning it off (while with g-sync)?

    The V-SYNC option is part of G-SYNC tearing prevention with framerates inside the refresh rate. Disabling the V-SYNC option in this case actually removes G-SYNC functionality, leaving you with an incomplete, partial form of G-SYNC.

    Read the second entry in my Closing FAQ for the longer answer:
    https://blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/15/

    Should I even use g-sync?

    If you can’t stand tearing artifacts, and you want the lowest possible input lag for no-tear frame delivery, yes. Otherwise, it’s entirely up to preference.

    Is there a big difference in the input delay between the option 1 and option 3 in my list?

    No.

    In fact, at cross-hair level, there’s virtually no input lag difference between the three scenarios you listed but for tearing; #1 can’t, whereas #2 & #3 can.

    Like0Vote Down 
    4 years 4 months ago
    xpnkz
    Member
    xpnkz

    Beautiful, this is like the holy grail when it comes to G-Sync information, thanks.

    I just want to ask over to be sure, since I recently switched to a Nvidia GPU with a G-Sync Compatible display and reading the comments I saw some conflicting comments too, specially since late driver updates seems to have changed a bunch of things (for example no more display selection under G-SYNC tab, but just says “Set the G-SYNC capable display as the primary display”).

    So for the best results, all I have to do in Nvidia Control Panel is:

    ● G-Sync: “ON” (Fullscreen) in the G-Sync tab and Monitor Technology set to “G-Sync” too?
    ● Vertical Synchronization: “V-Sync ON” (not Fast Sync)
    ● Low Latency Mode: “ULTRA”
    ● Max Frame Rate: “141” (my monitor is 144Hz)
    ● In game: V-Sync or related settings all OFF

    If someone can quickly glance over this and say if it’s correct, thanks!

    Like0Vote Down 
    4 years 4 months ago
    jorimt
    Author
    jorimt

    Everything you listed is fine, but a couple of notes…

    G-Sync: β€œON” (Fullscreen) in the G-Sync tab and Monitor Technology set to β€œG-Sync” too?

    As long as you enable G-SYNC under NVCP > Set up G-SYNC, it will automatically set the remaining options under NVCP > Manage 3D settings properly (those being “Monitor Technology” and “Preffered refresh rate”).

    Low Latency Mode: β€œULTRA”

    Low Latency Mode is not supported in DX12 and Vulkan games, and in some supported DX11 games, G-SYNC + NVCP V-SYNC + LLM “Ultra” will result in an automatic FPS limit of ~138 at 144Hz (internally via the NVCP Max Frame Rate limiting solution), so if you want your manual FPS limit to take effect, simply use LLM “On” instead; with G-SYNC, there is no known difference between LLM “On” and “Ultra” other than the auto limit.

    Like1Vote Down 
    4 years 4 months ago
    xpnkz
    Member
    xpnkz

    Awesome! Thanks for the quick answer and tips!

    Like1Vote Down 
    4 years 4 months ago
    coballes19
    Member
    coballes19

    Great article.
    Though, I would have wanted to know how close using high refresh rate gets to reducing vsync’s input lag on 60 fps games. I know that if you are a 60fps player and if adaptive sync is somehow unfeasible, you can counteract the input lag by simply increasing the refresh rate. I just don’t know by how much.
    Like:
    144hz 60fps Vsync off
    vs
    144hz 60fps Vsync on
    Or in 200hz and 240hz. It would be an interesting study considering, at least in my experience, adaptive sync is not an infallible and in AMD’s case, they don’t even support windowed mode.

    Like0Vote Down 
    4 years 4 months ago
    jorimt
    Author
    jorimt

    I touched on this subject here:
    https://blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/13/

    However, this “trick” only really works with G-SYNC on + V-SYNC on/off or G-SYNC off + V-SYNC off.

    Limiting the FPS to 60 with standalone V-SYNC at a higher than 60Hz refresh rates is not really going to speed up 60 FPS frame delivery like it does with the other scenarios, it will just repeat frames. E.g. 60 FPS with standalone V-SYNC at 120Hz will simply repeat each frame across 2 refresh cycles, 240Hz across 4, 360Hz across 6, 480Hz across 8, and so on.

    As for how much 60 FPS input lag can be reduce the higher the max physical refresh rate, it just depends; there’s a point where 60 FPS is just 60 FPS. I.E the minimum “input lag” in this case is limited by the render time of a single frame, which is 16.6ms per at a 60 FPS average.

    The goal when playing at 60 FPS is to eliminate any frame delay on top of that render time. An ever increasing max refresh rate paired with G-SYNC or standalone V-SYNC off will get you closer.

    Like0Vote Down 
    4 years 4 months ago
    coballes19
    Member
    coballes19

    What I’m trying to say is that I know there’s a complete difference in input lag between:
    “60hz: Gsync off + Vsync on+ 60fps(RTTS)”
    vs
    “144hz: Gsync off + Vsync on + 60fps(RTTS)”

    I just wanna know the difference in input lag between:
    “144hz: Gsync off + Vsync off + 60fps(RTTS)”
    vs
    “144hz: Gsync off + Vsync on + 60fps(RTTS)”

    Because my theory (or what I hope at least) is that 60fps at high refresh rate, the difference between Vsync on and vsync off is so small, it’s virtually the same. It’s likely, just that I have no data.

    Like0Vote Down 
    4 years 4 months ago
    jorimt
    Author
    jorimt

    I’ve technically already covered this here:
    https://blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/7/

    More specifically:

    As the numbers show, while G-SYNC and V-SYNC averages are close over a period of frames, evident by the maximums, it eventually adds up, causing 1/2 to 1 frame of accumulative delay, as well as recurring stutter due to repeated frames.

    As long as it’s within the refresh rate, the average framerate doesn’t matter in this case, and the max Hz will only affect how much each additional frame of delay is “worth.”

    So, for 144Hz and framerates within the refresh rate, we have this test, which tells us how much input lag V-SYNC off has in that scenario:

    comment image

    And then we have this test which tells us how much input lag standalone V-SYNC has in the same scenario:

    comment image

    Thus, since standalone double buffer V-SYNC has up to 1 frame more input lag than G-SYNC with framerates within the refresh rate, it will typically have up to 1 1/2 frame more input lag than standalone V-SYNC off in the same scenario.

    To calculate how much more input lag 1 1/2 frame of delay is at the given refresh rate, you simply need to know the frametime of said refresh rate. So, as stated in this part of the article:
    https://blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/3/

    Input Lag: Not All Frames Are Created Equal

    When it is said that there is β€œ1 frame” or β€œ2 frames” of delay, what does that actually mean? In this context, a β€œframe” signifies the total time a rendered frame takes to be displayed completely on-screen. The worth of a single frame is dependent on the display’s maximum native refresh rate. At 60Hz, a frame is worth 16.6ms, at 100Hz: 10ms, 120Hz: 8.3ms, 144Hz: 6.9ms, 200Hz: 5ms, and 240Hz: 4.2ms, continuing to decrease in worth as the refresh rate increases

    Thus, at 144Hz, 1 1/2 frames is an additional 10.35ms of delay.

    You can also use something like this frametime calculator, and then multiply the “Frame times in ms” by 1.5:
    https://www.hardwarepal.com/frame-time-calculator-fps/

    Like0Vote Down 
    4 years 4 months ago
    coballes19
    Member
    coballes19

    There was no standalone vsync on the pics you posted. But I did find some of your test to have one.
    comment image
    comment image
    Vsync off is 21ms while vsync on is 25ms, making it just 4ms, far from 1 1/2 frame (10.35ms) or even just 1 frame (6.9ms).

    In case of 200hz, vsync off was 19ms, vsync on was 22ms. Vsync on even managed to add up to 28ms (9ms of lag) which was beyond 1 1/2 frame of 200Hz (7.5ms).
    Interesting…

    Like0Vote Down 
    4 years 4 months ago
    jorimt
    Author
    jorimt

    There was no standalone vsync on the pics you posted. But I did find some of your test to have one.

    I absentmindedly posted the same image twice. I meant to post this as the second image (I’ve corrected it in my original reply):

    comment image

    Vsync off is 21ms while vsync on is 25ms, making it just 4ms, far from 1 1/2 frame (10.35ms) or even just 1 frame (6.9ms).

    I specifically said “up to” 1 1/2 frames. I.E. worst case. It can be anything below that. It varies. But yes, in that particular example, it’s below one frame on average at 144Hz.

    This is because with framerates below the refresh rate, a frame occasionally repeats with standalone V-SYNC due to a missed delivery window, causing stutter. Input lag increases in this case because said stutter is caused by the same frame information being shown twice. G-SYNC and standalone V-SYNC off don’t cause this in the same scenario.

    In other words, if you can’t tolerate tearing and VRR is available, there’s no reason to use standalone V-SYNC over G-SYNC, especially in scenarios where you have a 60 FPS lock running at a higher refresh rate.

    But yes, where VRR isn’t available, FPS-limited V-SYNC is the next best thing where input lag is concerned:
    https://blurbusters.com/howto-low-lag-vsync-on/

    There’s also Scanline Sync, but it’s a little more fiddly to set up and requires better performance to maintain:
    https://forums.blurbusters.com/viewtopic.php?f=2&t=4173&start=70#p36230

    In case of 200hz, vsync off was 19ms, vsync on was 22ms. Vsync on even managed to add up to 28ms (9ms of lag) which was beyond 1 1/2 frame of 200Hz (7.5ms)

    That 1 1/2 frame number isn’t hard science, it was an estimated max off-the-top-of-my-head number for a typical scenario as an example.

    Basically, in those 4 runs averaged out per test, there must have been more instances of frames repeating with the V-SYNC scenario in the 200Hz test than there was in the 144Hz test.

    Again, there’s variance…

    While the higher the refresh rate, the lower the “worth” of a single frame of input lag, when we play a game, our system is running a unique simulation each time. Nothing is static, so the render time of each frame is always going to vary; you can have one run where you have an average reading that is mostly comprised of comparatively “min” level readings, and then another where it’s more comprised of comparatively “max” level readings.

    Like0Vote Down 
    4 years 4 months ago
    coballes19
    Member
    coballes19

    What I mean is that the chart is missing a
    “144hz: Gsync off + Vsync off + 60fps limit (RTSS)”
    which could have told me how much simply upping the refresh rate can counter act the effects of vsync without relying on any adaptive sync tech. Obviously, your input lag can’t go lower than “144hz: Gsync off + Vsync off + 60fps limit (RTSS)”. It’s the absolute minimum input lag.
    There are games where I CAN 100% without a doubt feel the difference between “60hz+60fps(RTTS)+vsync ON” vs “144hz+60fps(RTTS)+vsync ON”
    but not vs “144hz+60fps(RTTS)+vsync OFF” so simply upping the refresh rate while retaining same fps with same vsync turned on without adaptive sync definitely did decrease the input lag. I just don’t know the difference in input lag on 144hz 60fps between vsync on and vsync off.

    I guess it’s beyond the scope of the article. Still would have been nice to know for situations where adaptive sync is not available/feasible.

    Like0Vote Down 
    4 years 4 months ago
    jorimt
    Author
    jorimt

    See my reply above.

    Like0Vote Down 
    4 years 4 months ago
    wpDiscuz

    Related Content

    Featured Content

    Blur Buster Forums

    Blur Busters Forums

    TestUFO Motion Tests

    TestUFO Motion Tests