Search Issue Tracker
Fixed
Votes
0
Found in
5.0.0f4
Issue ID
678032
Regression
Yes
Mathf.FloorToInt behavior changed in Unity 5
Mathf.FloorToInt bahavior changed from 4.6 to 5.0.
In 5.0:
When the floating point value gets close to int.MaxValue or greater, the return value goes massively negative then tends towards zero.
In 4.6:
It just stays massively negative: -2147483648.
There's attached script "script.cs", which depending on Unity version (4.6 or 5.0) gives different value on 'more' public variable. Just drag it to any object in new scene and enter play mode to see it.
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
Add comment