Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.8.15
Issue ID
BUR-2691
Regression
No
The Burst converted value differs from the value of the non-Burst conversion when converting the value from a float to a double
How to reproduce:
1. Open the “BurstConversion“ project
2. Open the “SampleScene“
3. Enter the Play Mode
4. Open the “Test“ GameObject in the Inspector
5. Observe the values of the “With Burst” and the “Without Burst“ properties
Expected result: There is no difference between the values of the “With Burst” and the “Without Burst“ properties
Actual result: The “With Burst“ property value is higher than the “Without Burst“ property value
Reproducible with: 1.8.14 (2021.3.38f1, 2022.3.30f1), 1.8.15 (2021.3.38f1, 2022.3.30f1, 6000.0.4f1)
Reproducible on: macOS 13.5.2 (Intel), Windows 11 (User's)
Not reproducible on: No other environments tested
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
- Entities are jittering when Temporal Anti-aliasing (TAA) is applied
- The drawing order of Transparent objects is incorrect when changing the Material from Opaque to Transparent with GPU Resident Drawer enabled
- Sprite animations do not update when Animator parameters change in the Player
- [iOS] Memory increases significantly when a TMP Text component has a lot of text
- [Linux][X11] Editor Graphics API can't be set to OpenGL when running on an Nvidia Optimus laptop, prime offload enabled, and while using X11
Resolution Note:
The difference is due to the Mono Runtime handling intermediate floating point calculations differently, as opposed to Burst or .NET Core, whose values are more precise.