Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.1.0a13
2019.2.0a1
Issue ID
1117299
Regression
No
Animation behaves differently in Edit and Play modes when animation's Bake Into Pose settings are enabled
How to reproduce:
1. Open the attached project named "Case_1117299"
2. Select the "New Timeline" and Play the Timeline Preview. Observe the behavior of two objects(they are in sync)
3. Click the Scene Play button
4. Observe the issue
Expected result: Objects are synchronized just like in the Timeline preview
Actual result: Objects are not synchronized.
Reproducible with - 2017.4.18f1, 2018.3.3f1, 2019.1.0a14, 2019.2.0a1
Notes:
If the animation has the Bake Into Pose settings enabled and the object Animator controller is set to "None (Runtime Animator Controller)" the animation works properly in the Play mode.
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:
Edge case. Will not fix because of high level risk of fix.
The fact of adding an AnimatorController makes it that the Timeline Root Motion handling is done differently ( AnimatorController is always the base layer)
This explains the different at runtime.
Workaround is to not attach AnimatorController.