Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0a19
Issue ID
627427
Regression
No
Implicit byte to int conversion doesn't work as expected in webGl
For example:
byte c1 = 1;
int c3 = c1 << 8, // c3 = 256 in Editor, but is 0 in WebGL build
int c4 = 1 << 8; // c4 = 256 both in Editor and WebGL
Mono 2.10 and 3.4 return 256 in both cases.
Only happens with logical operators, int a = byte(255) + 1; seems to work fine.
To reproduce:
1. Attach the attached 'Uint2Test.cs'
2. Build to webGL & play compare the output in editor and browser.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment