Search Issue Tracker
Fixed
Fixed in 6000.4.0a1
Votes
0
Found in
6000.4.0a1
Issue ID
UUM-116734
Regression
Yes
UIBuilder loses reference to VisualTree after entering playmode
Description
The VisualTreeAsset of a new UIBuilder is destroyed after entering playmode and never restored.
Initial setup
None
Reproduction steps
1. Open the UIBuilder
2. Create a new document
3. Add a VisualElement
4. Enter play mode
5. Stop play mode
6. Try to add a new VisualElement
Expected behaviour
Everything works are normally. The VisualElement is not greyed out in the Hierarchy view and the inspector display all the attributes of the selected VisualElement.
Actual behavior
4. The VisualElement is greyed out in the Hierarchy view. In the inspector, the attributes are lost.
6. An exception occurs when trying to add a new VisualElement because there is no VisualTreeAsset anymore.
Logs and Links
(Add links to Yamato jobs, links to logs, and add a stack trace in this section)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Add comment