Search Issue Tracker
In Progress
In Progress in 1.8.X
Votes
0
Found in [Package]
1.8.27
Issue ID
BUR-2932
Regression
No
Mathematics hash function returns different results when compiled with Burst and Mono
How to reproduce:
1. Open attached project "IN-124637"
2. In the menu bar click on "Test/Burst Compiled"
3. In the menu bar click on "Test/No Burst Compiled"
4. Observe Console
Expected result: Result is the same across both methods
Actual result: Results are different
Reproducible with: 1.2.6 (2023.1.0a3), 1.3.3 (6000.0.62f1, 6000.2.13f1, 6000.3.0f1, 6000.4.0a5, 6000.5.0a1)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- passing more than one parameter into "f()" results in expected behavior
- issue reproduces with hash(uint3), hash(int3), hash(float3)
- issue does not reproduce with hash(uint2), hash(uint4), hash(int2) hash(int4), hash(float2), hash(float4), hash(bool3), no other methods tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Add comment