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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
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