Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1120363
Regression
No
Evaluate() doesn't evaluate a Timeline when animated GameObject has a reference to a Controller in the Animator Component
Steps to reproduce:
1. Open the original project
2. Navigate to Project -> Assets -> Scenes
3. Open "SampleScene"
4. Press Play
Expected results: PlayableDirector.Evaluate() evaluates the Timeline
Actual results: Animator Controller prevents PlayableDirector.Evaluate() from working which prevents Animation in the Timeline from playing
Reproducible with: 2017.4.20f1, 2018.3.5f1, 2019.1.0b2, 2019.2.0a4
Notes: This Animation works in Editor Mode but doesn't work in 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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note:
PlayableDirector.Evaluate() evaluates the timeline immediately for the given frame, and the results may be overwritten later in the frame (e.g. by an Animator Controller). Play() on the director will layer the timeline on top of the animator controller. DeferredEvaluate() will evaluate the timeline at the end of the next frame, which may be the desired behaviour here.