Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.2.6f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1110556
Regression
No
[Bug] Material not drawn in Game View when changing shader from script until said material is selected in the Project Window
How to reproduce:
1. Open the project "case_1110556-NoDrawOnMaterialSwitch" and scene "CloudTests_v01"
2. Enter Play Mode
3. Select "CloudMaterial" In the Project Window
4. Observe Scene View and Game View
Expected result: square clouds visible in both Scene View and Game View before and after selecting the material
Actual result: square clouds visible in Scene View but not visible in Game View until the appropriate material is selected
Reproducible with: 2017.4.20f2, 2018.3.6f1, 2019.1.0b4, 2019.2.0a6
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
- The tag adder functionality does not work if a space is entered instead of a name
- Errors thrown in the Console when configuring In-App Purchases package
- Longer Scaler Profile names go out of the"Scaler Profilers" section
- AI Navigation window UI elements overlap when the AI Navigation window is docked and resized
- Editor freezes after some time when using NavMeshQuery::Raycast
Resolution Note (2020.2.X):
When assigning a new shader to a material, we have to reset the render queue on the material to ensure we're not overriding the shader render queue by default. The Standard Shader material inspector when opened assigns the render queue based on its settings (Render Mode). That's custom behaviour, and we cannot know on the engine side, what exactly controls the render queue on the material.
As a workaround, it's possible to assign the render mode in each modified material from script. This will ensure the correct render queue override is selected.