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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.