-
-
Notifications
You must be signed in to change notification settings - Fork 7
Known Issues
Problem
SteamVR starts up and is usable for a few seconds, including display in the headset and tracking, but consistently crashes.
If your machine was upgraded from a version of Windows with the Mixed Reality Portal, there is a high chance that some stale data is present or corrupted. This issue may also happen if some corruption happens during the initial set-up process.
Workaround
This can be solved by clearing the environment data, in particular solution 2 where you delete the WindowsHolographicDevices folders manually, then re-run the Room Setup.
Solution
No further work planned. Detecting the corruption does not seem possible and preemptively deleting the environment data is detrimental to quality of tracking.
AMD only updated their RDNA driver to work with Oasis. This is the driver for RX5000, RX6000, RX7000 and RX9000 series. Older cards (such as 500 series) cannot work with Oasis due to the limitation of the AMD driver.
Problem
The unlock procedure completes on my system with an AMD GPU, however SteamVR fails to start or displays a pink screen.
Solution
Some AMD drivers don't work. Try one of the verified drivers:
| Version | Works |
|---|---|
| 25.9.2 | ✅ |
| 25.10.x | ❌ |
| 25.11.1 | ✅ |
| 25.12.1 | ✅ |
| 26.1.1 | ✅ |
| 26.2.1 | ✅ |
| 26.2.2 | ✅ |
| 26.3.1 | ❌ |
| 26.5.1 | ❌ |
| 26.5.2 | ❌ |
| 26.6.1 | ❌ |
| 26.6.2 | ✅ |
| 26.7.1 | ✅ |
Problem
The unlock procedure completes on my system with an AMD GPU, however SteamVR fails to start.
Solution
The AMD driver will only enable support for Oasis on Windows 11 24H2 and above. This is because AMD does not want to break compatibility with the Mixed Reality Portal on older versions of Windows. You have no choice but to update to Windows 11 24H2 or above.
Problem
Cannot select 60Hz mode in the SteamVR Settings, only 90Hz mode is available.
Solution
None. This issue has been reported to AMD and cannot be fixed by Oasis alone.
Problem
On a minority number of units, due to specific factory calibrations, lines or triangles are visible in the middle of the display or near the edges of the display.
Workaround
This issue can be worked around by toggling SteamVR Settings -> Show advanced settings, then Windows Mixed Reality -> Use Hidden Area Mesh -> Off.
Solution
Under investigation. This issue is the result of the advanced distortion profile used on Reverb G2, where the distortion function does not diverge to infinity, but rather behave randomly outside of the distortion area. Such function is incompatible with the distortion model used by SteamVR. A workaround is already in place in the driver, reducing the likelihood of this issue, but not eliminating it.
Problem
StreamVR crashes at startup or fails to initialize the display when 60Hz mode is selected.
Workaround
Switch the refresh rate in SteamVR Settings -> General to 90Hz for SteamVR to start, then the refresh rate can be changed (without a restart) to 60Hz.
If the setting is not accessible from SteamVR Settings, try manually unsetting it: close SteamVR entirely, then edit file C:\Program Files (x86)\Steam\config\steamvr.vrsettings. Look for a line "preferredRefreshRate" : 60,, and delete this line.
Solution
None. The developer cannot reproduce the issue but hopes to be able to dedicate some time to troubleshoot it in the future.
Problem
There is a visible tear of the screen, where one part of the screen seems to "lag" behind. It is unclear if this issue is unit specific (your headset) or machine specific (GPU, driver, etc...).
Workaround
- Reverting to NVidia driver 546.65 resolves this issue.
- Alternatively, switch the refresh rate to 60Hz in SteamVR Settings -> General.
Solution
None. The developer cannot reproduce the issue but hopes to be able to dedicate some time to troubleshoot it in the future.
Problem
The unlock procedure fails to find the HDMI/DisplayPort output for the headset, and SteamVR cannot start and open the display output.
Solution
Ensure that the "high performance" graphics adapter is enabled. You may also try adding the following applications to the list of applications that prefer use of the high performance graphics adapter: Steam\steamapps\common\Oasis Driver for Windows Mixed Reality\unlock\unlock_wmr.exe, steam\steamapps\common\SteamVR\bin\win64\vrserver.exe, steam\steamapps\common\SteamVR\bin\win64\vrcompositor.exe and steam\steamapps\common\SteamVR\bin\win64\vrstartup.exe.
Unfortunately, not all topologies of hybrid GPUs are supported by SteamVR native drivers, hence it is possible that this issue is unavoidable on certain laptops.
Problem
The view in the headset is too high or too low, not matching my actual height.
Solution
Look around the room for a minute, then face the front of your playspace. Open the SteamVR Dashboard and perform a Recenter (this part is critical, as it forces the driver to acquire a valid room anchor). Now perform the Room Setup procedure. When asked to calibrate height, lay the headset flat on the floor, enter 0cm/0in height, and press Calibrate.
Problem
Initial position in the room is lost between restarts of SteamVR. Position in the room "jumps" around when looking in certain directions.
Workaround
Look around the room for a minute, then face the front of your playspace. Open the SteamVR Dashboard and perform a Recenter (this part is critical, as it forces the driver to acquire a valid room anchor). Now perform the Room Setup procedure.
Solution
Under investigation. This issue is caused by the lack of redundancy when tracking "room anchors". The developer wishes to implement a network of redundant anchors to reduce the frequency of this issue.
Problem
The view in the headset is not level (parallel to the horizon), but instead tilted left or right.
Solution
This happens sometimes at first run when the tracking doesn't do a good job at learning your room. This can be solved by clearing the environment data then re-running the Room Setup. Make sure to look around the room for a minute or two before entering the Room Setup.
Problem
The quality of the tracking of the motion controllers is poor and/or the controllers shake repeatedly.
Workaround
Ensure optimal Bluetooth quality. Use built-in Bluetooth on HP Reverb, HP Reverb G2 and Samsung Odyssey+. Use an antenna when possible. Connect your USB Bluetooth receiver to a USB 2.0 port away from any USB 3.0 port that is being used (with a USB 3.0 device actively connected). Use a higher quality/brand Bluetooth receiver.
Problem
SteamVR detects your controller, and the buttons/vibration work, however the controllers never appear.
Solution
This issue is caused by the USB connection to the headset not running at USB 3.0 speed. Check your USB port or USB hub, remove/replace any extension cable or adapters.
Problem
Controller is detected, but does not appear correctly (eg: wrong controller model in game) or cannot perform interactions with the buttons.
Workaround
Try using the emulation mode by toggling SteamVR Settings -> Show advanced settings, then Windows Mixed Reality -> Emulate Touch Controllers.
Try using community bindings through the SteamVR Settings -> Controllers control panel.
Solution
Under investigation. Some games (like Resonite) could receive better compatibility if Oasis "looked" more like the previous Windows Mixed Reality for SteamVR driver.
Problem
The HP eye tracking calibration application does not enter VR properly, making it impossible to complete the eye tracking calibration procedure.
Workaround
Eye tracking is still functional in uncalibrated mode. This is sufficient for usage like foveated rendering.
Solution
None. When time allows, the developer hopes to create a way for the calibration application to enter VR properly.