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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Group Selection title text size is smaller in renaming than the actual font size
- Rich Text is not correctly highlighted when searching through Debug Logs in the Console window
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
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.