Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
0
Found in
2018.4
2019.3.9f1
2020.2
Issue ID
1242162
Regression
No
An internal error is thrown when using CBUFFER in a custom Shader
How to reproduce:
1. Open the attached project
2. In the Project Window, select the "Leaves" Shader Asset
3. Observe the Console Window
Expected result: No errors are thrown
Actual result: "Internal error communicating with the shader compiler process" error is thrown
Reproducible with: 2018.4.24f1, 2019.4.2f1, 2020.1.0b14, 2020.2.0a17
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
- VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
- Operations on the Color32 array are not reflected in WebGL Player when HDR is off
- Rigidbody moves away from the original GameObject when Center of Mass is set in every frame
- WebGL Player does not proceed beyond logo screen when "Target WebAssembly 2023" is enabled
- "NullReferenceException" error thrown in UnityEditor.ObjectListArea when an audio clip is selected in one of two opened Project tabs while the second Project tab is not active/painted
Resolution Note (fix version 2020.2):
Fixed in Unity 2020.2.0a19
Resolution Note (fix version 2020.1):
Fixed in Unity 2020.1.0f1
Resolution Note (fix version 2019.4):
Verified fixed in
Version 2019.4.6f1 (a7aea80e3716) Personal
Tue, 21 Jul 2020 18:49:45 GMT
Branch: 2019.4/staging
The shader now displays the correct compilation error, in this case multiple declarations of CBUFFER
Resolution Note (fix version 2018.4):
Fixed in Unity 2018.4.26f1