Is v-sync broken?

[Sean8102]

No matter what combo of window mode (fullscreen. borderless etc), v-sync (double or triple buffered) I set, the game seems to run un capped. ~160 FPS on my 3080.

Only thing that works is the FPS cap. But if I don't set it to a little bellow my refresh rate (75 Hz) I get some screen tearing.

Mainly just wondering if anyone else is experiencing this?

Using DX 11 or Vulkan gives same results.

[Dave]

Originally posted by Sean8102:

Originally posted by Dave:

If a game doesn't do anything internally different for DX games and set to 3x buffering, it will just fall back to double buffering. No harm in enabling it.

The main drawback to 3x or rendering ahead is it increases input lag.

According to GFE overlay my render latency stays around 7 MS regardless of these settings (window mode, vsync etc)

That's misleading. What you're talking about is the time to render a frame. Lock your FPS at 30, and watch that skyrocket. It won't have any affect on input lag. That ms will change on a lot of factors.

You can have 5ms rendertimes AND have input lag because you are rendering too many frames in advance.

[Sean8102]

forcing v-sync for BG3 in NVCP worked

Thanks guys.

[Dave]

Originally posted by Sean8102:

forcing v-sync for BG3 in NVCP worked

Thanks guys.

That's really odd it wasn't working. It's like your game was in borderless and not FS.

[Sean8102]

Originally posted by Dave:

Originally posted by Sean8102:

forcing v-sync for BG3 in NVCP worked

Thanks guys.

That's really odd it wasn't working. It's like your game was in borderless and not FS.

after forcing through NVCP it works in all 3 window modes (fullscreen, borderless, windows).

IDK just glad that worked lol

[IchigoMait]

Originally posted by Dave:

Originally posted by Sean8102:

forcing v-sync for BG3 in NVCP worked

Thanks guys.

That's really odd it wasn't working. It's like your game was in borderless and not FS.

If you're in borderless, vsync still works, the only instance it doesn't work, is when you try to use the ingame setting and the devs force disable it (ubisoft likes to do it, but you can still force it on through their settings file, or just use drivers), but with certain monitors with certain drivers and windows versions you can still get tearing even below refresh rate, while in other scenarios like just having a different windows and drivers, you might not get tearing while in borderless and below refresh rate, and for both scenarios the same game, the same monitor.

On windows 7 you had windows aero for it, which dropped frames that went above refresh rate basically what fast sync does for dedicated window modes (mostly fullscreen where alt tabbing has issues), so you would never get tearing without vsync in borderless/window modes, but after going to win10, borderless doesn't help.
Adaptive vsync was even better in win7, in win10 it's useless.
In win10 above vsync works though better, and even if adaptive is useless, having vsync on while below refresh rate won't cause stuttering, unlike in win7 or below, where standard vsync below refresh rate was just a stutter fest when scenes/camera moved.

So yeah, best settings:
win 7 = borderless, fps limit below refresh rate, and/or fast sync for fullscreen dedicated mode or also an option adaptive vsync, it turns vsync off when below refresh rate. no idea about gsync, never got to use it with win 7 or below.

win 10 = borderless, fps limit below refresh rate, standard vsync forced on or when gsync is on the vsync forced off, but some exceptions where gsync doesn't work you can try forcing for that specific game fast sync when in fullscreen dedicated mode or standard vsync for the rest. (fast sync has a more stable framerate it doesn't change constantly more in 10 fps increments, probably because of the frame drop mechanic, but yeah do use a fps limiter when using fast sync, it doesn't cap it)