Resolved OpenXR, Oculus Quest 2 In Editor Play Mode, Only Works With Direct3d11 API, Vulkan Crashes

Hey there,

I've gotten the Oculus Quest 2 working with Unity 2021.1.15f1 by these steps:

1) Windows - > Package Manager - > OpenXR Plugin
2) Windows - > Package Manager - > OculusXR Plugin
3) Edit - > Project Settings -> XR Plugin Management - > Install XR Plugin Management
4) XR Plug-in Management - > select 'OpenXR' in windows and android tabs.
5) Under XR Plug-in Management 'OpenXR' Project Settings entry appears.
Interaction Profiles - > Select 'Oculus Touch Controller Profile'
Play Mode OpenXR Runtime - > Select 'Oculus' (this gets it working in play mode in the editor, and you have to keep selecting this every time you re-open your project)
6. You also have to do Project Settings - > Package Manager - > Enable Pre-release Packages.
7) Package Manager - > XR Interaction Toolkit, install this.
8) Right click and add an XRRig (device based) game object to the scene.
9) Make sure Oculus Quest 2 is set to Developer Mode.
10) You also need to do: Window - > Analysis - > Input Debugger. In the Input Debugger window you need to select 'Lock Input To Game View' in order for headsets to work in editor play mode as well.

Now here's where things get tricky.

Under Project Settings - > Player....You have to have both 'Direct3D11' and 'Linear' color spaces to use the Oculus/OpenXR in edit mode.

However, the Oculus Quest 2 when building to Android needs 'Gamma' and 'OpenGLES 3.0'.

This is creating a real problem, because now I need to build the game in Android, Gamma, and OpenGLES 3.0. Switching to Gamma and switching to OpenGLES 3.0 requires a huuuge re-import.

Is there a way I can just get the testing in editor play mode working using Gamma and OpenGLES instead? It just won't work unless I select specifically Linear color space and Direct3D11 under API.

 

Alright, I'll have to submit a bug report.

Vulkan also freezes as well. Still running a handful of tests.

 

Alright, it's a new project.

I'll maybe create an unlisted youtube video as well to post here.

Is there a way I can get the crash report myself to check the code? Is it the code in the 'OpenXR Plugin' or the 'XR Plugin Management' folders under Packages?

EDIT: Sorry for this, but I don't know how to properly report an issue, does that pop up when it crashes?

 

Okay, upon further testing, Gamma color space is working, but the Vulkan API is not working with Oculus Quest 2. Right now the Unity Bug Reporter is packing the report.

I'm going to test other graphics APIs and get back to you on which ones work and which don't. I know that Direct3D11 does work with the Oculus Quest 2, but again this isn't supported by Android.

 

Here's the video and I've reported the bug as well but don't know how to give you the number.

The problem is that Vulkan crashes when PlayMode OpenXR Runtime is set to - > Oculus and using the Oculus Quest 2 with the Oculus Link.

OpenGLES 3.0 won't work also with Gamma, so that means the only Graphics API that working with the Oculus Quest 2 right now is Direct3D11 which won't work with Android builds.

Here's a Youtube showing as clearly as possible what's happening:

(This is a 2 minute video explaining the problem as clearly as I can)

Here is the project:
https://drive.google.com/file/d/1VVpvB779G9lG8tIX0r6ml0-rmUgQpSdf/view?usp=sharing


Here are my basic system specs:
Windows 64-bit, Windows 10 Home
Intel Core i5-9400 at 2.9Ghz
16GB of Ram
Using NVIDIA GeForce GTX 1660

I've titled this 'only working with linear color space' but the title should be renamed to 'only working with Direct3D11 API.

 

OKAY HUGE UPDATES!

I've learned a TON of things in the last 5 days of trying to port to the Oculus Quest 2 natively.

Using the following settings I was able to solve the problem, and test in editor with the Oculus Quest 2 headset AND build to the platform.

The trick was to not select 'OpenXR' under XR Plug-in management, and to switch to Android build platform in the Unity Editor.

Enabling the incremental garbage collector for some reason was required for me to stop it from locking up when I tested in editor play mode.

I'm not entirely sure how SteamVR will work now since I can't build an EXE, have XR Plug-in Management with 'OpenXR' selected, it NEEDS to be Oculus for PC builds too....but, my thought is that Steam Works just has branches or some way you upload different separate EXE files per the headset you're targeting.

P.S - I haven't tried Vulkan, but OpenGLES 3.0 is working.

 

For some reason it works when you hit 'build and run' for pc, but even if I try to boot up the runtime manually, when you select OpenXR and build to a windows executable and run it, it won't launch the game even if you're using Steam VR.

Steam VR only works for Oculus Quest 2 at my end if you selected Oculus as your PC runtime.

 

I need to do more testing. So far SteamVR recognizes the headset standalone only when I build it for PC - > Oculus.

For anyone else reading this, when you've got your Oculus Quest 2 hooked up, you need to switch to PC - > OpenXR and select Oculus Headset for playtesting with with the Oculus controllers profile....But THEN you can switch to Android or whatever you'd like and it'll work properly. It's very strange.

 

Not the play mode runtime, but the Plug-in Providers.

 

OpenXR is a utter mess...does anyone have any insights as to when we will be able to use and not spend weeks messing about with it like @astracat111? I am really disappointed in Unity and Oculus for this rather poor rollout of OpenXR. What a sh@t show.

 

@the_real_apoxol It states I need Unity 2019 or new to use OpenXR with Unity yet I am on 2021.1.15f1. Plus it does not support FFR yet which is pretty key feature for most titles. I already submitted a bug a few days ago and am waiting to hear back.

 

@the_real_apoxol Any update on this ?
Is FFR now supported in OpenXR ?

 

late but just to let you know, activating spacewarp + vulkan makes oculus XR to not work on editor while OpenXR works

 

Thanks! I just wasted a whole day to realize this was my issue (using Legacy XR + 2021.3.x).

I need to start doing a full test every time I toggle any single check-boxes in Unity when working in VR.

 

Thank you so much. The spacewarp setting checked is what caused my playmode to get stuck on unity loading in the headset.

 

yeah, happened to me. Unity hasn't released the fix yet...

 

Thank you, the developer mode was switched off and I was working on Pass-through feature which requires developer mode on. Thanks again!