G-SYNC 101: G-SYNC vs. V-SYNC w/FPS Limit


So Close, Yet So Far Apart

On the subject of single, tear-free frame delivery, how does standalone double buffer V-SYNC compare to G-SYNC with the same framerate limit?

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, but for 60Hz (remember, a “frame” of delay is relative to the refresh rate), the numbers are relatively close. So what’s so great about G-SYNC’s ability to adjust the refresh rate to the framerate, if the majority of added input latency with V-SYNC can be eliminated with a simple FPS limit? Well, as the title of this section hints, it’s not quite that cut and dry…

While it’s common knowledge that limiting the FPS below the refresh rate with V-SYNC prevents the over-queuing of frames, and thus majority of added input latency, it isn’t without its downsides.

Unlike G-SYNC, V-SYNC must attempt to time frame delivery to the fixed refresh rate of the display. If it misses a single one of these delivery windows below the maximum refresh rate, the current frame must repeat once until the next frame can be displayed, locking the framerate to half the refresh rate, causing stutter. If the framerate exceeds the maximum refresh rate, the display can’t keep up with frame output, as rendered frames over-queue in both buffers, and appearance of frames is delayed yet again, which is why an FPS limit is needed to prevent this in the first place.

When an FPS limit is set with V-SYNC, the times it can deliver frames per second is shrunk. If, for instance, the FPS limiter is set to 59 fps on a 60Hz display, instead of 60 frames being delivered per second, only 59 will be delivered, which means roughly every second a frame will repeat.

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. This is why it is recommended to set a V-SYNC FPS limit mere decimals below the refresh rate via external programs such as RTSS.

That said, an FPS limit is superior to no FPS limit with double buffer V-SYNC, so long as the framerate can be sustained above the refresh rate at all times. However, G-SYNC’s ability to adjust the refresh rate to the framerate eliminates this issue entirely, and, yet again, beats V-SYNC hands down.



3898 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
mahmcud
Member
mahmcud

Hey, I followed the settings in this guide (G-SYNC and NVIDIA V-Sync enabled, with the NVIDIA Max Frame Rate limit set to 3 FPS below my monitor’s refresh rate), but I’m having an issue: in some games, such as RDR2, GTA V, and AC Shadows, using NVIDIA Control Panel’s Max Frame Rate limiter doesn’t feel smooth while other limiters like rtss work normal. Is there any way to fix this?

Robi
Member
Robi

Hey Jorimt, i did some testing again and found that in Cyberpunk2077 Frame Gen increases your latency in less gpu demanding areas, what do you know about this?

Here is my testings:

Question: Does DLSS Frame Generation increase PC Latency when GPU utilization decreases? (Cyberpunk 2077)

My settings:

– DLSS Super Resolution: Quality Transformer Model 2
– DLSS Frame Generation: 2×
– FPS cap: 157 RTSS (Async)
– NVIDIA Reflex: enabled (By default when FG)
– G-SYNC and V-Sync (NCP) configured correctly
– All graphics max + Path Tracing

My observations:

– In demanding areas, NVIDIA overlay PC Latency is around 35 ms.
– In less demanding areas, PC Latency rises to around 55 ms, despite lower GPU utilization.
– With Frame Generation disabled, I get around 100 FPS and 26 ms average latency.
– Interestingly, switching to DLAA while keeping Frame Generation enabled increases GPU utilization and reduces latency again but only in the less gpu demanding area.

I’ve repeated these tests, and I can feel the difference in responsiveness, I play lots of FPS games and I can physically feel the difference between 35ms and 55ms this is not a margin of error from Nvidia Overlay LAT.

Has anyone observed Frame Generation causing higher latency at lower GPU utilization?

wbotter
Member
wbotter

Hey! Wondering if V-Sync is applicable to Gsync Pulsar monitors? I just got one, went from PG27AQDM to the XG27AQNGV after receiving not one but TWO defective PG27AQWP-W’s!!! After the second AQWP-W started intermittently dropping signal due to the UHBR-20 handshake failing, works flawlessly in UHBR-13.5 with DSC, but for a $1250 monitor, I’d expect it to work as intended. So, I ultimately gave up on the flagship and was just searching for 27″ or less 1440p monitors over the 240hz my AQDM was already giving me, and the Gsync pulsar caught my eye. I had a BenQ Zowie with DyAc+ a few years ago and loved it, so yeah the curiosity got me with this monitor. I currently have a 9800x3d, cl 28 32gb 6000mhz, and a 5070. (Yes, Ik my gpu is hardcore limiting my FPS). I play competitive games mostly, in “comp settings” (basically low everything), DLSS Quality or Balanced using Model K, and I’ll get 384fps peaks, 271 avg, 202 1% lows and an average PCL of 10. All captured using frameview in marvel rivals after many many many “change one setting,” *capture for 45min-1hr of gameplay,* did this increase or decrease performance? lol! (All without DLSS FG. I’m not opposed to DLSS FG 2x, but 3x and above my PCL climbs quite a bit.)

Anyways, got any advice to get the most out of the GSYNC Pulsar Monitors? Or same rules apply? Thanks!!

user2422
Member
user2422

In an earlier comment you mentioned that ULLM is somewhat inefficient compared to Reflex or a manual limit, if i were to use Gsync + Vsync + ULLM, would that starving of the max queued frames and the potential stutters that come with it even apply considering that ULLM is auto limiting the fps in this configuration? Like does it limit low enough to prevent this from even happening?

Also when using Gsync + Vsync and then only enabling ULLM via Inspector without setting max pre-rendered frames to 1 (which ULLM would’ve otherwise done if it was applied via NVCP or NVApp), would this then be just an auto limiter without the other effects of ULLM? I’ve tried this configuration in-game and the auto limit still applies but I’m unsure whether or not ULLM will have any other impact in this configuration.

eonjr
Member
eonjr

Hi, thank you for the guides! But I have something to ask. My laptop has a 300hz refresh rate that is also GSync compatible. I have it capped at 285 using a formula that I saw on a Reddit post a while ago (via NVIDIA APP > Max Frame Rate).

I unfortunately get this gray flickering during gaming but I can get used to it. However, what I cannot stand is, when I tried using editing software (like Adobe Premiere Pro), the flickering was also present despite me having turned off GSync specifically for that app (via NVIDIA App). Is there something I am doing wrong? What can be done to completely eliminate flickering for non-game apps?

wpDiscuz