Do you have both the Mic and audio enabled? If so turn off one of them, it's currently a bug and it will be fixed eventually. You can also go back to an older version that doesn't have the bug https://github.com/alvr-org/ALVR/releases/tag/v20.11.1
#i need help
17 messages · Page 1 of 1 (latest)
@buoyant portal do you know if this is already fixed in nightly builds?
i have the same problem, i go around it by closing ALVR client on PC as soon as the headset connects, then i just open it again and it wont disconnect
if you are fast enough, you can open your desktop through steamvr and close alvr client. if youre not fast enough, the connection resets
or just use your mouse to close the client when the headset connects, easier than speedrunning alvr client shutdown any%
I haven't found anything that changed that would fix it but I've used a Quest 2 just fine on the nighties with both audio and mic enabled
the original problem here is the kind of thing a reboot fixes
the first time connection of headset after you update version can be janky, my first attempt usually ends up like the OP describes - then i restart everything and its fine
other scenarios that i saw similar results were when i was testing zerotier - something about that vpn can cause this
so not having a proper connection between headset and pc, only a partial one
fwiw - I have this same issue and haven't been able to resolve it since v20.12.1. Rebooting does not fix it at all.
#linux-discussion message
does latest nightly work?
Haven't tried. I'm not using the launcher because I launch it from a wrapper script to set do some other things. Might give it a go though.
v20.11.1 with the adb forwarder worked like a champ.
Holy shit, I just re-read your earlier comment and disabled my vpn (Proton) and it worked. Also still worked after re-starting the vpn. Will check if it survives a reboot later!
If you still want to use the VPN while using VR check if you have a "allow local traffic" option in your VPN's settings.