Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
4.1.0-pre.2
Issue ID
1348587
Regression
Yes
[OpenXR] Settings are not loaded for Oculus Quest when the Unity Editor build is executed in batchmode
How to reproduce:
1. Download the user's attached project: "case_1348587_repro"
2. Navigate through the explorer to the Unity's editor installation folder
3. In the command window run the following command "unity.exe -batchmode -executemethod CustomBuild.CheckFeatures -projectpath d:\temp\case_1348587_repro -logfile test.log -quit"
4. Wait a few minutes and then check the log file "test.log" located in the Editor's folder
Expected result: No errors appear
Actual result: The following error appears "Package Settings Corrupt"
Reproducible with:
Open XR 4.0.6 (2020.3.15f1)
Open XR 4.1.0-pre.2 (2021.1.16f1, 2021.2.0b6, 2022.1.0a4)
Not reproducible with:
Open XR 4.0.5 (2020.3.15f1)
Could not test with: 2019.4.29f1 (project breaks after downgrading)
Notes:
- Make sure to change the commands project's path accordingly, or move the project to a folder located in "d:\temp"
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #1357482