Search Issue Tracker
Fixed in 4.2.0
Votes
10
Found in [Package]
4.0.6
Issue ID
1357482
Regression
Yes
[XR SDK] XR Settings get reset after building a project without Library folder with -batchmode argument
Reproduction steps:
1. Download the attached "1357482.zip" project
2. Note the content of "Open XR Package Settings.asset" in Assets > XR > Settings folder
3. Modify the "build.bat" script to point to correct paths
4. Run the script
5. Observe "Open XR Package Settings.asset" content
Expected result: the "Open XR Package Settings.asset" does not change
Actual result: the "Open XR Package Settings.asset" gets reset
Reproducible with: XR Management 4.0.6, 4.0.7 (2021.2.0b7, 2022.1.0a5)
Not reproducible with: XR Management 4.0.5 (2021.2.0b7, 2022.1.0a5)
Notes:
- tested with OpenXR and Oculus XR plug-in providers
- to be able to reproduce the issue again, copy "Open XR Package Settings.asset" from the zip file and delete the Library folder
-
hschulte
Sep 20, 2021 07:28
This is a serious bug preventing us from switching to OpenXR right now. No controller devices are recognized in builds coming from our CI pipeline.
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
Resolution Note (fix version 4.2.0):
Fixed with XR SDK 4.2.0 (2022.1.0a13)