Troubleshooting
First off, please make sure to carefully read installation instructions.
I'm having trouble starting ALVR.
ALVR starts fine, but says X error.
ALVR starts fine and doesn't show any error, but it doesn't see (or connect to) my headset.
If you need more help, come to our Discord and ask in the #help channel. When asking for help, please describe the issue, if you're getting an error message, copy it, and tell us what you already tried to fix it.
ALVR Launcher.exe needs Chrome, Chromium or Edge to be installed in order to work. Chrome is preferred because Edge can cause problems after updating ALVR. If you're using Windows 10, make sure your Windows is up to date. Windows 10 version 1803 should have Edge preinstalled. Otherwise you will need to install either Chrome or Chromium yourself.
This section has some advice for when ALVR shows an error (or sometimes warning) pop-up. This could be either a yellow pop-up in the setup window (ALVR Launcher.exe) or a separate pop-up when you connect with a headset.
If you get a warning pop-up inside the ALVR Launcher.exe window saying clientFoundInvalid, make sure the version of ALVR you installed on your headset is compatible with the version you're trying to run on your PC.
The latest release can be found here and contains both the alvr_client.apk file for your headset and the alvr_server_windows.zip archive with the application for your PC.
The version of ALVR available on the SideQuest store is compatible with the latest release on GitHub (the previous link). Keep in mind that the version on SideQuest might us a while to update after a new version is released on GitHub.
ALVR currently needs a recent AMD or Nvidia GPU to run, since it utilizes hardware video encoding (see requirements). If you get an error saying something like
Failed to initialize CEncoder. All VideoEncoder are not available. VCE: AMF Error 1. g_AMFFactory.Init(), NVENC: NvEnc NvEncoderD3D11 failed. Code=1 NvEncoder::LoadNvEncApi : NVENC library file is not found. Please ensure NV driver is installed at c:\src\alvr\alvr_server\nvencoder.cpp:70
and you have up-to-date GPU drivers, then your graphics card isn't supported. If you're using a laptop with a powerful enough discrete GPU, you might be able to get ALVR to work by forcing SteamVR to use it in either Windows settings, or the Nvidia control panel.
If you have a compatible GPU, you're most likely seeing a different error after either VCE: or NVENC: than above. In that case, try using a different video codec in ALVR settings. You can also try lowering your video resolution setting.
This error can show up when connecting your headset, when SteamVR gets started. Make sure the audio device you have selected in ALVR settings isn't disabled, it should be the device you usually use for games (speakers/headphones). ALVR does not create its own audio device.
You can see if you have an "enable audio enhancements" option on your sound device in Windows settings and if so, make sure it's disabled.
Here is some advice for issues that can come up even though you don't see any error popup from ALVR.
This issue can have multiple causes. It is likely that the issue is with the PC ALVR application. See below for more specific issues.
Check that the PC app and the headset app run on the latest version of ALVR. At the time of writing, the latest version is v14.1.0. If your version is v2.3.1 or v2.4.0-alpha5 then you downloaded ALVR from the wrong link. The correct link is https://github.com/alvr-org/ALVR.
Make sure ALVR is running both on the PC and on the headset. To be visible in the client list, ALVR on the headset sends broadcast packets which the PC application listens for. These can be blocked by your firewall or possibly your router, if both headset and PC are connected wirelessly, having AP isolation enabled on the router will cause this.
To fix this, you can try the following:
- Ping the headset to check it's reachable from the PC - you can do this by opening CMD and typing
ping <headset IP>without "<>" (you can find the headset's IP in the top left corner of SideQuest) - if ping fails, check that both PC and headset are connected to the same network - You can also try disabling your firewall for testing, but you shouldn't leave it disabled to use ALVR
This message means that the ALVR SteamVR driver isn't loading properly when SteamVR starts. Check that SteamVR isn't blocking ALVR (see SteamVR settings, enable advanced settings and check Startup / Shutdown -> Manage Add-ons).
If you're still getting this message (or otherwise not getting a headset icon in the SteamVR window), a SteamVR log (vrserver.txt) will have some information on why the driver isn't loading. You can find it where you installed Steam, in Steam\logs\vrserver.txt.
Unable to load driver alvr_server because of error VRInitError_Init_FileNotFound(103). Skipping. - This usually means a library that ALVR needs is missing. Make sure you followed installation instructions carefully, installed the latest Visual C++ Redistributable x64 package and no files are missing where you extracted ALVR (especially in the bin\win64 directory).
Skipping duplicate external driver alvr_server - This line means another ALVR driver is registered. Go to the installation tab in ALVR and remove all drivers.
Skipping external driver X:\path\to\your\alvr_server_windows because it is not a directory - This can happen if you put ALVR in a OneDrive (or a similar service) directory or the path to ALVR contains characters not in UTF-8. Try putting ALVR elsewhere, preferably so that the path to ALVR contains only ASCII characters.
If you have trouble looking through the logs, none of the tips work, or don't apply to you, feel free to ask on our Discord in the #help channel (you may be asked to post the log there).
This is a situation where you have ALVR open on both headset and PC, you can see the headset in the client list and trust it. ALVR then starts SteamVR automatically when you try connecting and SteamVR shows an icon for the headset (and controllers).
First make sure that SteamVR (more specifically, vrserver.exe) is allowed incoming connections (UDP, port 9944) in your firewall. You can also try disabling your firewall for testing, but you keep it disabled to use ALVR.
You can try restarting ALVR on both the headset and the PC. On the headset, when connecting, you should see the view lagging behind when you turn your head (it drops below 1 fps), this means the headset is getting a response from the server when connecting and is waiting for the video stream to start. If you get no lag in the headset, response from the PC isn't reaching the headset.