Search Issue Tracker
Third Party Issue
Votes
1
Found in [Package]
1.9.1
Issue ID
OXRB-281
Regression
No
[Quest][OpenXR] Vulkan application stuck on loading when launching on Meta Quest 2/3 headset with Development build enabled
Steps to reproduce:
1. Open the attached user's project "SimpleAPKTest.zip"
2. Switch to Android platform
3. Make sure Development build and Vulkan Graphics API are enabled/selected
4. Make sure OpenXR is selected
5. Connect Quest 2/3
6. Build for Android
Expected Result: The application starts
Actual Result: The application either crashes or is stuck on loading
Reproducible with these devices:
VLNQA00609 - Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno 740, OS: 12
VLNQA00415 - Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 12
Reproducible with: OpenXR 1.9.1 (2022.3.16f1, 2023.2.4f1, 2023.3.0b1)
Not reproducible with OpenXR 1.9.1 (2021.3.33f1)
Testing Environment: Windows 11
Not reproducible on: No other environment tested
Notes:
-User reported that the application crashes, however I could not reproduce the crash
-Issue does not reproduce with OculusXR plugin
-Issue does not reproduce with a release build
-Quest 3 is running v60.0, and Quest 2 v59.0
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
- WebGL Player with WebGPU Graphics API fails to render Scene when custom Render Feature is used
- “EndLayoutGroup” error thrown when changing Shader Precision Model settings in Build Profiles window > Player Settings Overrides
- Button hover state uses default theme color when a custom .uss is applied
- Samples Showcase script warning does not clear after enabling required settings until GameObject is reselected
- VFX Particles receive shadow artifacts when using ShaderGraph with enabled shadows and Face Camera Plane Orient mode
Resolution Note:
We've heard back and the underlying issue is caused by Meta's handling of xrCreateVulkanInstance where they accidentally request duplicate extensions. There's no known workaround until their fix lands, which will be in their v64 software update at the end of March.