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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.