-
-
Notifications
You must be signed in to change notification settings - Fork 498
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ALVR addon doesn't appear on Steamvr #2112
Comments
I might have had a similar problem with the new SteamVR update, something happened that caused SteamVR to send |
That works. Should I keep this issue open until a permanent fix is found? |
I guess so, as it's a problem on the main SteamVR branch |
Welp. Now even the 'previous' beta branch (2.4.4) of SteamVR doesn't work for me. |
Yep, been seeing this since yesterday evening when I tried to use ALVR. Not sure what's changed though. |
I ran it just now, it still works for me, version 2.4.4 |
Well I'm on 20.8.1 so unless I go to nightly releases (which seem to not always be nightly) there's nothing for me to upgrade to. It's not blocked. It worked on Sunday and Monday, then stopped working on Tuesday. No changes made here. |
strange, I'm using the Nvidia fork on Linux if that adds any context |
Well, no idea what's wrong with it. Completely uninstalled & reinstalled Steam then SteamVR, ran SteamVR and closed it. Ran ALVR and it's still not showing the alvr_server add-on in SteamVR settings and it just tells me to plug my headset in now. Even tried the latest nightly. |
OK, I have finally got ALVR working (at least back into the SteamVR home screen) by following the instructions at https://github.com/Scrumplex/Steam-Play-None. Note however that that Proton-Up-Qt did not work in x11 as it complained about no QT environment. Fortunately Linux Mint recently added experimental Wayland support so once I logged back in on that I could run it, then log back into x11 and follow the rest of the instructions. |
Had problems yesterday running the ALVR server, fixed by statically linking x264 in source build, and later black screens on SteamVR 2.4.4, also fixed by using https://github.com/Scrumplex/Steam-Play-None. The SteamVR container runtime issues may also be related to the x264 linking issue mentioned on #2130, so maybe the same fix would fix the server startup issue, but I haven't tried that specifically. |
Thanks! Now ALVR 20.8.1 works with SteamVR 2.4.4 for me. |
I'm guessing this might be related to the SteamVR update, and it's recommended to follow #2115 to configure it to verify that it's available. |
SteamVR just updated to 2.6. Now workaround with setting previous version does not work, as previous version is now 2.5. |
There's a better workaround, see the linux troubleshooting page of the wiki |
Closing as duplicate of other issues |
Description
I had a problem launching Steamvr, and had to reinstall Steam to get it to work. Then when I launched ALVR, the plugin no longer appeared. I tried reinstalling steamvr, and ALVR to no avail. I registered the plugin, at /usr/lib/steamvr/alvr so idk what's wrong
General Troubleshooting
Environment
Hardware
Note: for Linux, an upload to the
hw-probe
database is preferred:hw-probe -all -upload
CPU:
Ryzen 5 5600x
GPU:
Nvidia RTX 3070ti
GPU Driver Version:
nvidia-550
Audio:
Pulse Audio, Pipewire
Installation
ALVR Version:
alvr-nvidia 20.7.1-1
ALVR Settings File:
SteamVR Version:
2.5.4
Install Type:
exe
,deb
,rpm
, etc)zip
)OS Name and Version (
winver
on Windows orgrep PRETTY_NAME /etc/os-release
on most Linux distributions):EndeavourOS 24.5.8-1 with Plasmashell 6.0.4
The text was updated successfully, but these errors were encountered: