Search Issue Tracker
Fixed
Fixed in 2021.3.50f1, 2022.3.59f1, 6000.0.41f1, 6000.1.0b2
Votes
0
Found in
2021.3.46f1
2022.3.53f1
6000.0.27f1
6000.1.0a5
Issue ID
UUM-87636
Regression
No
Graphics.DrawMeshInstanced does not work when 2D Renderer and 2D Shaders are used
Reproduction steps:
1. Open the attached “DrawMeshInstancedTest.zip” project
2. Open the “SampleScene”
3. Enter the Play mode
4. Observe the Game view
Expected result: Two rows of 10 instanced quads are visible
Actual result: One row of 10 instanced quads is visible
Reproducible with: 2021.3.46f1, 2022.3.53f1, 6000.0.27f1, 6000.1.0a5
Reproducible on: Ubuntu 24.10, Windows 11
Not reproducible on: No other environment tested
Notes:
- The issue does not reproduce if ‘URP/Unlit’ Shader is used (That is the row of quads that gets rendered in the project), but that appears to be the only Shader that the issue does not reproduce with
- Also reproduces in the Player
- Enabling “Wireframe” mode in the Scene view shows that the geometry is not rendered
- Mesh Renderer with the Material works correctly, but not when used with DrawMeshInstanced
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note (fix version 6000.1.0b2):
Fix for this issue will be available on Unity 6000.1.0b2 and above