Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2022.1.16f1
2022.2.0a12
Issue ID
UUM-14011
Regression
No
TrackPropertyValue does not track the value when managedReferenceValue is null
To reproduce:
1. Open the project “BugTesting”
2. Select “SPUndo” GameObject in the Hierarchy
3. Click the ““ button in the Inspector
4. Select any other GameObject in the Hierarchy
5. Select “SPUndo” GameObject in the Hierarchy
6. Click “” and “-” in the Inspector and note how the bar is changing its color
7. Click the “-” button in the Inspector
8. Select any other GameObject in the Hierarchy
9. Select “SPUndo” GameObject in the Hierarchy
10. Click “+” and “-” in the Inspector
Expected result: The bar is changing its color like in the 6th step
Actual result: The bar remains green
Reproducible with: 2022.1.16f1, 2022.2.0a12
Not reproducible with: 2022.2.0a13, 2022.2.0b7, 2023.1.0a10
Could not test with: 2020.3.39f1 (Console errors), 2021.3.9f1 (Warning*)
Reproduced on: macOS Monterey 12.5.1 (Intel)
Notes:
- The script is at Assets → SerializedPropertyUndo → Editor
- 2021.3.9f1 Warning “Binding is not supported for managedReference<SPUndoSubclass> properties "reference"“
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note:
2022.2 is already fixed (we are not sure what commit did that). 2022.1 is the only remaining affected version, so closing the ticket
Resolution Note (2022.2.X):
2022.2 is already fixed (we are not sure what commit did that). 2022.1 is the only remaining affected version, so closing the ticket