Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.15.1
Issue ID
OXRB-632
Regression
No
Black screen on startup and an endless loop of xrLocateSpace errors when "Not Specified" & "Floor" Tracking Origin is used
Steps to reproduce:
1. Create a new VR Template Project
2. Switch Platform to Android
3. In XR Management enable OpenXR and disable any XR Feature, like Meta support, etc (customer wants to use the Standard Khronos OpenXR Loader)
4. In the XR Rig change the Tracking of the Headset to Floor
5. Build APK and deploy on HMD
6. Results in a black Screen and OpenXR errors
Expected result: no black screen and no OpenXR errors
Actual result: application enters a loop asking for xrLocateSpace with an invalid handle from which it never recovers
Reproducible according to the customer: OpenXR 1.13.0 - 1.15.1 (6000.1.8f1)
Not reproducible according to the customer: OpenXR 1.12.1 (6000.1.8f1)
Could not test on all currently supported streams due to missing required hardware
Notes:
-Do note this was not reproduced by CQA due to missing Android VR hardware
-"Unity6.1_1.4.3_OpenXR-Plugin.logcat" is provided by the customer
-In the log at line 398 you should see the list of OpenXR extensions the device reports as supported
-At line 367, we can see 2 calls to xrCreateReferenceSpace that fail with XR_ERROR_REFERENCE_SPACE_UNSUPPORTED
-Additional behavior was observed by the customer:
"Not Specified" & "Floor" Tracking Origin result in the endless loop of xrLocateSpace failures and never recovers -> Black Screen.
"Device" & "Unbounded" Tracking Origin will initially give the same errors until it will eventually start rendering (and the errors stop) but the height is predefined from the Inspector.
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
- Find prefab components in scene is broken in new hierarchy
- Number "0" is not visible in Unity Documentation page button tooltips
- Selected Korean input text in UIToolkit TextField is not fully replaced when refocusing and entering new input
- [UITK Controls] Non text InputField can't be reset by API
- Control Scheme name field has no character limit, causing “Add Control Scheme” window to expand if name is too long
Resolution Note:
Unable to reproduce the issue on other hardware. Due to the logs indicating that xrCreateReferenceSpace fails with XR_ERROR_REFERENCE_SPACE_UNSUPPORTED, we believe the source of the issue is originates from the hardware's runtime.