G-SYNC 101: G-SYNC Ceiling vs. FPS Limit


How Low Should You Go?

Blur Busters was the world’s first site to test G-SYNC in Preview of NVIDIA G-SYNC, Part #1 (Fluidity) using an ASUS VG248QE pre-installed with a G-SYNC upgrade kit. At the time, the consensus was limiting the fps from 135 to 138 at 144Hz was enough to avoid V-SYNC-level input lag.

However, much has changed since the first G-SYNC upgrade kit was released; the Minimum Refresh Range wasn’t in place, the V-SYNC toggle had yet to be exposed, G-SYNC did not support borderless or windowed mode, and there was even a small performance penalty on the Kepler architecture at the time (Maxwell and later corrected this).

My own testing in my Blur Busters Forum thread found that just 2 FPS below the refresh rate was enough to avoid the G-SYNC ceiling. However, now armed with improved testing methods and equipment, is this still the case, and does the required FPS limit change depending on the refresh rate?

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

As the results show, just 2 FPS below the refresh rate is indeed still enough to avoid the G-SYNC ceiling and prevent V-SYNC-level input lag, and this number does not change, regardless of the maximum refresh rate in use.

To leave no stone unturned, an “at” FPS, -1 FPS, -2 FPS, and finally -10 FPS limit was tested to prove that even far below -2 FPS, no real improvements can be had. In fact, limiting the FPS lower than needed can actually slightly increase input lag, especially at lower refresh rates, since frametimes quickly become higher, and thus frame delivery becomes slower due to the decrease in sustained framerates.

As for the “perfect” number, going by the results, and taking into consideration variances in accuracy from FPS limiter to FPS limiter, along with differences in performance from system to system, a -3 FPS limit is the safest bet, and is my new recommendation. A lower FPS limit, at least for the purpose of avoiding the G-SYNC ceiling, will simply rob frames.



507 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
sleepynoodle
Member
sleepynoodle

Why do you think that basically no (to my understanding) cs:go pros use these settings or anything similar? Just regular settings with no capped FPS. Is it lack of knowledge or what do you think?

doodles
Member
doodles

Hey jorimt,

Just a quick question after reading your guide on G-sync + V-sync and input lag…

So I understand that if G-sync is used in combination with V-sync, it would essentially be forcing the computer to deliver steady frame timing over the period over a second (so for 144 Hz they would all be 6.9 ms versus the 144 frames averaging out to 6.9 ms). Also from what I understand, all of this discussion is related to changing these settings withing the NVIDIA control panel.

What does this mean with regards to in-game settings say for a game like Apex Legends or Modern Warfare? Do we have ENABLE V-sync within the individual games as well, to see the benefits from the G-sync + V-sync settings in the Control Panel? Or is doing so not necessary, and might cause other issues?

Vegetariano
Member
Vegetariano

Hello, jorimt.

This guide just rocks. I have just one question about the new Nvidia driver setting “Max Frame Rate”. From now on, I can set the maximum frame rate that the GPU will render a game directily in the driver.

Is there a difference in latency between set the max FPS at the driver new option or in the RTSS?

Thank you!

andregm3
Member
andregm3

New LG Tvs with G-Sync (Firmware 04.71.04):

1. Improvement
1) Featuring NVIDIA G-Sync Compatible.

2. Applicable model list
65SM9500PUA
75SM9070PUA
86SM9070PUA
55SM9000PUA
65SM9000PUA
75SM8670PUA
49SM8600PUA
55SM8600PUA
65SM8600PUA
75UM8070PUA
75SM8670AUA
65SM8600AUA
82UM8070PUA
86UM8070PUA
86UM8070AUB
82UM7570PUB
86UM7570PUB
OLED55B9PUA
OLED65B9PUA
OLED55B9PUB
OLED65B9PUB
OLED77B9PUA

TheLonelyDevil
Member
TheLonelyDevil

>And while each frame is still rendered in 16.6ms, and delivered in intervals of 60 per second on the higher refresh rate display, they are scanned in at a much faster 6.9ms per.

Could you explain this line a bit more? In a 240 Hz 60 FPS CAP example, for instance?

wpDiscuz