Search Issue Tracker
Active
Under Consideration for 6000.4.X
Votes
0
Found in
6000.3.9f1
6000.4.0b9
Issue ID
UUM-134218
Regression
No
Hierarchy v2: Node action state not properly preserved/cleared during playmode transitions
Cut action state and visual styling are not properly synchronized when entering/exiting playmode in Hierarchy v2, leading to inconsistent behaviour compared to legacy hierarchy.
Issue 1
Steps to reproduce:
1. Cut a node in edit mode
2. Enter playmode
Actual results: Cut styling should be cleared (action is cleared)
Expected results: Visual styling remains, but cut action is gone
Issue 2
Steps to reproduce:
1. Cut and then delete a node in playmode
2. Exit playmode (node is restored)
Actual results: Legacy hierarchy: Cut action is preserved;
Hierarchy v2: Node appears as new, action not preserved
Expected results: Restored node should match legacy hierarchy behavior
Reproducible with versions: 6000.3,4,5
Not reproducible with versions:
Can’t test with versions:
Tested on (OS): Mac
Notes:
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Pressing “+” to add new Property throws “NullReferenceException” error after deleting Categories with Properties from Blackboard
- Reuse Collisions Callbacks is not enabled by default when opening a new project with HDRP template
- Bloom and Exposure Artifacting around GameObject appears when setting Scale of Z Axis to 0
- [Android][IL2CPP][ARMv7] Struct field value corrupts when invoking a generic delegate with a large struct by value
- Highlights persist throughout Options Panels in the Rendering Debugger Window
Add comment