Search Issue Tracker
By Design
Votes
0
Found in
2022.2.6f1
2023.1.0b1
2023.1.0b3
Issue ID
UUM-27310
Regression
No
Renaming a child object does not rename it in the parent's animator
*What happened?*
If you rename a child object that has animation properties present in it's parent's animation, the animation will no longer have a reference to the correct child object and the animation will no longer work.
Current workaround is just to rename the child object back to it's original name. This will fix the animation.
*Steps to Reproduce*
# Create a new Unity project on one of the affected versions
# Create a new Game Object, and a child Object within that
# Add an animation to the Parent object that contains a Property from the child object below it.
# Rename the child object
# Observe within the animation, the property is now labelled as 'Missing!' and the animation does not play correctly
*Expected Result*
When an object is renamed, it will correctly update it's name within the Animator so that the animation is not broken.
*Actual Result*
The animator's reference to the object is broken once renamed, so the object would have to be animated again.
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
- Frame Debugger's Hierarchy is not navigable when connecting it to the project built with the Volumetric Fog
- The number of SetPass Calls is increasing when attaching the Frame Debugger to the Player
- Scrollbar briefly appears in the Package Manager during installation process even when the package list is too short to require scrolling
- Script resets to use the previous Skybox color when saving the Scene changes
- [2D] Sprite Library Editor window throws NullReferenceException error when entering Play Mode with Game View maximised
Resolution Note:
This is by design