Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2018.4.X, 2019.4.X, 2020.3.X
Votes
0
Found in
2018.4
2020.2.0b2
2021.1
Issue ID
1289378
Regression
No
Internal error communicating with the shader compiler process when SV_PrimitiveID is the only Input signature
How to reproduce:
1. Open attached "ShaderTest.zip" project
2. Set Graphics API to OpenGLCore
3. Select TestShader asset
4. In the Inspector, select Compile and show code
5. Observe the errors in the Inspector and Console window
Expected result: No errors appear
Actual result: Error "Internal error communicating with the shader compiler process" appears
Reproducible with: 2018.4.29f1, 2019.4.15f1, 2020.1.14f1, 2020.2.0b12, 2021.1.0a7(OpenGLES3, OpenGLCore, Vulkan)
Not reproducible with: 2018.4.29f1, 2019.4.15f1, 2020.1.14f1, 2021.1.0a7(OpenGLES2, Direct3D11)
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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.0a8
Resolution Note (fix version 2020.3):
Fixed in 2020.3.5f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.28f1
Resolution Note (fix version 2018.4):
Fixed in: 2018.4.36f1