Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2020.3.X, 2021.3.X, 2022.1.X
Votes
0
Found in
2020.3
2021.2
2021.2.10f1
2022.1
2022.2
Issue ID
1402454
Regression
No
Shader Compiler errors are thrown due to unexpected reasons related to the Shader script
How to reproduce:
1. Open the user's attached "Bug_report_project" project
2. Compile the "Assets -> UpscaleShader" Shader
Expected result: The Shader is successfully compiled. No error is thrown
Actual result: Shader compiler errors are thrown in the Console log. In some versions, only "Unterminated macro list" error is thrown instead
Reproducible with: 2019.4.36f1, 2020.3.30f1, 2021.2.13f1, 2022.1.0b9, 2022.2.0a5
Thrown errors:
Shader Compiler IPC Exception: Terminating shader compiler process
Shader compiler: Compile SHADER_NAME - <Unnamed Pass>, Vertex Program: Internal error communicating with the shader compiler process. Please report a bug including this shader and the editor log.
Shader compiler: Compile SHADER_NAME- <Unnamed Pass>, Fragment Program: 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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a10
Resolution Note (fix version 2022.1):
Fixed in 2022.1.1f1
Resolution Note (fix version 2021.3):
Fixed in 2021.3.2f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.35f1