Search Issue Tracker
By Design
Votes
0
Found in
5.4.0f3
Issue ID
825982
Regression
No
Vector2.magnitude computed value is different on iOS than on Android/Windows
Repro steps :
1. Build & deploy user attached project to iOS device.
2. Notice console output where actual magnitude is different than expected.
It seems that Mathf.Sqrt() is also producing not consistent results between platforms.
Reproduced on: 5.3.5f1, 5.4.0f3, 5.5.0b1
RESOLUTION:
The precision of intermediate results is unspecified by the IEEE-754 standard. It can not be relied on.
For more reading, see http://docs.oracle.com/cd/E19957-01/806-3568/ncg_goldberg.html#3098
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