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
- Assert error is thrown when the Editor language is set to one of the experimental ones in an HDRP project
- A BatchDrawCommand is using a pass from the shader “Universal Render Pipeline/Particles/Lit” that is not SRP Batcher compatible
- The Scene does not get rendered in the Player when MSAA is enabled and more than one Camera is used
- Crash on mono_object_get_class when generating Font Atlas of a specific font file
- GPU usage doubles when a project is running in the background
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a3
Resolution Note (fix version 2019.4):
Fixed in 2019.4.10f1