Search Issue Tracker
Fixed
Fixed in 6000.2.6f1, 6000.3.0b3, 6000.4.0a1
Votes
14
Found in
6000.2.0b12
6000.3.0a3
6000.4.0a1
Issue ID
UUM-112944
Regression
Yes
UI Builder does not detect changes to SerializeReference fields when modifying custom UXML Control attributes
Reproduction steps:
1. Open the attached “IN-109761.zip” project
2. From the Project Window, open the “MyDocument.uxml” in UI Builder
3. From the Hierarchy, select “MyCustomControl”
4. In the Inspector under Attributes, expand the My Test > My Class > My Reference properties
5. Modify the “My String” or “My Int” field values and observe them
Expected result: All modified fields should show as overridden with "dirty" marking in the UI Builder Inspector
Actual result: SerializeReference fields (“My String” and “My Int”) are not marked as dirty
Reproducible with: 6000.2.0b1 (1618a92a88ac), 6000.2.0b12, 6000.3.0a3
Not reproducible with: 6000.0.54f1, 6000.1.13f1, 6000.2.0a10
Reproducible on: macOS 15.5 (M4 Max), Windows 11
Not reproducible on: No other environment tested
Notes:
- Only the “My String” property (which is a direct reference) under “My Class” foldout behaves correctly and shows the override
- If the fields are shown as dirty at the very start, left-click on any of the properties and select “Unset all” and then perform the reproduction steps
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Default state” name in Inspector is not truncated when given longer name for “New State” in Animator window
- Upgrading HDRP Project causes the Cloud Layer to warp when using the Global Volume with the Visual Environment enabled
- The Inspector does not shown SkinnedMeshRenderer Bounds when they are overriden by script
- Confusing validation message in Scoped Registries
- Compute shader is dispatched with unsupported workgroup size on multiple browsers when building the project for Web with WebGPU Graphics API
Add comment