16 ms·

It is unfortunate but forced vsync means I will never adopt Wayland. I do not want a frame+ delay when I'm gaming. I do not want v-sync lag when my framerate oc

It is unfortunate but forced vsync means I will never adopt Wayland. I do not want a frame+ delay when I'm gaming. I do not want v-sync lag when my framerate occasionally drops below my 240hz refresh rate. I don't even especially like X11, I just don't want vsync forced on me.

papercrane 3y ago
I'm not sure how widely supported it is, but Wayland has a protocol to support turning off v-sync. https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/65 https://gitlab.freedesktop.org/wayland/wayland-protocols/-/m...
- clhodapp 3y ago
  I believe that Mesa has just recently added support.
zamadatix 3y ago
Wayland doesn't actually add an additional frame of latency like you'd expect by just saying "vsync" in a normal context. https://zamundaaa.github.io/wayland/2021/12/14/about-gaming-on-wayland.html https://zamundaaa.github.io/wayland/2021/12/14/about-gaming-... In cases where your game occasionally dips below 240hz enabling VRR will prevent additional latency without requiring you introduce tearing in the display pipeline.
- errantmind 3y ago
  > If you require the absolutely lowest latency possible though and don’t care about screen tearing then X without compositing, with VSync disabled is a better fit for you. You can re-evaluate once the possibility to have VSync disabled is implemented in your compositor of choice and the measured increased volatility in latency (99th percentile) with immediate mode is fixed. I enjoyed the post, thanks. I suppose I'll wait then and re-evaluate when Wayland's 'immediate mode' is fixed and it is roughly comparable to X11 without a compositor. I go to great lengths to minimize my latency so this is really the only factor that matters to me.
johnny22 3y ago
tearing can be optionally enabled via recent protocol extensions, but I'm not sure how widely implemented it is yet.

papercrane 3y ago

I'm not sure how widely supported it is, but Wayland has a protocol to support turning off v-sync. https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/65 https://gitlab.freedesktop.org/wayland/wayland-protocols/-/m...

clhodapp 3y ago
I believe that Mesa has just recently added support.

zamadatix 3y ago

Wayland doesn't actually add an additional frame of latency like you'd expect by just saying "vsync" in a normal context. https://zamundaaa.github.io/wayland/2021/12/14/about-gaming-on-wayland.html https://zamundaaa.github.io/wayland/2021/12/14/about-gaming-... In cases where your game occasionally dips below 240hz enabling VRR will prevent additional latency without requiring you introduce tearing in the display pipeline.

errantmind 3y ago
> If you require the absolutely lowest latency possible though and don’t care about screen tearing then X without compositing, with VSync disabled is a better fit for you. You can re-evaluate once the possibility to have VSync disabled is implemented in your compositor of choice and the measured increased volatility in latency (99th percentile) with immediate mode is fixed. I enjoyed the post, thanks. I suppose I'll wait then and re-evaluate when Wayland's 'immediate mode' is fixed and it is roughly comparable to X11 without a compositor. I go to great lengths to minimize my latency so this is really the only factor that matters to me.

johnny22 3y ago

tearing can be optionally enabled via recent protocol extensions, but I'm not sure how widely implemented it is yet.