Search Issue Tracker
Fixed
Fixed in 1.11.0
Votes
0
Found in [Package]
1.11.0
Issue ID
OXRB-363
Regression
Yes
“[OpenXR] The OpenXR Package Settings asset has duplicate settings and must be regenerated.“ warning is shown and the duplicates of the “XRPerformanceSettingsFeature“ appear when upgrading the OpenXR Plugin package version
How to reproduce:
1. Open the “OpenXRAssetBugRepro_2“ project
2. Navigate to “Edit/Project Settings/XR Plug-in Management/Project Validation“
3. Observe the warnings
4. Navigate to the “Assets > XR > Settings“ in the Project window
5. Expand the “OpenXR Package Settings.asset“
6. Observe the amount of the “XRPerformanceSettingsFeature“
Expected result: The warning “[OpenXR] The OpenXR Package Settings asset has duplicate settings and must be regenerated.“ is not shown and no duplicates of the “XRPerformanceSettingsFeature“ appear
Actual result: The warning “[OpenXR] The OpenXR Package Settings asset has duplicate settings and must be regenerated.“ is shown and the duplicates of the “XRPerformanceSettingsFeature“ appear
Reproducible with: 1.11.0 (2021.3.40f1, 2022.3.35f1, 6000.0.8f1)
Not reproducible with: 1.10.0, 1.11.0-exp.1 (2021.3.38f1, 2022.3.32f1, 6000.0.2f1)
Reproducible on: macOS 14.5 (Intel), Windows 10 (User’s)
Not reproducible on: No other environments tested
Notes:
- If you click on the “Fix” button near the “[OpenXR] The OpenXR Package Settings asset has duplicate settings and must be regenerated.“ warning, a new “OpenXR Package Settings.asset“ is created and the old one stays, but the old one has all existing settings wiped
- Deleting the “XR” folder and replacing it with the “XR” folder from a freshly unzipped “OpenXRAssetBugRepro_2“ project does not fix the issue
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Add comment