Search Issue Tracker
Duplicate
Votes
0
Found in
5.5.0b9
Issue ID
845517
Regression
No
DrawMeshInstanced always draws the first submesh and ignores submeshIndex
Reproduction steps:
1. Open the attached project (New Unity Project 1.zip)
2. Open the "scene.unity" scene.
3. Enter the play mode
4. Observe the objects which are drawn to the right.
Note: the blue object is drawn by the Graphics.DrawMesh method, the red object is drawn by Graphics.DrawMeshInstanced
Expected result: The red object is drawn the same way as the blue object.
Actual result: The part of the red object is not drawn.
Reproduced on: 5.5.0b4, 5.5.0b5, 5.5.0b9, 5.5.0b10 and 5.6.0a1
Note: The method Graphics.DrawMeshInstanced was not implemented on the older version than 5.5, so the bug can be observed only on this version.
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
This is a duplicate of issue #845514