Search Issue Tracker
Fixed in 8.1.0
Votes
0
Found in [Package]
7.1.8
Issue ID
1217043
Regression
No
[ShaderGraph][Mac] shader with keywords causes shader compiler errors
How to reproduce:
1. Open the attached project
2. Re-import "KeywordTest" shader
3. Check the console
Reproducible with: 2019.3.2f1 (7.1.8), 2020.1.0a24 (7.2.1).
Actual result: A lot of "internal error communicating with the shader compiler process" errors appears. (Full errors in edit)
Expected result: The shader graph compiles.
Notes:
- Removing any property and saving the shadergraph resolves the bug.
- Can't test ShaderGraph 6.9.2 and lower because the faulty shader graph fails to deserialise.
- Reproduces if you do this with handwritten (non - shader graph) shaders.
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
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
Resolution Note (fix version 8.1.0):
verified
Version: 2020.2.0a19.2490
Shader Graph 8.1.0
Resolution Note:
Verified fixed on
Version 2019.4.6f1 (a7aea80e3716) Personal
Tue, 21 Jul 2020 18:49:45 GMT
Branch: 2019.4/staging
SRP Package version 7.3.1