Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.3.0a1
2019.3.13f1
2020.1
2020.2
Issue ID
1248017
Regression
Yes
ShaderUtil.GetAllShaderInfo() function doesn't return errors from Surface shader functions
How to reproduce:
1. Open the user's attached project
2. Go to Assets -> Shaders in the Project window
3. Select the Foo asset and observe the Inspector
4. Open Test Runner (Window -> General -> Test Runner)
5. Hit Run All and observe the Console log
Expected result: "Shader 'Custom/Foo' has errors." message printed
Actual result: No error messages printed
Reproducible with: 2019.3.0a1, 2019.3.14f1, 2020.1.0b9, 2020.2.0a11
Not reproducible with: 2018.4.23f1, 2019.2.21f1
Could not test with: 2017.4.40f1 (ShaderUtil.GetAllShaderInfo() function is not present)
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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a13
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0b12
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.1f1