Search Issue Tracker
By Design
Votes
0
Found in
2020.3
2020.3.23f1
2021.2
2022.1
2022.2
Issue ID
1384361
Regression
No
Walking animation stops working when creating a new clip in the Animation window
How to reproduce:
1. Open the "1384361.zip" project that is located in the google drive link
2. In the Hierarchy window select "PlayerAmature" GameObject
3. Open Window > Animation > Animation
4. Click Create new Clip
5. Click Add Property > right-click Animator > Add Properties
6. Enter Play Mode and observe the controllable character
Expected result: Characters walking animation is working
Actual result: Characters walking animation isn't working
Reproducible with: 2020.3.27f1, 2021.2.10f1, 2022.1.0b7, 2022.2.0a4
Can't reproduce with: 2019.4.35f1 (can't resolve console error)
Note:
1. The new animation clip is not connected to anything in the Animator window, so it shouldn't affect current animations
2. Jumping animation still works
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
This is by design.
When the state machine contains Animated curves that matches the names of a Parameters, those parameters becomes "driven by" those curves, meaning that the values of those parameters will be updated every frame to: the value of the evaluated curve, the default value, or last value, depending on the configuration of the currently playing state and/or the presence of a clip that writes to that parameter in the state.
Following the repro steps, the animation clip ends up containing animated properties with the names "Speed" and "MotionSpeed", which matches the names of the Parameters defined in the Animator Controller that controls the Idle, Walk, Run transitions. So that means that if the "New animation" is not being played, those driven parameters are being overwritten using their default value of 0 every frame.
If you enter playmode, and open the Animator window with the Parameters tab open, you can see that the "Speed" and "MotionSpeed" parameters are shown as read only, signifying that they are "driven" values.