Arch Linux

tekstryder

Member

Registered: 2013-02-14

Posts: 336

Re: For those using Xorg, do you have plans to move to Wayland?

Which frankly is hilarious

Hilarious as in sad.

If a user "needs" screen tearing, that user "needs" better hardware.

Support for this pathetic-concession protocol will eventually land in Mutter as well, thankfully behind a flag.

• https://gitlab.gnome.org/GNOME/mutter/- … uests/3797

Sigh.

seth

Member

Registered: 2012-09-03

Posts: 65,015

Re: For those using Xorg, do you have plans to move to Wayland?

Hilarious as in hilarious.
Then: getting a completely synced output in X11 is hard because of the multiple layers involved, we need a more straight forward protocol. Wayland will fix this once and for all. It will break pretty much everything else. But it will finally get use perfect frames (well, except for bugs in the drivers and also nobody knew that vulkan was that hard…)
Now: Give us back tearing! Vsync lags and that sucks! And I get fragged all the time!!!

Reality: run a 200+fps output, then neither problem matters anymore - it's the whole point of VRR and high FPS outputs (and not that you can totally "feel" the difference between 85Hz and 120Hz…, that's esoteric nonsense)
And it will also take care of what I assume to be the *actual* problem here, which is: in order to not stall the render thread waiting for the vblank signal, everyone's gonna use triple buffering what introduces 1 frame lag guaranteed - regardless of the rest of your hardware.
The only thing to combat that is to make frames last really short.

I will say though, that back during the war… errr… LAN party era where 60fps was the limit, a fistful of gamers could legitimately take advantage out of the tearing by essentially exploiting bugs:
You could see where where the target was in the next frame but the entire target logic was still in the old frame, essentially playing one frame in the future…
But I doubt that's what's driving the calls to disable vsync today.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc