Search Issue Tracker
Not Reproducible
Votes
0
Found in
6000.3.0a1
Issue ID
UUM-109639
Regression
Yes
Console error logged when adding VR feature: Error adding new OpenXR Settings object to build settings.
When adding the VR feature from the Unity registry in 6000.3.0a1 to a new 3D URP project template, a log is created in the console that claims to be an error message.
{quote}Error adding new OpenXR Settings object to build settings.
Cannot add null config object with name 'com.unity.xr.openxr.settings4'.
UnityEditor.SettingsWindow:OnEnable ()
{quote}
The number isn't always four in the error, I've seen it vary. I am not sure yet if this occurs in every supported editor, that would take some time to test and it's in the middle of hackweek right now.
*Steps to reproduce:*
# Create a new 3D URP template project in trunk or open the XR QA XR Manual Functional Test Suite - [ManualFunctionalTest|https://github.cds.internal.unity3d.com/unity/xr.manualtests.functional/tree/main/ManualFunctionalTest].
# Update the packages in package manager that have updates.
# Install the VR feature from the Unity registry.
*Expected results:*
No log like this should be generated, it's not informative or helpful in the context of adding the VR Feature from the Unity registry. It should be suppressed in this feature adding circumstance, or removed.
*Actual results:*
A log is created in the console that claims to be an error message.
Error adding new OpenXR Settings object to build settings.
Cannot add null config object with name 'com.unity.xr.openxr.settings4'.
UnityEditor.SettingsWindow:OnEnable ()
*Reproducible with versions:*
1.15.0-pre.2
*Not reproducible with versions:*
unknown/untested
*Can’t test with versions:*
N/A
*Tested on (OS):*
Windows 11
*Notes:*
* Employ the bisection team or I can test this further at a later time after hackweek is over.
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
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Resolution Note:
We cannot reproduce the bug anymore (multiple machines, multiple OS, multiple devs).