Search Issue Tracker
Won't Fix
Won't Fix in 2020.3.X
Votes
0
Found in
2020.3.34f1
Issue ID
UUM-2213
Regression
No
[Backport] The Material's shader is not fully set when switching the shader at runtime
How to reproduce:
1. Open the attached project "ShaderSystemIssue.zip"
2. Open the "SampleScene" Scene
3. Enter the Play mode
4. Select the "SCENE MANAGER" GameObject in the Hierarchy window
5. Press the "Swtich Shader" button in the Inspector window
Expected result: The Material of the "Cube" GameObject switches to "Lit"
Actual result: The Material of the "Cube" GameObject becomes transparent
Reproducible with: 2019.4.38f1, 2020.3.33f1, 2021.2.0a21, 2021.2.0b1
Not reproducible with: 2021.2.0b2, 2021.2.19f1, 2021.3.1f1, 2022.1.0a1, 2022.1.0f1, 2022.2.0a11
Note: Selecting the Material in the Inspector window fixes the issue
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2020.3.X):
There are no fixes planned for this Bug
Resolution Note (2020.3.X):
Cannot fix this issue as this fix requires multiple changes in graphics area.