Resolved VR Oculus not working since 2020.1 (since release)

Since migrating to 2020.1, where the Oculus integration is deprecated, we switched to XR Plugin Managment package. Here the screen mirroring does not work, stereo rendering does not work (only renders UI for example to one eye).

This is in a clean HDRP project, created from the Hub.

I think it is very strange that this has not been fixed since the release of 2020.1, it is easy to re-produce - I assume that the XR test team has tried creating a clean project from the Unity hub and testet it.

Please help - we are using in a professional capacity, and it is hard to go months with a critical issue like this.

The issue is in 2020.1 (all version up to 2020.1.0f6, 2020.2 (all versions up to 2020.2.0b2), HDRP 9.0.0, HDRP 10.0.0, XR Plugin Management all versions since 2020.1

 

To re-produce issue (in Unity 2020.1.6f1 (HDRP 9.0.0) or Unity 2020.2.0b2 (HDRP 10.0.0) // Oculus Rift S // Windows 10 x64 w/latest updates) // Oculus XR Plugin 1.4.3:

• Create new HDRP project from Unity Hub
• Install HDRP 9.0.0 (2020.16f1) or 10.0.0 i(2020.0b2) from package manager
• Add XR Plugin Management fro package manager (3.2.15)
• Setup XR in project settings for Oculus, Single-pass instanced.
• In example scene add Tracked Pose driver to camera (and enable XR rendering in Output)
• Add a UI element to scene
• Hit Play, observe that UI is only drawn in one eye
• Also: make a build - see that screen mirroring does not work, and UI is only drawn in one eye

 

Works in built in renderpipeline but not HDRP

 

did you report this as a bug?

 

Yes

 

I've also reported the bug with screen mirroring not working in HDRP (several weeks ago) -- even more it prevents the static scene view mirroring variable from even being able to change from "None"

 

Yes, kind of strange that this bug has been there so long - when it occurs in clean HDRP project...

 

Hey there, can you let us know of your case number so the team can look into this for you?

Thank you!

 

Case #: 1279033

 

Thank you! We're aware of them (Case #1279469 and Case #1279033) and the team will investigate.