Search Issue Tracker
By Design
Votes
0
Found in
2021.3.35f1
2022.3.20f1
2023.2.12f1
2023.3.0b9
Issue ID
UUM-64587
Regression
No
Sprite Renderer not rendering duplicated GameObject grey when using MaterialPropertyBlock
Reproduction steps:
1. Open the “TempProject.zip”
2. Open the Frame Debugger window (Window > Analysis > Frame Debugger)
3. Enter Play mode and Enable the Frame Debugger
4. Observe the Game window of the 3rd frame and Draw Dynamic event in the Frame Debugger window (Camera.Render > Drawing > Render.TransparentGeometry > RenderForward.RenderLoopJob > Draw Dynamic)
Expected result: Both trees are rendered gray and there’s nothing of note in the Frame Debugger window
Actual result: Only one of the trees is rendered gray and “Why this draw call can’t be batched with the previous one
Objects have different MaterialPropertyBlock set.” message is shown in the Frame Debugger window
Reproducible with: 2021.3.35f1, 2022.3.20f1, 2023.2.12f1, 2023.3.0b9
Reproduced on: macOS Sonoma 14.3 (Intel), Windows 11 (22H2), macOS 13.2.1 (M2) (by user)
Notes:
- Also reproducible in Player
- If the issue does not reproduce restart the Editor
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
If different set of values are set in the MaterialPropertyBlock, it will break batching even if the same object is being to call SetPropertyBlock. This is By Design.