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
- Switching a Type QueryBlock to prefabs fails
- Search Index Manager allows deleting Empty Index List when clicking on “-“ button, throwing “ArgumentOutOfRangeException” error in the Console window
- "System.ArgumentOutOfRangeException" error is thrown when baking Adaptive Probe Volumes
- Project Directory is opened when Opening the Editor Log from the Console Window and the Editor is launched with the -nolog argument
- "vector<bool> too long" error is thrown when using UnityYAMLMerge
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