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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
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.