Just echo'ing the other comment.
I'm on arch, and with nearly no tinkering my index just works.
Only low level knowledge I think would be useful is the different VR runtimes. SteamVR vs Monado
Just echo'ing the other comment.
I'm on arch, and with nearly no tinkering my index just works.
Only low level knowledge I think would be useful is the different VR runtimes. SteamVR vs Monado
Can you elaborate on what your setup is? I have tinkered plenty and there are multiple issues I'm still dealing with on my Arch machine, despite being on a setup that Valve claims is supported (KDE Wayland, Nvidia), namely:
- SteamVR won't see my Index unless I power cycle it
- The in-overlay desktop view does not work at all, either shows all black or doesn't render at all, so I can't control my desktop from VR which is a massive pain
- The SteamVR Home environment (the startup app) crashes immediately even if launched manually
Not the same person, but in case it helps, monitor dbus for denied flatpak permissions and use flatseal to grant them? (Could try allowing everything in flatseal just to rule it out)
I don't use arch btw, but on fedora i have often found setroubleshoot useful for non-flatpak apps
I'm sorry you're missing out on Alyx - it's not the greatest game ever made, but it's up there.
Fortunately I've already played through Alyx a few years back (and it really is an amazing experience). These are issues I'm having since moving my rig away from Windows a few months ago. Even then, games are still playable on this setup, but the points above add a lot of friction that I'd really like to get rid of.
I'm using Arch-packaged Steam, so it's not running in flatpak. I suspect both the headset not detected and desktop view being unavailable issues are Wayland-related, but the Steam Frame itself is running Arch+KDE, and KDE is dropping X11 very soon, so I'm confused that this setup is not functional even in the latest version of SteamVR - it should be what the Frame is running, modulo the CPU architecture.