Search Issue Tracker
By Design
Votes
0
Found in
2019.1.0a9
Issue ID
1101127
Regression
No
Changing "Update Mode" in Animator has no effect when it is done in Play mode
How to reproduce:
1. Open attached project "case_1084441-Playables_Update_Mode_Bug.zip" and scene "SampleScene"
2. In Hierarchy window, select "Cube"
3. In Inspector window, set Animator (component) -> Update Mode -> Normal
4. In Inspector window, set NewBehaviourScript (component) -> Director Update Mode -> Game Time
5. Enter Play mode
6. Observe Console window (in my case numbers around 0.0001695806 were printed)
7. While still in Play mode change Cube -> Animator (component) -> Update Mode -> Animate Physics
8. Observe Console window
Expected result: printed values are constantly "0.0167"
Actual result: printed values in my case were around "0.0001695806" (seems like the mode have not changed)
Reproducible with: 2017.4.15f1, 2018.3.0b11, 2019.1.0a9
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
- Lights with Cookies generate Cookie Atlas and increase Memory usage every time when Play mode is entered
- Crash on mono_traverse_object_internal when exiting Play mode on a specific project
- Camera prefab shows up in overrides after upgrade when game view is changed to Simulator
- Prefab Override context menu does not appear when changing attributes on a Terrain Component
- Particles are visible through Mesh when Sprite-Lit-Default Material is used
Resolution Note (2019.3.X):
This is by design: the Animator UpdateMode only influences the PlayableGraph created for its controller; all the other PlayableGraphs connected to the Animator through a PlayableOutput must be synced with the Animator UpdateMode manually. This is because the Animator only controls its own PlayableGraph created from the controller, but all the other PlayableGraph must be controlled by an external entity, whether it's a user script, or Timeline for instance.