Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0b6
Issue ID
914313
Regression
No
Shaders: shader compiler crashes on a specific 'if' statement with values used from vertex input
To reproduce:
1. Create a new project
2. Import attached shader
Expected: there will be no errors
Actual: 'Internal error communicating with the shader compiler process' error is thrown
Note: when in 'if' statement in lines 50-52 number '2' is replaced by lower number(at least 1.9999), error disappears
Reproducible on any 5.5, 5.6, 2017.1.0, 2017.2.0a1
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
- NullReferenceException when setting 'isTextObjectScaleStatic' to false on a disabled TextMeshPro GameObject
- Shader Stripping Custom Options disappear when exiting Play mode without reloading Domain
- Decals do not get projected when 'Rendering Layer Mask' on a GameObject is 23rd Layer or above due to encoding/decoding issues
- Deriving from SearchContextAttribute doesn't always work
- Scripting API documentation is missing for macOS editor extensions
Resolution Note:
Unfortunately, this is a Microsoft FXC.exe (shader compiler) internal bug, we won't fix that.