Search Issue Tracker
Fixed in 1.3.0
Votes
0
Found in [Package]
1.2.8
Issue ID
1370424
Regression
Yes
[OpenXR][Oculus] Quest 2 black screen with Vulkan enabled after OS version update 33.0.0 with OpenXR
Reproduction steps:
1. In your Oculus Quest 2 go to "Settings > About" and make sure your OS version is 33.0.0. If not, click update and wait for the update to be installed
2. Open the attached user's project "Oculus23.zip"
3. Make sure that Vulkan is selected as the Graphics API along with IL2CPP
4. Build for Oculus Quest 2
5. Observe that nothing is being rendered
6. Look at the ADB log for the "xrGetVulkanGraphicsDevice2KHR: vulkan instance does not match" error
Expected result: the APP is launched properly on Quest 2 with Vulkan enabled after OS version update 33.0.0 with OpenXR
Actual result: Quest 2 black screen with Vulkan enabled after OS version update 33.0.0 with OpenXR
Reproduces on: Open XR 1.2.8 (2021.1.11f1, 2021.1.27f1, 2021.2.0b16, 2022.1.0a14)
Not reproducible: Open XR 1.2.8 (2020.3.21f1, 2021.1.10f1)
Could not test on 2019.4.32f1 (no OpenXR package)
Android Logcat:
W/OpenXR: xrGetVulkanGraphicsDevice2KHR: vulkan instance does not match
I/VulkanLoader: ovrVulkanLoader::Load
W/VulkanLoader: ovrVulkanLoader::LoadDeviceFunctions: device invalid
W/VulkanLoader: ovrVulkanLoader::LoadExtensionList: physicalDevice invalid
Notes:
-Issue does not reproduce with Oculus Plugin
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 1.3.0):
This issue is fixed in the upcoming 1.3.0 release of the OpenXR package.