Almost every distro I’ve used so far ends up having problems installing Steam due to mismatching i386 packages. I’ve heard that they’re being removed upstream. Anyone happen to know a timeline?

  • Leaflet@lemmy.worldEnglish
    0·
    3 days ago

    I use the Steam flatpak. The nice thing about that is that 32bit libraries aren’t installed on the host system.

        • Fisch@discuss.tchncs.deEnglish
          0·
          2 days ago

          Works perfectly fine, actually. I have a Valve Index. The only headsets with Linux support are the one I have, the HTC Vive and standalone headsets that work with ALVR (e.g. the Quest ones).

          • okamiueru@lemmy.worldEnglish
            0·
            2 days ago

            Anything special you needed to do? I have the HTC Vive, and I’ve tried a few times over the years, without any success. Last time was about 2-3 years ago.

            • Fisch@discuss.tchncs.deEnglish
              0·
              1 day ago

              It should just work. You install SteamVR through Steam, start it and it should detect the headset.

              Here are a few ideas on what could have gone wrong:

              • Steam is installed as a flatpak
                • Doesn’t work out of the box but I think it’s also in this thread where I asked how to make that work
              • You use GNOME
                • Currently, VR works on KDE in X11 and Wayland but in GNOME only in X11. GNOME 47 (The next update, some people might already have it depending on the distro) adds support for VR in Wayland tho

              These are the 2 things I could think of off the the top of my head. If you know what exactly didn’t work I might be able to help you.

              Edit: Forgot to add, you also need to install CoreCTRL and use it to set the GPU to high, otherwise performance is gonna be shit.

            • Fisch@discuss.tchncs.deEnglish
              0·
              1 day ago

              There’s a weird issue with VR on Linux where it doesn’t use the right GPU profile for some reason. A pretty easy workaround for that is to use CoreCTRL to manually set the GPU profile to high.

    • hellofriend@lemmy.worldOPEnglish
      0·
      3 days ago

      That’s what I’ve resorted to but it’s not working as well as the apt package. Freezes often, cloud sync breaks repeatedly.