Search Issue Tracker
Fixed in 2020.2
Fixed in 2019.4, 2020.1
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)
-
vanisi3667
Jul 02, 2020 04:47
thanks for sharing!
cheryl from https://www.siouxfallstreeservice.org
-
sam1212
Jul 01, 2020 04:52
<p><span style="font-weight: 400;">Thank you for sharing<a href="https://www.indplsartcenter.org/braffood2019">!</a></span></p>
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
- Modifying scoped registries in project manifest does not update Package Manager UI window
- Models change their position in scene after reporting them in 2019.4
- Texture 'Read/Write' option does not double the memory in Profiler
- Pixel perfect setting not applied immediately
- [PLM] Changing the Environment Volume Profile settings does not trigger a new bake
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