Search Issue Tracker
Fixed in 0.4.2-38
Votes
0
Found in [Package]
0.2.4-27
Issue ID
1101466
Regression
No
Unity burst compiler produces incorrect result when converting constant uint to ulong
To reproduce:
1) Open attached project and sample scene
2) Play it
In the center, a value for "ulong value = uint.MaxValue;" is shown
Expected (Burst Jobs disabled): 4294967295
Actual (Enabled): 18446744073709551615
-
nobare
May 11, 2019 06:59
Unity burst are going to compile the all details to produce the incorrect result it was when converting constant unit was ulong on this. You have to know how this was possible just read article on https://telstraeduaustralia.com/ozessay-com-au-review it has the all information that was available on this site having the all access on this.
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
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Resolution Note (fix version 0.4.2-38):
Fixed in Burst 0.4.2-38