Search Issue Tracker
Fixed
Fixed in 6000.2.0b9, 6000.3.0a2
Votes
0
Found in
2022.3.63f1
6000.2.0b5
6000.3.0a1
Issue ID
UUM-109114
Regression
Yes
Name of the first renamed Visual Element does not change in the UI Builder Hierarchy when it’s being renamed in the Inspector
Steps to reproduce:
1. Create a new project
2. Create UI Document (Create > UI > UI Document)
3. Double-click on the newly created UI Document to open UI Builder window
4. Drag Visual Element into Hierarchy section twice
5. Click on one of the Visual Elements and rename it in the Inspector section
6. Click on the another Visual Element and observe the name of the first Visual Element in the Hierarchy
Actual results: Visual Element does not get renamed
Expected results: Visual Element name changes into a new one
Reproducible with versions: 2022.3.63f1, 6000.2.0b1, 6000.2.0b5
Not reproducible with versions: 2021.3.52f1, 6000.0.51f1, 6000.1.7f1, 6000.2.0a10
Tested on (OS): macOS Sequoia 15.4 (M4)
Notes:
- Issue is not reproducible when renaming second Visual Element
- Third visual element cannot be viewed on Inspector when pressed on it, only second Visual Element is visible, clicking on the second Visual Element and clicking on the third Visual Element again makes issue not reproducible
- Renaming Visual Element with right-click > Rename does not reproduce the issue
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment