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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
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.