Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2018.4
2019.3.0f1
2020.2
Issue ID
1245722
Regression
No
[Playables] Animator.stabilizeFeet is set to False after the second time of calling the Update method when using Playables API
How to reproduce:
1. Open the project "case_1245722-Animator.stabilizeFeet"
2. Open the Scene "SampleScene"
3. Enter the Play Mode
4. Observe the Console window
Expected results: Animator.stabilizeFeet remains True in every call of the Update method because it was set to True in the Awake method
Actual results: Animator.stabilizeFeet is set to False after the second time of calling the Update method although it was set to True in the Awake method
Reproducible with: 2018.4.25f1, 2019.3.16f1, 2019.4.3f1, 2020.1.0b15, 2020.2.0a17
Notes:
1. Animator.stabilizeFeet is set to False after calling PlayableGraph.Evaluate method in the Awake method and remains Flase in every call of the Update method
2. Animator.stabilizeFeet remains True in every call of the Update method when it is set to True in the first call of the Update method
3. Animator.stabilizeFeet remains True in every call of the Update method when not using Playables API
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2022.1):
Fixed in: 2021.2.0b1