Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.3
2019.3.1f1
2020.1
2020.2
Issue ID
1250058
Regression
No
[FXC Crash] Shader Compiler internal error thrown when reimporting shader using Centroid Interpolator
Reproduction steps:
1. Open attached project "1250058"
2. In the Project folder, right-click on "case_1250058-ffCrash" and reimport it.
Expected result: No errors are thrown
Actual result: 3 errors are thrown
Reproducible with: 2018.4.23f1, 2019.3.15f1, 2020.1.0b10, 2020.2.0a13
Errors thrown:
Shader Compiler Socket Exception: Terminating shader compiler process
Shader compiler: Compile ffShader/ffWire - <Unnamed Pass>, Fragment Program: Internal error communicating with the shader compiler process. Please report a bug including this shader and the editor log.
Shader error in 'ffShader/ffWire': Internal error communicating with the shader compiler process. Please report a bug including this shader and the editor log.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2020.2.X):
Changing "float3 Normal : TEXCOORD1_centroid;" to a proper HLSL construct "noperspective centroid float3 Normal : TEXCOORD1;" or "linear centroid float3 Normal : TEXCOORD1;" makes the crash go away.
The crash happens in FXC, so there's nothing we can do about it.