Search Issue Tracker
Fixed in 2021.3.7f1
Fixed in 2021.3.X, 2022.2.X, 2023.1.X, 2023.1.0a3
Votes
0
Found in
2021.3.4f1
2022.2.0a17
2023.1.0a1
Issue ID
UUM-4336
Regression
No
Draw calls that batch in opaque pass do not batch in shadow pass when some of the draw calls come from SkinnedMeshRenderer and some come from MeshRenderer
Reproduction steps:
1. Open the user’s attached “1239248-SRP_Batching.zip“ project
2. Open the Frame Debugger window (Window > Analysis > Frame Debugger)
3. Click Enable
4. Compare the amount of calls in “MainLightShadow > Shadows.DrawSRPBatcher” and “DrawOpaqueObjects > RenderLoop.DrawSRPBatcher”
Expected result: Both have the same amount of calls
Actual result: “MainLightShadow > Shadows.DrawSRPBatcher“ has 2 calls, while “DrawOpaqueObjects > RenderLoop.DrawSRPBatcher” has only 1
Reproduced with: 10.9.0 (2020.3.35f1), 12.1.7 (2021.3.4f1), 13.1.8 (2022.1.4f1), 14.0.3 (2022.2.0a16)
Reproduced on: macOS Monterey 12.0.1 (Intel)
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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Resolution Note (fix version 2023.1):
Fixed in 2023.1.0a3
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0b1