Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2021.2
2021.2.4f1
2022.1
2022.2
Issue ID
1387749
Regression
No
Shaders with Fallback defined are rendered pink when used with CommandBuffer
How to reproduce:
1. Open the user's attached project "CommandBuffer_bug.zip"
2. Open the "Bug" Scene in "_GAME_" > "Scenes"
3. In the Hierarchy window select the "Sprite" Object
4. In its Inspector window in Component "Bug (Script)" change Material to "Shader Graph material"
5. Press Play
Expected result: Object is rendered with the selected ShaderGraph material
Actual result: Object is displayed as a pink square
Reproducible with: 2019.4.35f1, 2020.3.27f1, 2021.2.10f1, 2022.1.0b6, 2022.2.0a3
Notes:
- Any Shader that has Fallback defined with CommandBuffer uses this Fallback Shader instead of what was created/written
- Disabling (Fallback Off) or removing Fallback from the Shader code renders the Object correctly
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note (2022.2.X):
Thanks for your freedback. Unfortunately, ShaderGraph currently does not support CommandBuffers. Any success anyone may have had with them in the past is a bit of a coincidence. You could peruse our product board and request the feature more explicitly here; https://portal.productboard.com/unity/1-unity-platform-rendering-visual-effects/tabs/7-shader-graph.