Search Issue Tracker
Won't Fix
Won't Fix in 1.8.X
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
- After converting a Built-in project to URP render texture related errors are spammed that can lead to Game view being rendered on top of Scene view
- UI Builder slider value lags and stutters when sliding/modifying certain property values
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
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.
Resolution Note (1.8.X):
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.