Search Issue Tracker
Fixed in 2022.2.15f1
Fixed in 2022.2.X, 2023.1.X, 2023.1.0b1
Votes
0
Found in
2022.2.3f1
2023.1.0a26
Issue ID
UUM-24939
Regression
Yes
GameObjects aren't rendered in builds when "Cast Shadows" is disabled
How to reproduce:
1. Open the user attached project “StrictShaderVariantMatching.zip”
2. Open Scene “SampleScene“ (Assets/Scenes)
3. Run And Build (File>Build And Run)
Expected result: Cube GameObject is rendered in the build
Actual result: Cube GameObject isn’t rendered in the build
Reproducible with: 2022.1.0a7, 2022.2.3f1, 2023.1.0a26
Not reproducible with: 2020.3.44f1, 2021.3.17f1, 2022.1.0a6
Reproduced on: macOS 13.0.1 (Intel)
Note: The Cube GameObject is rendered if the Cast Shadows setting is enabled in the URP-HighFidelity.asset settings (Assets/Settings) under Lights, Additional lights
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
Add comment