Hey Gamers! I have a friend who needs a hand, their message is quoted below without edits. They’re on Garuda Dragonized Gaming Edition. I don’t have any other details, but let me know if I need to ask them anything.
“Sure. I think the issue is I’m running a Quest 3, and I can’t hard-wire it, my desktop has no USB C, so I need to go over wifi. I tried ALVR, and nothing would talk to eachother, which was never an issue before. The headset wouldn’t talk to ALVR, and ALVR wouldn’t talk to SteamVR. ChatGPT told me to install and manually set the path to OpenXR and that did nothing. I never had an issue with my headset talking to windows, so I don’t think it’s my network, I dunno”
Hey Lynn!
I’m in a similar situation but I’ve been able to play VR games through ALVR and the Quest 2 without an issue.
For starters, your friend doesn’t need a specific USB C cable, he could use a USB C connected to the Quest 3 and a USB A 3.0 connected to the PC.
I take it that he installed ALVR through the AUR, being Garuda an Arch-Linux (I use Arch BTW) distro. I had several issues with that version and I fixed every issue using the alvr_streamer_linux.tar.gz download in the release page, see here for instructions.
Things that should be taken in consideration:
- both the ALVR client (installed on the Quest) and the ALVR server (running on the PC) should be the same version number
- the latest SteamVR patch breaks ALVR, hence it’s mandatory to select “previous_version” through the Beta configuration of SteamVR (see here
I have a follow up from them this morning.
“Hey, sorry to bother, but I’ve hit another roadblock… When connecting, ALVR spits out "Handshake error: Cannot find a device which name contains “pipewire”. When googling, it seems most don’t have this issue, their is more… Audio coming from computer speakers/headphones instead of the headset and stuff. I checked Helvum cus I read you can route audio manually, but Pipewire isn’t even there. I have installed and enabled Pipewire, and did the installation thing that pops up when first starting ALVR, including downloading and setting the “on connect/on disconnect” script”
