Originally posted by sinepgib
View Post
Announcement
Collapse
No announcement yet.
X.Org Server Adds "AsyncFlipSecondaries" To Deal With Crappy Multi-Monitor Experience
Collapse
X
-
- Likes 1
-
Originally posted by whitecat View Post
Not on clone mode.
Leave a comment:
-
- Likes 1
Leave a comment:
-
Originally posted by sinepgib View PostSome say every reality can be expressed by the digits of pi. It's clear it can also be expressed with the names of bands.
Leave a comment:
-
Originally posted by cl333r View PostI get your pessimism but strangers on the internet are the best people on Earth. One can only describe them as a mix of MLK, Einstein, Confucius and Aristotle.
You gave me a good laugh, thanks.
Leave a comment:
-
Originally posted by MrCooper View Post
There's no reason why a Wayland compositor can't drive separate monitors at different refresh rates (without tearing), no matter if they show the same or different contents.
This change is a workaround for an architectural limitation of Xorg (single framebuffer which spans all outputs).
- Likes 3
Leave a comment:
-
Originally posted by tomas View PostAnd assuming you are correct, is that a limitation of Wayland itself or just in a specific compositor like Mutter, Sway or Kwin?
Do all of the above compositors have this problem you claim and can it then be derived to be a design problem in the Wayland protocol itself?
This change is a workaround for an architectural limitation of Xorg (single framebuffer which spans all outputs).
- Likes 3
Leave a comment:
-
Originally posted by whitecat View Post
Not on clone mode.
Do all of the above compositors have this problem you claim and can it then be derived to be a design problem in the Wayland protocol itself?
Leave a comment:
-
Originally posted by treba View PostOn Wayland you can have multiple screens at different refresh rates, each of them having fullscreen or non-fullscreen "unredirected"/direct scanout clients. Without tearing. In other words a no compromise situation. I think atm only Weston is already capable of doing such a extreme situation (especially the non-fullscreen direct scanout case, which requires overlay plane support via atomic KMS). But a typical situation like screen A 144Hz with a unredirected game + screen B 60Hz + screen C 60Hz works just fine without tearing on Gnome - and if I'm not mistaken on Sway and KDE as well.
That's possible because unlike on X11 there's no "global" VSync on Wayland. Clients receive frame callbacks (or/and presentation times) for the screens they are visible on. Clients on different screens don't need to be in sync.
- Likes 3
Leave a comment:
Leave a comment: