Search Issue Tracker
By Design
By Design in 2023.1.X
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
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.
Resolution Note (2023.1.X):
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.