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
- Tile Paint action disappears from Undo History when Tile Selection tool has been used beforehand
- The pregenerated LightDefinition.cs.hlsl does not match the source LightDefinition.cs when regenerating shader includes
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
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.