Search Issue Tracker
Fixed in 14.0.3
Votes
0
Found in [Package]
14.0.3
Issue ID
1421660
Regression
No
Shadow casters can't be SRP-batched when they have different UnityPerMaterial values
Reproduction steps:
1. Open the attached project "ShaderGraphSRPBatcher.zip"
2. Enter Play mode
3. Open the Frame Debugger window and enable it
4. Select either of the two "ShadowLoopNewBatcher.Draw" draw calls under "HDRenderPipline::Render Main Camera/ExecuteRenderGraph/RenderShadowMaps"
Expected result: The draws are batched
Actual result: The draws are not batched, a message is displayed:
"Why this draw call can't be batched with the previous one
Objects either have different shadow caster shaders, or have different shader properties / keywords that affect the output of the shadow caster pass"
Reproducible with: 10.9.0 (2020.3.35f1), 12.1.7 (2021.3.4f1), 13.1.8 (2022.1.3f1), 14.0.3 (2022.2.0a15)
Could not test with: 7.7.1 (2019.4.39f1) (Broken assets when downgrading/remaking project)
Reproducible on: macOS 12.0.1 (Intel)
Note: In 2022.2.0a15 the second line of the message is under Batch Cause
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Resolution Note (fix version 14.0.3):
Fixed in: 2022.2.0a16 (HDRP 14.0.3)