4 ms·
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/20
by 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.