Search Issue Tracker
Fixed in 1.4.4
Votes
0
Found in [Package]
1.4.1
Issue ID
1292528
Regression
No
Burst package throws compile errors when building a script with multiple conditional statements if they use Color32
How to reproduce:
1. Open the attached "1292528.zip" project
2. Build and run the project
3. Notice the compile errors in the console after the build
Expected result: Burst compiles the code without errors
Actual result: Burst fails to compile code and throws errors in the console
Reproducible with: 1.1.1, 1.4.1 (2018.4.29f1, 2019.4.15f1, 2020.1.14f, 2020.2.0b13, 2021.1.0a8)
Could not test with: 0.2.4-preview.5 (2021.1.0a8) (some Burst features not available)
Note:
- There needs to be a Color32 variable in the "If" statement condition for Burst to fail
- If the script has any 2 of the 3 "If" statements removed the compilation happens without errors
- Build fails using both MONO and IL2CPP mode
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.4.4):
Fix has been released with burst version 1.4.4