Search Issue Tracker
By Design
Votes
1
Found in
2019.4
2020.3
2020.3.22f1
2021.2
2022.1
Issue ID
1381896
Regression
No
Float to Int conversion returns unexpected/differential results when adding a second conversion to float in the equation
How to reproduce:
1. Open the attached project "Floatinconsistent.zip"
2. Open "SampleScene" Scene
3. Enter Play mode
Expected result: the results displayed in the Console window are 70, 70, 70
Actual result: the results displayed in the Console window are 70, 69, 70
Reproducible with: 2019.4.33f1, 2020.3.23f1, 2021.2.4f1, 2022.1.0a16
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
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
Resolution Note (2022.2.X):
The difference in output values is an implementation details in floating point operations within the VM. Note that .NET Core and .NET Framework also yield different results. If a "rounding" behavior is expected, please use Math[f].Round as the behavior of casting to floating point to integer is truncation.