Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.4.X
Votes
0
Found in
2018.4
2019.3
2019.3.3f1
2020.1
Issue ID
1251613
Regression
No
Shader compiler throwing internal communicating errors for UniversalForward, Fragment Program on particular shader compilation
How to reproduce:
1. Open user-submitted project (827425-ShaderCompilerRepro.zip)
2. Open the SampleScene
3. Select "CSR3_Env" in the Project window
4. Change something in the shader, or in one of its cginc files, to force a re-compilation
5. In the Inspector window, click on "Compile and Show Code"
Expected result: no errors are thrown in the Console window
Actual result:
Reproducible with: 2019.4.0f1, 2020.1.0a2
Not reproducible with: 2020.1.0a3, 2020.1.0b11, 2020.2.0a13
Could not test with: 2018.4.24f1(Shader incompatible)
Notes:
Not dependant on the URP package version
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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a3
Resolution Note (fix version 2019.4):
Fixed in 2019.4.10f1