Search Issue Tracker
Fixed in 2022.2.9f1
Fixed in 2021.3.20f1
Votes
4
Found in
2021.3.17f1
Issue ID
UUM-23329
Regression
Yes
GameObjects aren't rendered in the Player when the Material Shader is created with a ShaderGraph
How to reproduce:
1. Open the user's attached "ShaderStrip" project
2. Build and Run
Expected result: Both Cubes are rendered in the Player
Actual result: Only the left-side Cube is rendered
Reproducible with: 12.1.3 (2021.2.8f1), 12.1.4 (2021.2.11f1)
Not reproducible with: 7.7.1 (2019.4.35f1), 10.8.1 (2020.3.28f1), 12.0.0 - 12.1.2 (2021.2.7f1, 2022.1.0a1), 13.1.5 (2022.1.0b7), 14.0.0 (2022.2.0a4)
Note: Couldn't test with Built-In and HDRP Active Targets as the project fails to build due to Shader compilation errors
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 (fix version 2022.2.9f1):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-25112
Resolution Note (fix version 2021.3.20f1):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-25112