Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.0.64f1
6000.2.15f1
6000.3.2f1
6000.4.0b1
6000.5.0a3
Issue ID
UUM-130101
Regression
No
Inconsistent “Remove property” behavior when removing child properties in Animator window
Steps to reproduce:
1. Create new Unity project
2. Make sure Editor theme is set to Light
3. Create a new "Cube" GameObject (GameObject > 3d Object > Cube)
4. Open the Animation window (Window > Animation > Animation)
5. Create a new animation by pressing the "Create" button in the Animation window
6. In Animator window press “Add Property”
7. Add Transform > Position property
8. Expand the Property
9. In Position.x property press on button on the right and select “Remove properties”
10. Observe Transform Property getting deleted
11. In Animator window press “Add Property”
12. Add Box Collider > Center
13. In Center.x property press on button on the right and select “Remove property”
14. Observe “Cube : Center” Property
\\
Actual results: Inconsistent behavior between Properties deletion, removing Transform child properties, deletes entire Transform Property, meanwhile on Box Collider Property, deleting Center.x removes only child
Expected results: Consistent behavior across context menus, wither both remove selected child property or both remove the entire parent block
\\
Reproducible with versions: 6000.0.64f1, 6000.2.15f1, 6000.3.2f1, 6000.4.0b1, 6000.5.0a3
\\
Tested on (OS): maOS Tahoe 26.1 (M1)
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
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- "Editor unavailable" message is displayed when navigating to "Get set up" tab in Unity Hub
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
Resolution Note:
This is by designed and will be closed for the following reasons…
1) “Transforms” are an exception for animation where all three floats of the transform vector MUST be animated. This is an architectural decision made for performance reasons.
2) Deleting keys in a clip vs Add/Remove properties to a clip are two different operations should not be compared for consistency.
a) Deleting all keys from a single transform property gives the property its “default” value, since it cannot be removed from the clip (transform vector). This means the property will be evaluated with its default value, not the scene value.
b) Remove Properties removes the entire transform vector. The transform vector (not a single property) is either animated or not animated. This is why the entire transform vector is removed.
As for the exceptional behaviour of removing all floats from the transform vector instead of only removing the specifically selected float, this is expected and required behaviour for optimizing runtime performance.
Thank you for your feedback and hope this explanation help understand this behaviour a bit better.
Resolution Note (6000.5.X):
This is by designed and will be closed for the following reasons…
1) “Transforms” are an exception for animation where all three floats of the transform vector MUST be animated. This is an architectural decision made for performance reasons.
2) Deleting keys in a clip vs Add/Remove properties to a clip are two different operations should not be compared for consistency.
a) Deleting all keys from a single transform property gives the property its “default” value, since it cannot be removed from the clip (transform vector). This means the property will be evaluated with its default value, not the scene value.
b) Remove Properties removes the entire transform vector. The transform vector (not a single property) is either animated or not animated. This is why the entire transform vector is removed.
As for the exceptional behaviour of removing all floats from the transform vector instead of only removing the specifically selected float, this is expected and required behaviour for optimizing runtime performance.
Thank you for your feedback and hope this explanation help understand this behaviour a bit better.