Not sure if its XWayland but the vision stutters a lot while everything else is smooth. Also X11 seems unusable for some reason on KDE because I get a lot of glitchy artifacts (and Direct Mode seems to be enabled)

Edit: Using an AMD 6750xt with i5-8600k on Arch Linux with KDE Wayland

  • PureTryOut
    2·
    1 year ago

    I’m jealous you’re even able to play it on X11. I’ve played it exclusively on Windows purely because VR on Linux is too buggy with my setup. At first the VR window only showed on my desktop and not actually on my Valve Index, and after finding a workaround it only plays at 90Hz with stuttering. Even if I manage to play through that there is the issue that audio doesn’t play through the headset and you can’t configure audio devices from within SteamVR. It’s a big mess honestly…

    Monado (a FOSS OpenXR runtime) works fine however, I wish Steam just used that underneath…

      • PureTryOut
        1·
        1 year ago

        Not just switching audio when appropriate, I can’t get it to play any audio on the headset whatsoever. Yeah it’s still possible to play with the audio on my PC speakers but it’s a severely worse experience sadly.

        Personally I’m experiencing https://github.com/ValveSoftware/SteamVR-for-Linux/issues/334 so I can’t help you sorry. Hope you find the answer though!

        • ReakDuckOP
          1·
          1 year ago

          Seems like the stutters are the reason why async is disabled, turning this on gives me artifacts even on wayland. Anyways, afriend has the same GPU but uses Fedora Gnome instead of Arch Linux KDE so maybe we find a pattern?

          At first I had the same Issue as you… till I found out that my DisplayPort cable was half-way plugged in. Took me 2 Hours to find out. Everything acted like everything worked except that the compositor was on Desktop instead in the Headset.

          • PureTryOut
            1·
            1 year ago

            Cable only half-way plugged in, if only I had the same problem 😅

            In my case it seems to be an unfortunate hardware/software combo bug. I’m due for a new PC sometime soon anyway, I’ll have to be patient for a bit.