Announcement

Collapse
No announcement yet.

KWin-LowLatency: An Effort To Yield Less Stutter & Lower Latency With The KDE Desktop

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #21
    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!

    Comment


    • #22
      Originally posted by Mario Junior View Post
      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!
      Too bad KWin on Xorg was declared legacy before it was neither finished nor fixed. Poor management of priorities of what's important.

      Comment


      • #23
        Originally posted by aufkrawall View Post
        Too bad KWin on Xorg was declared legacy before it was neither finished nor fixed.
        Really? Because KWin on wayland is completely broken for the majority of users, as far as I can tell.

        Comment


        • #24
          Originally posted by fuzz View Post
          Really? Because KWin on wayland is completely broken for the majority of users, as far as I can tell.
          But at least the Wayland version doesn't introduce stutter, unlike the X11 one. They haven't fixed it in years and it still doesn't look like it.
          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


          • #25
            Originally posted by fuzz View Post
            Really? Because KWin on wayland is completely broken for the majority of users, as far as I can tell.
            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


            • #26
              Originally posted by M@GOid View Post
              Strange, 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.
              The problem is heavy stutter. KWin is unable to sync every frame perfectly. 60FPS videos at 120Hz also have the problem, of course. Kwin constantly "hiccups" every 2 or 3 seconds, dropping frames.

              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.

              Comment


              • #27
                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.
                It's far from ready due to stuff like this: https://bugs.kde.org/show_bug.cgi?id=387313

                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

                Comment


                • #28
                  Originally posted by oiaohm View Post

                  https://www.youtube.com/watch?v=FYItn1jvkbI

                  Really not as broken as you would first presume.
                  As long as it still crashes when doing simple tasks on modern Intel-only hardware (as is the case for my setup!), it's broken.

                  Comment


                  • #29
                    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.
                    It's 100% unusable for me. The bugs have been documented as far as I can tell. Theoretical use cases don't mean something works well. Not blaming anyone, it's just how software development goes.

                    Comment


                    • #30
                      Originally posted by czz0 View Post
                      Wayland 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.
                      But Windows (the compositor, DWM.EXE) forces Vsync on all windows. It seems to work fine there.

                      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

                      Working...
                      X