Search Issue Tracker
Fixed in 6000.1.3f1
Fixed in 6000.1.X, 6000.2.X, future release
Votes
0
Found in
2021.3.45f1
2022.3.53f1
6000.0.28f1
6000.1.0a4
6000.2.0a1
Issue ID
UUM-87528
Regression
No
UI does not display until editor refresh if assign Source Asset before Panel Settings to UI Document component
Steps to reproduce:
- Open a Unity Project
- In the Project Window, create a new Panel Settings asset via Create > UI Toolkit > Panel Settings Asset
- In the Project Window, create a new UI Document via Create > UI Toolkit > UI Document
- Open the UI Document in UI Builder (double-click on the asset) and add one or more visible element/s to it (e.g. drag a button from the library to the hierarchy)
- Save and then close UI Builder
- Add an empty GameObject to the Scene via GameObject > Create Empty
- Select the new GameObject
- Add a UI Document component to the GameObject
- Assign your created UI Document as the Source Asset in the component
- Assign your created Panel Settings Asset as the Panel Settings in the component
- Observe the Game view
Actual results: The created UI does not display straight away. You have to either have the editor refresh by changing another setting (e.g. Sort Order) or enter playmode, to get the UI to display in Game view.
Expected results: The created UI displays straight away.
If you assign the Panel Settings before the Source Asset then this is how it works (the bug does not occur).
Reproducible with versions: 6000.1.0a4, 6000.0.28f1, 2022.3.53f1, 2021.3.45f1
Not reproducible with versions: -
Can’t test with versions: -
Tested on (OS): MacOS Sonoma 14.6.1
Notes:
- This bug was a particular pain point as I thought I had broken the UI in some way, or that it had not been setup correctly, when it didn't display at first.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Add comment