Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2018.1.0b10
2019.3.15f1
2019.4
2020.1
2020.2
Issue ID
1253379
Regression
Yes
AnimatorOverrideController produces glitches in transitions when it is created at runtime
How to reproduce:
1. Open user's attached "AnimatorBlendingTest2019.zip" project
2. Open "test" Scene
3. Open TestAnimatorController in the Animator window
4. Make sure parameters are visible in the Animator window
5. Make sure that Animator window would be visible during Play Mode
6. Enter Play Mode
7. Observe the parameters and transitions in the Animator window
8. Observe the GameObject in the Game view, which has "created at runtime" text written above it
Expected result: OnAnimatorMove changes GameObject's color when CurveValue is changed on the first animation (step 7)
Actual result: OnAnimatorMove changes GameObject's color on every animation even when CurveValue is not changed (step 7)
Reproducible with: 2018.1.0b10, 2018.4.23f1, 2019.4.2f1, 2020.1.0b13, 2020.2.0a15
Not reproducible with: 2018.1.0b9
Notes:
- AnimatorController and AnimatorOverrideController, which are created in the Editor doesn't produce any glitches
- Attached a video for reference in edit
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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a20
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.2f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.9f1