Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2020.3
2021.2
2022.1
2022.2
Issue ID
1410859
Regression
No
Mathf.Sign returns 1 when input is 0
To reproduce:
1. Create a new Unity project
2. Debug log the return value of Mathf.Sign(0)
3. Observe console window
Reproducible with: 2019.4, 2020.3, 2021.2, 2022.1, 2022.2
Expected result: Returns 0
Actual result: Returns 1
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:
Unfortunately that is not something we can change: that would be a major breaking change for existing code.
Documentation aligns with the current behaviour: Mathf.Sign returns 1 for 0 or any positive value, -1 for a negative value.