Troubleshooting - GPUOpen-LibrariesAndSDKs/Radeon-ReLive-VR GitHub Wiki

Troubleshooting

For all problems first make sure that you are running the latest Adrenalin driver and the latest ReLive VR client app.

Please attach the AMDWirelessVR.log file found in Steam's log directory (typically under %ProgramFiles(x86)%\Steam\logs) to all bug reports.

Video-related Issues

Headset cannot find the PC and continuously displays the WiFi animation

  1. Check if the ReLive VR OpenVR driver is registered with Steam. Take a note of the headset icon in SteamVR - it should be displaying the WiFi symbol when ReLive VR driver is active.
  2. Check if Windows Firewall allows traffic to vrserver.exe for the network type (Public, Private or Domain) of your network connection. You can quickly isolate this scenario by temporarily disabling Windows firewall - if you can establish connection with the firewall disabled, the problem is with the firewall configuration. Make sure to allow traffic to vrserver.exe for the appropriate network type.
  3. Check if the headset and the PC are placed on the same IP subnet by the DHCP server. Do not assume that the wired and the wireless networks are assigned to the same IP subnet because they're connected to the same router - while this is usually the case, there are some devices that are exceptions to the rule. If they're not on the same subnet, follow the recommendations on the Advanced Network Setup page. Use the ipconfig /all command on Windows to display your current network settings on the PC. It might be more difficult to find the IP address of the headset since the UI is different on different headsets, but you can always use a mobile phone or a PC with a WiFi adapter to connect to the same WiFi SSID as the headset and check the IP address there. On most Android phones you can find the IP address of the phone under System/Status in Android Settings.
  4. Check if your PC is configured to accept connections from paired devices only and ensure that the headset you are using is paired with the PC.

Headset connects, but the image is corrupted

  1. Make sure your headset is connected to the 5GHz AP and not the 2.4GHz one
  2. Reboot your router
  3. Follow suggestions on the Advanced Network Setup page.

Occasional periodic image corruption/freezes, audio stutter

  1. Reboot the headset and router
  2. Try reducing video bitrate to 50Mbps or lower.
  3. Check network and CPU activity on the PC (Windows downloading updates, Windows Defender running a background scan, etc).

Image lags behind head movements

  1. Try rebooting the headset, the PC and the router
  2. Check network traffic in the Performance tab of Windows Task Manager for high network utilization by other software while not streaming to the headset (Windows Update is often the culprit). You should see next to zero traffic. If you see high network utilization, try to identify which software component is causing it. Waiting for it to complete would resolve the issue.
  3. While in Windows Task Manager, check for high utilization of other resources, such as CPU, memory and disk
  4. If you are streaming over TCP, try switching to UDP.
  5. Follow suggestions on the Advanced Network Setup page.

Headset connects, but shows very high packet loss/corrupted image/no image in the headset, but PC is showing normal headset tracking

It is possible that your router drops large UDP datagrams. If this is the case, you would see a large number of log entries like the one below in the c:\Program Files (x86)\Steam\logs\AMDWirelessVR.log:

[FlowCtrlProtocol] Info: Message send from gap. oldID=4 newID=6

Try the following steps:

  • open the c:\Users\AppData\Local\AMD\OpenVR\settings\settings.json file in a text editor like Notepad. If you don't see the AppData folder, click on the View tab in Windows Explorerand check the Hidden items checkbox.
  • Scroll down towards the end of the file and there you will see a section called "Headset". It will look like this: "Headset" : { "DatagramSize" : 65507, "LogPath" : null, "MaxUserCount" : 1, "Network" : "UDP", "Port" : 1235 }
  • Try reducing the DatagramSize value to some smaller number. Try to find the largest that works well with your router. Usually 1472 is a "magic" size that works, but better performance can be achieved with higher numbers like 8192. If it starts working, try doubling it. If it still works, double it again. Once it stops working, try a value in the middle between the last value that worked and the last value that didn't. 65507 is the absolute maximum supported.

Image judder during linear (side-to-side, up-down and forward-backwards) movements only

It's not a bug, it's a feature :) This is an unfortunate artifact of streaming over the network with varying latency that cannot be compensated on the headset. On the bright side, unlike with rotational motion, linear motion judder does not cause nausea.

Audio-related Issues

No sound from the headset

  1. Check that there is an output audio device such as speakers, headphones or HDMI audio is present in the system
  2. Check if the default output audio device is actually connected and active. ReLive VR might not be able to capture audio from an inactive default audio device. If your PC does not have the default audio output device, you can use any of the virtual audio cable type applications that would add a virtual audio output that ReLive VR could capture the sound from.
  3. Check if other OpenVR streaming solutions are registered with SteamVR at the same time. To do so, check the external_drivers array in the %LOCALAPPDATA%\openvr\openvrpaths.vrpath file - you can open this file using any text editor, such as Notepad. If other OpenVR drivers capture audio in exclusive mode even when they are not in use, ReLive VR would not be able to capture desktop audio. Remove the offending driver from the list, save the file and restart SteamVR. Report the problem to the driver's vendor.
  4. Make sure that the default output audio device is configured as Stereo (not as 5.1, 7.1, etc).
  5. Try disabling audio enhancement/virtual surround software, which often comes pre-installed on gaming laptops and brand-name desktop PCs.

Audio lags behind video

Some audio delay is normal and unfortunately unavoidable. Ensure that you are using the latest Adrenalin driver and the latest ReLive VR client software as several older versions had various bugs that lead to audio delay increasing over time. To the best of our knowledge, these issues have been addressed in the latest versions.

Controller-related Issues

Video and audio streaming is working well, but hand controllers do not appear

Check the Use Third-Party Controller setting in the General tab of Radeon Settings. Set it to Disabled and restart SteamVR. Enable the third-party controller only when you're using controllers like XBox controllers that tend to constantly switch between hand controllers and gamepad-style controllers during gameplay. In most cases this setting should be left at Disabled.

Title-specific Issues

Image in the headset is too dark in some titles

Try enabling special treatment of 10-bit sRGB by setting the 10BitSRGB parameter to true in the settings.json file. This problem is caused by the incorrect handling of the 10-bit sRGB gamut in some game titles. Because this problem is title-specific, you might have to change this setting when playing specific titles only.

Certain games (Eagle Flight, Subnautica) fail to start in ReLive VR

Perform room setup for standing experience.

Miscellaneous Issues

SteamVR fails to start on multi-GPU systems when ReLive VR is enabled

Ensure that your ReLive VR-compatible AMD discrete graphics card is set to be the default graphics adapter (primary monitor is connected to the AMD discrete GPU)