-
-
Notifications
You must be signed in to change notification settings - Fork 7
Known Issues
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 may lead Oasis to crash repeatedly after a few seconds! This issue may also happen if some corruption happens during the initial set-up process.
There is a very easy remedy: This can be solved by clearing the environment data then re-running the Room Setup.
The unlock procedure hangs forever after the message "Display EDID" or by repeating "Device does not need manual activation of the display". There is no known solution at this time, however for several users, this issue was simply caused by a defective cable or headset (and it unclear whether that was the problem for all users).
Unsure what is causing this for some people.
Close SteamVR entirely, then editing file C:\Program Files (x86)\Steam\config\steamvr.vrsettings.
Look for a line "preferredRefreshRate" : 60,, and delete this line.
Some applications (primarily OpenXR) get stuck at the loading screen, but show up on the monitor [FIX STAGED FOR RELEASE]
This seems to happen if the proximity sensor (presence detection) on your headset is defective or flaky.
In SteamVR Settings, Video, toggle OFF the setting "Pause VR when headset is idle".
Oasis does not support the built-in Bluetooth interface that was included with the Samsung Odyssey+, HP Reverb G1 and G2. Instead, Oasis will require that you use Windows Bluetooth in order to pair your motion controllers.
- if your computer already has built-in Bluetooth, you are fine.
- if you already have an add-on PCI Express or USB Bluetooth interface, you are fine.
If you have neither of the above, you can purchase a cheap USB Bluetooth dongle like this one ($10 in the US): https://a.co/d/5haSNGn
If you don't plan on using your motion controllers, you are also fine, Oasis will work without motion controllers.
The original Mixed Reality Portal had what we call an "OOBE" (pronounced "ooo-bee"), or Out-Of-Box Experience. That was the phase during which you had to follow the tutorial, look around and aim at things. This phase was actually important to give a chance to the Mixed Reality driver to learn about your room as you followed the steps.
With SteamVR there is no such thing. When you first run the Oasis driver, it is highly encouraged that you take a moment look around the room to give a chance to the driver to learn about the room, and only then (after a minute or so of looking around), you shall proceed with the SteamVR "Room Setup", where you can calibrate your starting position, height, and create room boundaries.
This is a serious issue, which has been reported by about 2% of the users so far. The distortion does not appear correct, causing a convergence issue for the user (and some discomfort). There is no fix at this time.
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..
This affects only some HP Reverb G2 units. The factory calibrations trigger a bug that causes visible artifact on the screen. This issue can be worked around by toggling SteamVR Settings -> Windows Mixed Reality -> Use Hidden Area Mesh -> Off. You will need to toggle "Show advanced settings" in SteamVR.
This affects only late HP Reverb G2 v2 units. The passthrough cameras are incorrectly being displayed side-ways (rotated by 90 degrees). There is no fix at this time, but it will be addressed in a later version.
This affects only HP Reverb G2 Motion Controllers (the ones with the ABXY buttons). In the dashboard, the joystick cannot be used to scroll left and right. This issue already existed in the original Windows Mixed Reality for SteamVR driver. You can use the Trigger to "grab" and scroll left and right.
This affects only HP Reverb G2 Omnicept. The HP eye tracking calibration application does not enter VR properly, making it impossible to complete the eye tracking calibration procedure. Eye tracking is still functional in uncalibrated mode. There is no fix at this time, but it will be addressed in a later version.
There is a documented workaround here: https://github.com/mbucchia/Oasis-Driver-for-Windows-Mixed-Reality/issues/7#issuecomment-3238724329.