Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
0
Found in
2018.4
2019.4
2019.4.18f1
2020.2
2021.1
2021.2
Issue ID
1308930
Regression
No
[UI] Float type parameter in the Animator Controller displays 0.0 after being changed to a value <0.05
How to reproduce:
1. Open the user's attached project
2. In the Project window double-click on 'New Animator Controller'
3. In the Animator window select 'Parameters'
4. Set the 'New Float' value to 0.01
Expected result: The 'New Float' value is 0.01
Actual result: The 'New Float' is 0.0
Reproducible with: 2018.4.31f1, 2019.4.19f1, 2020.2.3f1, 2021.1.0b4, 2021.2.0a3
Notes:
- The issue is reproducible with values < 0.05
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.0a4
Resolution Note (fix version 2021.1):
Fixed in 2021.1.4f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.7f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.28f1