Search Issue Tracker
Fixed in 1.6.0
Votes
0
Found in [Package]
1.5.0
1.5.3
Issue ID
OXRB-100
Regression
Yes
[OpenXR] OpenXR plugin throws errors when developing without connected VR headset
Steps to reproduce:
1. Open the attached user's project "TestProjectBugReport.zip"
2. Make sure the OpenXR is selected as the XR plugin
3. Connect Quest 2 and enable the Oculus link
4. Enter and exit Play Mode
5. Disconnect the Oculus link
6. Enter Play Mode
7. Observe the Console window being spammed every 5 seconds with 4 messages, two warnings, one info and one error
Expected results: Only 1 message is logged and the Console is not spammed every 5 seconds
Actual results: Every 5 seconds 4 messages are logged, two warnings, one info and one error relating to not having a VR device connected (See Results.png)
Reproducible on: OpenXR 1.5.0 - 1.5.3 (2020.3.41f1, 2021.3.14f1, 2022.1.22f1, 2022.2.0b16, 2023.1.0a20)
Not reproducible on: OpenXR 1.4.2 (2020.3.41f1, 2021.3.14f1, 2022.1.22f1)
Notes:
-Does not reproduce with OculusXR 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
- AI Assistant upgrade banner's `Open package Manager` link doesn't work
- Sub-asset UI does not refresh when undoing Renderer Feature add or remove actions in a URP Renderer asset
- Scene flickers with a green tint when using Screen Space Ambient Occlusion and Contact Shadows with raytracing
- Scripts with null Components on GameObjects are not removed when calling GameObjectUtility.RemoveMonoBehavioursWithMissingScript
- Color Curve Key values remain visible after changing Curve type
Resolution Note (fix version 1.6.0):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/OXRB-88
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/OXRB-88