Search Issue Tracker
By Design
Votes
0
Found in
2022.2.0a9
Issue ID
1413697
Regression
Yes
[UIToolkit] Element display is broken in UI Builder
Steps to reproduce:
1. Create a new uxml in the UI Builder
2. Drag in a Vector2/3/4 field
Reproducible with: 2022.2.0a9
Not reproducible with: 2022.2.0a8
Actual result: see the attached screenshot
Expected result: should look like it used to look in earlier versions
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
- Camera.current returns null when Camera.targetTexture is set to null in OnPostRender
- Crash on BaseHierarchyProperty::Next when opening a specific project
- Shader Compilation for projects with lots of Shaders can be slow (i.e. VFX Graph asset heavy projects)
- The Editor hangs when opening a project that uses local packages and Version Control
- Area Light is culled when Camera Frustrum is outside the lights range
Resolution Note:
This is working as designed. A few notes:
We have changed (from the original FogBugz issue 1402313) the way the Builder behaves by default. Mainly:
- We have removed all Editor-specific themes from the dropdown list by default, which means that if the user hasn’t checked the “Editor Extensions Mode” toggle in the Canvas parameters, the Default Editor theme should not be available anymore
- The default theme for a new Builder document is now Default Runtime Theme (unless Editor Extensions Mode is enabled)
- That runtime theme doesn’t have the same style property settings as the default editor theme (that includes the Vector 3 field which is showing in a different flex direction than the editor styles for example)
- By default, since the canvas size is rather small, the Vector 3 field might look a bit weird, but it’s not broken. You can adjust the size of the canvas to see how the field behaves