Search Issue Tracker
Third Party Issue
Third Party Issue in 1.6.X
Votes
0
Found in [Package]
1.5.3
1.6.0
Issue ID
OXRB-109
Regression
Yes
OpenXR crashes on session_RequestExitSession when VR headset is not connected to computer
Reproduction steps:
1. Open user attached project "VR-Screenshake-Test.zip"
2. Make sure no VR headset is connected to the computer
3. Enter Play mode
Expected result: Error message that Headset is not connected
Actual result: Crash
Reproduced with: 1.5.3 (2023.1.0a21), 1.6.0 (2020.3.34f1, 2021.3.16f1, 2022.1.24f1, 2022.2.2f1, 2023.1.0a24)
Reproducible on: Windows 11
First few lines of the stack trace::
0x00007FFD84BFA502 (UnityOpenXR) session_RequestExitSession
0x00007FFD84BF9823 (UnityOpenXR) session_RequestExitSession
0x00007FFD84BCE073 (UnityOpenXR) DiagnosticReport_StartReport
0x00007FFD84BCD500 (UnityOpenXR) DiagnosticReport_StartReport
0x00007FFD8B9C46CA (Unity) Subsystem::InitializePlugin
Note:
- Crashes in builds as well
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
We also observed this issue lately and reported it to Meta team. This failure mostly happen when the headset is disconnected and also if the oculus link is not started during initialization. According to the responses from Meta this issue would be fixed in the next SDK release.
Resolution Note (1.6.X):
We also observed this issue lately and reported it to Meta team. This failure mostly happen when the headset is disconnected and also if the oculus link is not started during initialization. According to the responses from Meta this issue would be fixed in the next SDK release.