Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.2.X
Votes
5
Found in
2018.3.10f1
2018.3.12f1
2019.1.0b8
2019.2.0a9
Issue ID
1144501
Regression
Yes
Animator Component causes "Assertion failed on expression: 'index < m_ScaleCount'" messages when in Play Mode
How to reproduce:
1. Open the attached project "AnimatorAssertions.zip" and scene "SampleScene"
2. Enter Play Mode
3. Observe the Console Window
Expected result: no assertions in the Console Window
Actual result: error messages "Assertion failed on expression: 'index < m_ScaleCount'" populate the Console Window
Reproducible with: 2018.3.10f1, 2018.3.13f1, 2019.1.0b8, 2019.1.0b10, 2019.2.0a9, 2019.2.0a11
Not reproducible with: 2018.3.9f1, 2019.1.0b7, 2019.2.0a8
Note: the animations seem to be still working correctly. Error messages stop being printed when the Animator Component is disabled
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment