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

  • #61
    Originally posted by aufkrawall View Post
    Where do these idiotic ideas originate from?
    Nothing has changed with Windows 10 in terms of vsync, except of some limitations of UWP games with upscaling/downscaling.
    There is one change adding the registry key to turn vsync full off of under 9x/Me under windows 10 gets auto deleted. Its not like that registry key has been doing anything it was never connected up in 2000 forwards todo anything so it just sat wasting registry space. People have been turning it on and claiming differences for ages and it basically been a placebo effect. Its like how people for a long time would mess with Linux kernel nice settings on processes and claim differences before it was even hooked up.

    The fact that windows only party turns vsync limitations off gamers have not complained about. Only party turning of massively reduces tearing by not displaying part ready buffers.

    Comment


    • #62
      oiaohm I just fired up AC: Unity on both Windows and Linux to check for a shadow rendering bug, and it both equally tears like hell in fullscreen without vsync.

      Comment


      • #63
        Originally posted by aufkrawall View Post
        oiaohm I just fired up AC: Unity on both Windows and Linux to check for a shadow rendering bug, and it both equally tears like hell in fullscreen without vsync.
        That test shows issues just with userspace disable of vsync in form. Run X11 without a compositor with vsync off in the x11 server you will see a change for the worse. You cannot even drag basic windows around the X11 screen without them tearing in that setup let alone more fancy test. Of course that does not help the Unity test..

        Comment


        • #64
          Originally posted by debianxfce View Post
          I see only tearing when moving windows fast around the Xfce desktop. Applications work fine without compositing and scrolling in the web browser does not cause tearing. So I do not use the compositor or anything that slows down system performance.
          X11 server will in fact tear with vsync on with compositor off if you drag windows fast enough because the X11 server vsync implementation is nice and buggy.. Lets just say tearing gets worse when you turn X11 vsync off as well.

          Vsync total off scrolling the web browser it will from time to time tear there as well on x11 server. The fact you said it was not tearing you have left the servers vsync on..

          Comment


          • #65
            Without compositor or TearFree, Xorg can only be free of tearing for fullscreen windows (because they trigger page flipping). Drag a video player window playing a juddertest video to the very top or bottom of the screen to spot the tearing in windowed mode. That has nothing to do with the chosen DE, believing otherwise is just a proof of incompetence.

            That being said, I don't know why anyone should care about the tearing without compositor or TearFree. These features are there for a purpose and should function without issues (otherwise fill a bug report)...

            Comment


            • #66
              Originally posted by debianxfce View Post
              In gnome3, kde and some others you have tearing, but not with the Xfce desktop. The Xfce desktop is light and fast without compositing and any vsync on.

              Note that when Tearfree is auto, it is off normally. See man amdgpu.
              Really debianxfce you cannot read and understand.
              If this option isn't set, the default value of the property is auto, which means that TearFree is on for rotated outputs, outputs with RandR transforms applied and for RandR 1.4 slave outputs, otherwise off.
              Tearfree auto is half on. Heres the fun fact with xfce when screen it not rotated it sets RandR rotation of 0 what effectively means you have turns on TearFree to on because to the system the screen is rotated. Welcome to X11 stupidity.

              XFCE TearFree is on unless you particularly set it off.

              Comment


              • #67
                Originally posted by debianxfce View Post
                You invent your own theories., an example:



                A property that has values auto, on and off can not be half on. Tearfree is a digital value, not analog. Wayland is garbage and will never replace X, see:
                https://gitlab.freedesktop.org/wayland/wayland/issues
                http://lmgtfy.com/?q=xfce+how+to+fix+screen+tearing

                Comment


                • #68
                  Originally posted by debianxfce View Post

                  http://www.oc-burner.de/ftp/Videos/j...ertest_120.mp4

                  When running above I have a couple of centiliters tearing at the bottom of the bar. I can not see such a thing when watching TV with VLC. The Xfce desktop is light and fast, try it yourself.
                  Well said. I have absolutely no clue what this user is doing not using Xfce. Probably an IBM drone. I don't experience any tearing on my Xfce desktop either as long as I've had a few shots of vodka before hand. It's like the users here don't even know how to use good software.

                  Comment


                  • #69
                    Damn, I think we've driven him into a schizophrenic psychosis.

                    Comment


                    • #70
                      Originally posted by debianxfce View Post
                      A property that has values auto, on and off can not be half on. Tearfree is a digital value, not analog.
                      Half on is possible even with Tearfree. Because compositor can say Tearfree on and from mesa application can say Tearfree off. This means the buffer merges inside the application are done without consideration to tearing but the output tearing is considered. This is the half on state. Part of the stack has it on part of the stack has it off.

                      Originally posted by debianxfce View Post
                      Wayland is garbage and will never replace X, see:
                      https://gitlab.freedesktop.org/wayland/wayland/issues
                      That not many issues.
                      https://gitlab.freedesktop.org/group...s?state=opened

                      Really Wayland does not have that many bugs.

                      Comment

                      Working...
                      X