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
- Video Player glitches when Skip On Drop is enabled
- GameObject movement in Scene view becomes stuttery and intermittently freezes when using non-standard pointers across editor tabs or window boundaries
- Addressables.CheckForCatalogUpdates() always returns 0 when "Only update catalogs manually" is enabled
- VFX Graph forces a lengthy recompilation freeze when exiting Play Mode with a cloned Render Pipeline asset
- Project Auditor's "Install Rules" button has to be pressed twice to proceed when any compilation error in the Editor is present
Add comment