Search Issue Tracker
Active
Fixed in 2022.3.35f1, 6000.0.7f1
Votes
31
Found in
2022.3.27f1
6000.0.0f1
7000.0.0a1
Issue ID
UUM-71809
Regression
No
LOD Group renderers incorrectly retain their asset path when instantiated using InstantiateAsync
How to reproduce:
1. Open the attached “IN-74727” project
2. Open the “SampleScene”
3. Select the “Test” GameObject in the Hierarchy
4. In the Inspector, press the “Instantiate Prefab” button to create two GameObjects, one using Instantiate, and the other using InstantiateAsync
5. Observe the result in the Console window
Expected result: For both instantiated GameObjects, “IsPersistent” returns false and the renderer asset path is empty
Actual result: The GameObject instantiated with InstantiateAsync shows the renderer asset path as “Assets/Prefab_LOD.prefab” and “IsPersistent” returns true
Reproducible in: 2022.3.27f1, 6000.0.0f1
Could not test with: 2021.3.38f1 (InstantiateAsync is not supported)
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested
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
- Shader Keywords are not detected when defined in include files
- Right-clicking on Blackboard and Graph Inspector calls the contextual menu of the workspace
- [Android][Vulkan]Shader casting issue occurs when using Snapdragon devices with the Vulkan Graphics API
- "Paste" option is available in Shader Graph contextual menu even when the clipboard has unrelated item
- Editor crashes when debugging a for loop
Resolution Note (fix version 2022.3.35f1):