Search Issue Tracker
Won't Fix
Won't Fix in 1.2.X
Votes
1
Found in [Package]
1.2.3
Issue ID
OXRB-27
Regression
No
[OpenXR][HDRP][Oculus] The Editor crashes when leaving the Play Mode during Oculus Link whilst using DX12 as the Graphics API
How to reproduce:
1. Open the user's attached project
2. Connect an Oculus device through Oculus Link
3. Make sure DX12 is selected as the Graphics API (Project Settings -> Player -> Other Settings)
4. Enter and then leave the Play Mode
Expected result: The Editor does not crash
Actual result: The Editor crashes with multiple multiple errors such as: "ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FF60C01762C)
0x00007FF60C01762C (Unity) (function-name not available)"
Reproducible with: 2020.3.13f1, 2021.1.14f1, 2021.2.0b2, 2022.1.0a1
Could not test with: 2018.4.36f1, 2019.4.29f1 as OpenXR is not supported on these versions
Reproducible on:
VLNQA00379, Oculus Quest 2 (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Notes:
- Does not crash when using DX11 instead of DX12
- HDRP version 12.0.0 is used in the project
- This was tested on Windows 10
- Also crashes on a new OpenXR HDRP project
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
- Material's icon doesn't fit the "Material preview not available" text when the Material doesn't have a preview
- Two fields in GLTF Importer Inspector are misaligned with other settings
- Duplicate image components can be added in m_TrackedTextureLess images and are never removed
- Cancelling a Package installation leads to invisible compilation errors preventing the user to enter Play Mode when the “Cancel” button is clicked, and does not actually cancel the package install as it appears in the Project after the Editor is restarted
- NullReferenceException occurs when searching presets in “Select Preset” window after selecting a GLTF Importer preset
Resolution Note:
We are not able to reproduce this issue. If you are still encountering this issue, please notify us.
Resolution Note (1.2.X):
We are not able to reproduce this issue. If you are still encountering this issue, please notify us.