Search Issue Tracker
By Design
Votes
3
Found in
2018.4
2018.4.18f1
2020.2
Issue ID
1229758
Regression
No
[Shadows] Shadows don't appear in the built Player with a specific project when Development Build option is disabled
How to reproduce:
1. Open the uploaded project's "case_1229758-Project.zip" Scene labeled "MainScene"
2. Enter the Play Mode
3. Observe the shadow cast by the Cube GameObject
4. Build the project (with "Development Build" option disabled)
5. Open the Player
6. Observe the Cube GameObject
Expected result: Shadow is cast by the Cube
Actual result: Shadow is not cast by the Cube
Reproducible with: 2018.4.21f1, 2019.3.9f1, 2020.1.0b5, 2020.2.0a7
Couldn't test with: 2017.4.39f1 (Freeze while building the project)
Notes:
- Reproduced once in the legacy RP (didn't happen anymore);
- Not reproducible in URP and HDRP.
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 (2020.2.X):
Realtime shadow issues that reproduce only in Built-in RP and are not regressions, will not be fixed.
If the bug has no workaround and is blocking your production, please feel free to reopen it with any additional information you might have. Sorry for the inconvenience this might cause.