Search Issue Tracker
By Design
Votes
0
Found in
2020.3.40f1
2021.3.11f1
2022.1.20f1
2022.2.0b11
2023.1.0a14
Issue ID
UUM-19273
Regression
No
Incorrect float to int conversion when using Explicit Typecasting
Reproduction steps:
# Open the attached project (“FloatToIntBug.zip“)
# Open the Scene “Assets/Scenes/SampleScene“
# Enter the Play Mode
# Observe Console Window
Expected result: Multiplication 28300*0.04 is equal to 1132
Actual result: The shown answer is 1131
Reproducible with: 2020.3.40f1, 2021.3.11f1, 2022.1.20f1, 2022.2.0b11, 2023.1.0a14
Reproducible on: Windows 11
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note:
This behavior matches existing .Net Framework 4.8 behavior. There is a compiler change that injects a cast to float in .Net 6+ prior to performing multiplication with a float which prevents the truncation that is observed.