Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
2
Found in
2018.4
2019.4
2020.2
2020.2.2f1
2020.3
2021.1
2021.2
Issue ID
1311378
Regression
No
'Invalid time range' error appears in the Console when passing < 0.02f values as normalizedTime parameter to the Animator.Play
How to reproduce:
1. Open the attached '1311378.zip' project
2. Open 'SampleScene'
3. Enter the Play mode
4. Observe the Console
Expected result: There are no visible errors present
Actual result: The 'Invalid time range for Transition exit time condition' error gets thrown in the Console
Reproducible with: 2018.4.32f1, 2019.4.22f1, 2020.2.7f1, 2020.3.0f1, 2021.1.0b10, 2021.2.0a8
Notes:
- The issue doesn't reproduce with values that are >= 0.02f
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
- 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
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a12
Resolution Note (fix version 2021.1):
Fixed in 2021.1.14f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.16f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.29f1