Search Issue Tracker
Third Party Issue
Third Party Issue in 4.1.X
Votes
0
Found in [Package]
4.1.2
Issue ID
OXPB-142
Regression
No
[Quest] Editor crashes on ovrp_UnityOpenXR_OnSessionDestroy with a specific project when entering the Play Mode for the second time without VR connected
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/BorderDemo.unity” Scene
3. Enter the Play Mode
4. Exit the Play Mode
5. Repeat step 3
Expected result: Editor does not crash and continues to run
Actual result: Editor crashes
Reproducible with: 2021.3.35f1, 2022.3.20f1, 2023.2.11f1, 2023.3.0b8
Reproducible on: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
First few lines of the Stacktrace:
{{0x00007FFAB912882F (OVRPlugin) ovrp_UnityOpenXR_OnSessionDestroy}}
{{0x00007FFAB9121CF9 (OVRPlugin) ovrp_UnityOpenXR_OnSessionDestroy}}
{{0x00007FFAB9152724 (OVRPlugin) ovrp_UnityOpenXR_OnSessionDestroy}}
{{0x00007FFAB90E3ED9 (OVRPlugin) ovrp_Initialize7}}
{{0x00007FFB14173AE7 (OculusXRPlugin) XRSDKPreInit}}
Notes:
- Only reproduces without VR connected
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
- 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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
This issue is caused by the Vive Input Utility's project validator tool. It will enable OpenXR even if another loader is already active, which is not allowed by Unity. We have reported this issue to HTC: https://github.com/ViveSoftware/ViveInputUtility-Unity/issues/272
The workaround is to go to XR Plugin Management and ensure that only one loader is checked.
Resolution Note (4.1.X):
This issue is caused by the Vive Input Utility's project validator tool. It will enable OpenXR even if another loader is already active, which is not allowed by Unity. We have reported this issue to HTC: https://github.com/ViveSoftware/ViveInputUtility-Unity/issues/272
The workaround is to go to XR Plugin Management and ensure that only one loader is checked.