Search Issue Tracker
Fixed
Votes
0
Found in [Package]
8.3.1
Issue ID
1316809
Regression
Yes
[SRP] ScriptableRenderContext.DrawShadows does not take into account different ShadowDrawingSettings on second call
How to reproduce:
1. Open the user's attached "reign-srp-LTS.zip" project in 2020.2 or higher
2. Open the "Toon" Scene
3. Observe the shadows near the character in the Game view
Expected result: The character's shadows are drawn in the Game view
Actual result: The character's shadows are not drawn in the Game view
Reproducible with: 8.3.1 (2020.1.17f1), 10.3.1 (2020.2.6f1), 11.0.0 (2021.1.0b8), 12.0.0 (2021.2.0a6)
Not reproducible with: 7.5.3 (2019.4.21f1)
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:
This is actually a feature request for customizable scriptable culling, and we are not supporting this path at this point in time. This was not actually a regression, as it only seemed to work due to another bug that was fixed which was setting the shadow cull distance to the camera far plane when calling drawShadow with different culling results. The workflow for this at this point in time would be to use spotlights with orthographic projection with a matrix override for drawing the segmented shadow layers into different render textures.