Search Issue Tracker
Won't Fix
Votes
3
Found in [Package]
4.2.1
Issue ID
XRMB-8
Regression
No
[XR] XRManagerSettings.TrySetLoaders doesn't work at runtime
Reproduction steps:
1. Open the attached user's project "TrySetLoaders Bug.zip"
2. Build for Quest 1/2
Expected result: XRManagerSettings.TrySetLoaders works at runtime thus application doesn't fail to initialize with ARCore and Oculus plugins installed
Actual result: XRManagerSettings.TrySetLoaders doesn't work at runtime thus application fails to initialize with ARCore and Oculus plugins installed
Reproduces on: 2019.4.36f1, 2020.3.31f1, 2021.2.15f1, 2022.1.0b11, 2022.2.0a6
Reproducible on these devices:
N/A, Oculus (Quest), Android 10, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00415 - Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 10
Notes:
-Issue reproduces with OpenXR and Oculus plugins
Comments (1)
-
Tudvari
Nov 28, 2022 16:21
While we are waiting for the fix, could you please state this issue in the official documentation?
It was a very very long and frustrating ride to finally find out that it's not my fault that it doesn't work. And that I need some hacky code to fix it before the patch is live.
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
QA confirmed that this behaviour is no longer happening.