Search Issue Tracker
Fixed in 2018.2.X
Fixed in 5.6.X, 2017.1.X, 2017.2.X, 2017.4.X, 2018.1.X
Votes
0
Found in
5.6.4f1
Issue ID
968997
Regression
No
Assertion failed: Shader Compiler Socket Exception when certain Shaders interact with each other
To reproduce:
1. Open the attached project;
2. Attempt to Build the project.
Expected result: Unity builds the project successfully, no shader compile errors were thrown (or meaningful errors were thrown)
Actual result: Build fails,
"Assertion failed: Shader compiler: internal error compiling shader snippet type=1 platform=1: Protocol error - failed to read correct magic number"
"Assertion failed: Shader Compiler Socket Exception: Terminating shader compiler process, 0 retries left" were thrown into the console.
Reproduced on versions: 5.5.6f1, 5.6.5f1, 2017.1.3f1, 2017.2.1p1.
Not reproduced on versions: 2017.3.0a1-2017.3.0a6.
Fixed on version: 2017.2.2p3, 2017.4.3f1.
DirectX9 is deprecated in 2017.3 - 2018.x versions
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment