Search Issue Tracker

Fixed in 2020.2.X

Fixed in 2019.4.X, 2020.1.X

Votes

0

Found in

2019.3.12f1

2019.3.15f1

Issue ID

1253155

Regression

Yes

Clip Count is not updated correctly when Animator.runtimeAnimatorController is changed twice on the same frame

Animation

-

Reproduction steps:
1. Open the user's attached "AnimatorCrash - Copy.zip" project
2. Load the "SampleScene"
3. Select the "Animator" GameObject in the Hierarchy window and enter Play mode
4. Open Game view and press C key on the keyboard
5. Observe the "Clip Count" value of the Animator Component in the Inspector window
6. Press the C key again

Expected result: Runtime Animator Controller is set to the "AnimatorController" and Clip Count is 1
Actual result: Runtime Animator Controller is set to the "AnimatorController" but Clip Count is 0

Reproducible with: 2019.3.12f1, 2019.3.16f1, 2019.4.0f1, 2020.1.0b12, 2020.2.0a14
Not reproducible with: 2018.4.23f1, 2019.3.11f1

Note: a warning message appears each time Clip Count is set to 0: "PlayableGraph being evaluated with no outputs. Playables will not be updated"

  1. Resolution Note (fix version 2020.2):

    Fixed in: 2020.2.0a19

  2. Resolution Note (fix version 2020.1):

    Fixed in: 2020.1.1f1

  3. Resolution Note (fix version 2019.4):

    Fixed in: 2019.4.8f1

Log in to vote on this issue

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues