https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #26 from Samuel <samping...@gmail.com> --- (In reply to Erik Kurzinger from comment #25) > But is that really the solution users want? Sure, it would technically let > the game run at an uncapped refresh rate, but as I understand it the main > reason people want to run games that way is to minimize input latency, and > they're willing to accept possible tearing as a trade-off (e.g. competitive > gamers and whatnot). So would it maybe make more sense to have Kwin do > tearing flips instead for direct scan-out applications? There are open MR for allowing tearing in Wayland - 1. https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/65 ("Main blocker is, KMS doesnt support tearing due to atomic interface" - Simon Ser) 2. https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/103 -- You are receiving this mail because: You are watching all bug changes.
