Search Issue Tracker
Duplicate
Votes
8
Found in
2019.3.0b1
2019.4
2019.4.22f1
2020.3
2021.1
2021.2
Issue ID
1323966
Regression
Yes
Animator parameters revert to default state when switching to AnimatorOverrideController in Play mode
How to reproduce:
1. Open the user's attached project "AnimatorOverrideTest2019.zip"
2. From the Project tab, open Assets/TestScene.unity
3. Make sure that Inspector (Window > General > Inspector) and Animator (Window > Animation > Animator) windows are visible, as well as Game View
4. Enter Play mode
5. In the Hierarchy window, click on TestObject
6. In the Animator window, change TestParameter to a different number than is currently set
7. From the Project tab, drag DefaultAnimatorOverrideController and drop it in the Inspector tab, as TestObject's Animator's Controller
8. In the Animator window, check what the value of TestParameter is
Expected results: TestParameter has the same value as was set in step 6
Actual results: TestParameter reverts to the previous value
Reproducible with: 2019.3.0b1, 2019.3.16f1, 2019.4.27f1, 2020.3.8f1, 2021.1.8f1, 2021.2.0a17
Not reproducible with: 2018.4.35f1, 2019.3.0a11
Could not test with: 2019.3.0a12 due to license errors when trying to open Editor
Notes:
- The value doesn't revert to its previous state if steps 5-8 are executed when Play mode is not entered
- Documentation (https://docs.unity3d.com/2019.4/Documentation/ScriptReference/AnimatorOverrideController.html) says that "Swapping Animator.runtimeAnimatorController with an AnimatorOverrideController based on the same AnimatorController at runtime doesn't reset state machine's current state."
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #1271499