Holly shet, finally! Finnaly someone will make something about this problems on Kwin. I already reported in another thread about my experience with Plasma on AMD GPU. Kwin needs a rework urgently!
Announcement
Collapse
No announcement yet.
KWin-LowLatency: An Effort To Yield Less Stutter & Lower Latency With The KDE Desktop
Collapse
X
-
Originally posted by Mario Junior View PostHolly shet, finally! Finnaly someone will make something about this problems on Kwin. I already reported in another thread about my experience with Plasma on AMD GPU. Kwin needs a rework urgently!
Comment
-
Originally posted by fuzz View PostReally? Because KWin on wayland is completely broken for the majority of users, as far as I can tell.
Their rejection of auto-unredirect for fullscreen is pathetic too, like if I would always want to manually switch compositing on and off when alt + tabbing while gaming...
Comment
-
Originally posted by fuzz View PostReally? Because KWin on wayland is completely broken for the majority of users, as far as I can tell.
Really not as broken as you would first presume. KWin on wayland has some very interesting new testing features. Like this one where you can test for multi display output with a single display.
- 1 like
Comment
-
Originally posted by [email protected] View PostStrange, here works fine. What is exactly the problem? What is your setup? I use a AMD card with radeonsi driver, VLC video player and KDE to watch F1 races on my PC (using a PixelView USB adapter), but here is a 60Hz broadcast and I use a 120Hz Benq monitor.
NVidia driver on a 165Hz display. (I only use 120Hz or 100Hz for the desktop, depending on whether I watch 24/30/60FPS video (movies, NTSC) or 25/50FPS (PAL) video. The attitude of the kwin developers is the usual "the human eye can't see more than blah blah frames per second" or "nobody needs a display with more than 60Hz" nonsense.
- 1 like
Comment
-
Originally posted by oiaohm View Post
https://www.youtube.com/watch?v=FYItn1jvkbI
Really not as broken as you would first presume. KWin on wayland has some very interesting new testing features. Like this one where you can test for multi display output with a single display.
So deprecating X11 path before Wayland path is in production quality state is bizarre. And adaptive sync situation is even worse, due to Wayland protocol itself missing features:
https://bugs.kde.org/show_bug.cgi?id=405912
https://gitlab.freedesktop.org/wayla...land/issues/84
https://github.com/swaywm/wlroots/issues/1406
I'm KDE user, and would like to switch to Wayland, but it's just not ready yet. And it seems it will still take years to get to a modern Wayland + Vulkan compositing.
See also: https://github.com/swaywm/wlroots/pull/1214
- 3 likes
Comment
-
Originally posted by oiaohm View Post
- 2 likes
Comment
-
Originally posted by oiaohm View Post
https://www.youtube.com/watch?v=FYItn1jvkbI
Really not as broken as you would first presume. KWin on wayland has some very interesting new testing features. Like this one where you can test for multi display output with a single display.
Comment
-
Originally posted by czz0 View PostWayland will always be useless for gaming so long as they keep forcing Vsync, with no way to disable it.
The fact that Wayland and Gnome developers thought it would be okay to force Vsync and even hard cap the refresh rate to 60Hz (only recently fixed in Gnome), makes me have almost zero trust in them for gaming performance.
I agree being able to disable it would be nice, but I don't think it's as big of a detriment as you think.
Comment
Comment