Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2018.4
2020.2
2020.2.0a13
Issue ID
1252557
Regression
No
[Stats Window] URP Shadow casters count differs from Built-In RP shadow casters count when using the same settings
How to reproduce:
1. Download the attached "case_1088730-ShadowCascadeCulling.zip" project and open in Unity
2. Open "SampleScene" scene
3. Enter Play mode
4. Check Shadow casters count either in the Stats or the Frame Debugger
5. Switch to Built-in Pipeline by removing the Lightweight or URP Asset from Graphics settings
6. Change the "New Material" shader to "Standard" from "Universal Render Pipeline/Lit"
7. Check the Shadow casters count again in the Stats or the Frame Debugger
Expected results: the Shadow caster count should be the same as they have the same settings
Actual results: in the Built-In Pipeline there is a number of extra shadow caster draw calls (832 shadow casters) compared to LWRP/URP (0 shadow casters)
Reproducible with:
LWRP 4.10.0-preview (2018.4.23f1) (824 shadow casters instead of 832),
URP 7.0.1 (2020.1.0a11),
URP 8.1.0 (2019.3.16f1, 2020.1.0b11, 2020.2.0a13)
Could not test with: 2017.4 due to URP not being available
Note: reproducible on both OSX and Windows
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
Add comment