Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.1.0b1
2019.1.0f2
2019.2.0a1
Issue ID
1147325
Regression
No
[Shaders] ShaderUtil.ShaderHasError returns false when Shader has errors
How to reproduce:
1. Open the user's attached project ("ShaderErrorBug.zip")
2. Call menu Bugs/Reproduce Bug
3. See "False" log in the console (the result of ShaderHasError call)
4. Select ShaderWithError shader in the Project tab
5. Call menu Bugs/Reproduce Bug again
6. See True in the console (the result of ShaderHasError call)
Expected results: "ShaderHasError" method returns "True" without manual Shader selection when shader has errors
Actual results: "ShaderHasError" method returns "False" unless the Shader which has errors is selected
Reproducible with: 2019.1.0f2, 2019.2.0a13
Couldn't test 2017.4, 2018.3 and up to 2019.1.0b1 because of missing "ShaderHasErros" method
Notes:
1. After the Shader was selected once, "ShaderHasErrors" will work as expected, until the Editor is re-opened or all assets are re-imported
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
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
Resolution Note (fix version 2019.3):
Fixed in 2019.3.0a5