Announcement

Collapse
No announcement yet.

AMD's Marek Has A Patch Helping To Reduce Gallium3D Input Lag

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

  • #41
    oibaf OK, just tested on Mesa Git.

    Code:
    OpenGL vendor string: X.Org
    OpenGL renderer string: Radeon Vega Frontier Edition (VEGA10, DRM 3.27.0, 5.0.2-artix1-1-ARTIX, LLVM 9.0.0)
    OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.2.0-devel (git-fc455797c1)
    OpenGL core profile shading language version string: 4.50
    OpenGL core profile context flags: (none)
    OpenGL core profile profile mask: core profile
    OpenGL core profile extensions:
    OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.2.0-devel (git-fc455797c1)
    OpenGL shading language version string: 4.50
    OpenGL context flags: (none)
    OpenGL profile mask: compatibility profile
    OpenGL extensions:
    OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.2.0-devel (git-fc455797c1)
    OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
    OpenGL ES profile extensions:
    Sadly, misbehavior persists.

    Comment


    • #42
      Originally posted by tildearrow View Post
      oibaf OK, just tested on Mesa Git.
      Sadly, misbehavior persists.
      I tested your triangle program and it stutters when running in a window but not when it is full screen. No Xfce compositor or the amdgpu tearfree option enabled. Freesync is enabled.

      You can not see stuttering in games.

      And you can use the glXWaitForMscOML function to remove stuttering when windowed. So there is no problems with open source graphics drivers.

      Code:
      [email protected]:/media/ssd/tmp$ inxi -bM
      System:
        Host: ryzenpc Kernel: 5.1.0-rc5+ x86_64 bits: 64 Desktop: Xfce 4.13.2
        Distro: Debian GNU/Linux 10 (buster)
      Machine:
        Type: Desktop Mobo: ASUSTeK model: PRIME B350M-K v: Rev X.0x
        serial: <root required> UEFI [Legacy]: American Megatrends v: 4602
        date: 03/07/2019
      CPU:
        6-Core: AMD Ryzen 5 1600 type: MT MCP speed: 3389 MHz
      Graphics:
        Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
        driver: amdgpu v: kernel
        Display: x11 server: X.Org 1.20.4 driver: amdgpu
        resolution: 3840x2160~60Hz
        OpenGL:
        renderer: Radeon RX 570 Series (POLARIS10 DRM 3.32.0 5.1.0-rc5+ LLVM 9.0.0)
        v: 4.5 Mesa 19.2.0-devel - padoka PPA
      Last edited by debianxfce; 05-16-2019, 12:36 AM.

      Comment


      • #43
        Originally posted by debianxfce View Post

        I tested your triangle program and it stutters when running in a window but not when it is full screen. No Xfce compositor or the amdgpu tearfree option enabled. Freesync is enabled.
        ...so it does work on full-screen? Well, that's weird. Mesa devs should do something so this works windowed too... (AMDGPU-PRO and NVIDIA work)

        Originally posted by debianxfce View Post
        You can not see stuttering in games.
        Of course, because this only was a test program to reproduce a slight bug (which can get annoying for things like my compositor, however).

        Originally posted by debianxfce View Post
        And you can use the glXWaitForMscOML function to remove stuttering when windowed. So there is no problems with open source graphics drivers.
        ...which is why there is a commented glXWaitForMscOML in the code, but that's more of a workaround, and a pretty ugly one...

        Comment


        • #44
          Originally posted by tildearrow View Post

          ...so it does work on full-screen? Well, that's weird. Mesa devs should do something so this works windowed too... (AMDGPU-PRO and NVIDIA work)



          Of course, because this only was a test program to reproduce a slight bug (which can get annoying for things like my compositor, however).



          ...which is why there is a commented glXWaitForMscOML in the code, but that's more of a workaround, and a pretty ugly one...
          Please forgive my ignorance, I do not know what is "vsync" or input lag, I am just talking nonsense.

          Comment


          • #45
            Originally posted by tildearrow View Post
            ...so it does work on full-screen? Well, that's weird. Mesa devs should do something so this works windowed too.
            Why when you can use the glXWaitForMscOML function.

            Originally posted by tildearrow View Post
            which can get annoying for things like my compositor, however
            Use the Xfce desktop and do not reinvented a wheel.

            Originally posted by tildearrow View Post
            ...which is why there is a commented glXWaitForMscOML in the code, but that's more of a workaround, and a pretty ugly one...
            Why so, it is a documented OpenGL extension, not a hack.
            https://www.khronos.org/registry/Ope...nc_control.txt
            Last edited by debianxfce; 05-16-2019, 07:16 PM.

            Comment


            • #46
              Originally posted by debianxfce View Post
              Why when you can use the glXWaitForMscOML function.



              Use the Xfce desktop and do not reinvented a wheel.



              Why so, it is a documented OpenGL extension, not a hack.
              https://www.khronos.org/registry/Ope...nc_control.txt
              Use the XFCE desktop which does not support VSYNC and has screen tearing issues in 2019.

              http://lmgtfy.com/?q=XFCE+screen+tearing

              Comment


              • #47
                Originally posted by debianxfce View Post
                Why when you can use the glXWaitForMscOML function.
                You don't work around defects. You fix them.

                Originally posted by debianxfce View Post
                Use the Xfce desktop and do not reinvented a wheel.
                Stop it already. Not everything is XFCE.

                Originally posted by debianxfce View Post
                Why so, it is a documented OpenGL extension, not a hack.
                https://www.khronos.org/registry/Ope...nc_control.txt
                It is only meant to be used when necessary. Otherwise they encourage setting the swap interval.

                Comment


                • #48
                  Originally posted by tildearrow View Post
                  You don't work around defects. You fix them.
                  Kde is full of defects and you work around defects when developing your compositor.
                  Make a bug report and if AMD do not react, use a workaround. They have important things to do.

                  Originally posted by tildearrow View Post
                  Stop it already. Not everything is XFCE.
                  The Xfce desktop is the best. No need to develop a compositor.

                  Originally posted by tildearrow View Post
                  It is only meant to be used when necessary. Otherwise they encourage setting the swap interval.
                  You need that function, so use it.

                  Comment


                  • #49
                    Originally posted by retardxfce View Post
                    Use the XFCE desktop which does not support VSYNC and has screen tearing issues in 2019.
                    Stop using gnome3, it makes you mad. When the Xfce compositor is enabled there is no tearing. Note that compositors slow down performance.

                    Comment


                    • #50
                      Originally posted by debianxfce View Post
                      Stop using gnome3, it makes you mad. When the Xfce compositor is enabled there is no tearing. Note that compositors slow down performance.
                      Compositors do not slow down performance. You are simply using crappy hardware (RX560 lol) with some shitty athlon CPU so dont be surprised that your desktop performs like crap.

                      Comment

                      Working...
                      X