Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2020.3
2020.3.18f1c1
2021.1
2021.2
2022.1
Issue ID
1365552
Regression
No
Animator.parameterCount returns 0 when changing the Animator State's Motion through a script
How to reproduce:
1. Open the user-submitted project
2. Open the Scene "SampleScene.unity" (Assets/Scenes/SampleScene.unity)
3. Enter Play mode
4. In the Game view, click the Button GameObject
5. Observe the Console window (Window > General > Console)
Expected result: The message "-----------------1 start print param, count: 7" is printed
Actual result: The message "-----------------1 start print param, count: 0" is printed
Reproducible with: 2019.4.30f1, 2020.3.18f1, 2021.1.22f1, 2021.2.0b12, 2022.1.0a8
Note: On rare occasions, the amount of Parameters the Animator has is correctly returned as 7 instead of 0
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
Resolution Note:
After evaluating the impact, workaround and risk associated with fixing this issue, in addition to the current team's bandwidth and priorities, we have concluded that this issue will not be addressed in the foreseeable future.
We are closing this issue as Won’t Fix.
Making any changes to the state machine you can expect most of the Animator to be invalid until the end of the frame. This includes changing state animations or simply moving a state around in the editor which will disrupt live edit.