Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.1.X, 2020.2.X
Votes
0
Found in
2018.4
2020.2
Issue ID
1276366
Regression
No
[Shaders] Compute shader preprocessor warnings and errors don't get forwarded to the Console Window
Reproduction steps:
1) Create a ComputeShader asset
2) Add line "#pragma exclude_renderers asdfasdf0" to the source of the asset (the code)
Reproducible with: 2018.4.27f1, 2019.3.0a1, 2019.4.10f1, 2020.1.5f1, 2020.2.0b2
Expected Result: a warning about bad pragma arguments in the Console Window similar to what you would get by putting the same line in a graphics shader
Actual Result: no warning about malformed pragma syntax in the Console Window
Note: the example of how the Compute Shader code could look is in "SCRCMPT.png" below
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 2021.1):
Fixed in 2021.1.0a1.495
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b7.3288
Resolution Note (fix version 2020.1):
Fixed in 2020.1.10f1.4666