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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment