Search Issue Tracker
Third Party Issue
Votes
8
Found in
2022.3.0f1
2023.3.0a17
Issue ID
UUM-55686
Regression
No
[Quest] - Vulkan Development Build crashes on load
Building the samples and another project with an AR Session and other meta-openxr ARF features, when building and running to the headset on quest 3 the app crashes.
This ONLY repros on:
- Quest devices
- Vulkan Graphics API
* GLES did NOT repro
Environment Details*
Quest 3 OS: v57
Unity Editor: 2023.2.0b2
Graphics API: Vulkan
I attempted to repro this on another project without Meta-openXR and it did not crash.
Repro Steps:
1) Open meta-openxr ARF Samples Project
2) Open Project Settings
3) Select Development Build
4) Build and Run to Quest 3 HMD
5) Observe
Observed Results
- HMD loads for a moment before returning to the main "home"
expected Results
Project launches in HMD
Comments (6)
-
automaton82
Mar 30, 2024 19:35
March 30, still experiencing on Quest 3.
-
jcplusplus
Jan 30, 2024 18:59
This issue will be fixed in Meta's next OS release, v64, which should be available at the end of March.
-
Hbk29
Jan 09, 2024 02:08
The same problem occurs with MetaQuest2 and PICO4 in Unity 2022.3.16f1.
-
wilcoboode
Dec 11, 2023 09:40
We are using unity 2022.3.12f1, OpenXR 1.9.1 and Unity OpenXR Meta 1.0.1, and we get the same issue. Device invalid, and a direct crash on Quest 3 when using Vulkan.
-
jbhewitt
Nov 22, 2023 21:28
Same issue with Unity 2022.3.13f1
-
TheVirtualMunk
Nov 08, 2023 08:34
For us using release builds doesn't solve it. Unity 2022.3.12f1 - non-OVR project (pure Unity Meta OpenXR and XR Hands)
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:
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.