Search Issue Tracker
Fixed in 1.6.0
Won't Fix in 4.2.X
Votes
2
Found in [Package]
1.5.1
Issue ID
OXRB-88
Regression
No
OpenXR error looped when no HMD is present
Reproduction steps:
- Open the user's attached project
- Make sure no VR headset is connected to the computer
- Enter Play mode
Expected result: “Please make sure the device is connected. Will try to restart xr periodically.” error message in the Console
Actual result: 4 different error messages that update each second
Reproduced with: 4.2.0 (2021.3.12f1, 2022.1.20f1, 2022.2.0b11, 2023.1.0a14), 4.2.1 (2023.1.0a14)
Could not test with: 2020.3.40f1 (Due to errors)
Reproducible on: Windows 11
Comments (2)
-
CDKML
Feb 17, 2023 12:28
Same here, updated to 1.6.0 and it crashes Unity when i hit play
-
ertanturan
Dec 20, 2022 11:53
This issue is not fixed yet unfortunately. I've updated the packages to their latest versions particularly openxr to 1.6.0 but now it crashes Unity if there's no hmd present.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
This will be resolved when we release com.unity.xr.openxr@1.6.0
Resolution Note (4.2.X):
This port was created in error and is actually addressed in https://jira.unity3d.com/browse/OXRB-102