Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.14.1
Issue ID
OXRB-463
Regression
No
Errors are thrown when opening Profiler (Standalone Process) and OpenXR package is present in the project
Reproduction steps:
1. Create a new VR project
2. Open the Standalone Profiler (Window> Analysis> Profiler (Standalone Process))
3. Observe the result in the Profiler’s Console window
Expected result: No errors are thrown in the Profiler Console
Actual result: “CreateSerializedAsset is not supported while importing in a slave UnityEditor.EditorApplication:Internal_CallUpdateFunctions ()“ and “UnityException: Creating asset at path Assets\XR\Settings\OpenXR Package Settings.asset failed.“ exceptions are thrown in the Profiler Console
Reproducible in: 1.8.2 (2022.3.12f1) 1.14.1 (2022.3.59f1, 6000.0.41f1, 6000.1.0b8, 6000.2.0a6)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: On 2022.3.59f1 an additional exception is thrown multiple times: “Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL || uniqueDomainId == MonoDomainGetUniqueId()' UnityEditor.EditorAssemblies:ProcessInitializeOnLoadMethodAttributes ()“
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment