Search Issue Tracker
Duplicate
Votes
0
Found in
2018.4.0f1
2019.2.0a1
2019.3.0a1
2019.3.0b3
2020.1.0a1
Issue ID
1186441
Regression
No
Mesh is not rendered in the start location when using DrawMeshInstancedIndirect function
How to reproduce:
1. Open the attached project ("case_1186441-Project.zip")
2. Open the SampleScene from the Scenes folder
3. Enter the Play mode
Expected result: Two cubes are rendered in the Game View.
Actual result: Only the cube on the left side is rendered.
Reproduced in: 2018.4.10f1, 2019.2.7f2, 2019.3.0b5, 2020.1.0a7
Couldn't test with: 2017.4 (The project breaks)
Notes:
1. Not reproduced with Vulkan and Metal Graphics API
2. when using OpenGL on macOS the Editor throws a "Kernel 'SetIndirectArgs' not found" error
-
Resolution Note:
By-design that DirectX11 does not support "start instance location" for DrawMeshInstancedIndirect.
From the docs page for D3D11:
https://msdn.microsoft.com/en-us/library/windows/desktop/ff476410(v=vs.85).aspx"A value added to each index before reading per-instance data from a vertex buffer."
Note that this means the offset is applied to the Index, not to SV_InstancedID.
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
- URP Cascaded Shadows do not have a falloff in Player when the Player is built not in Development Mode
- Grid in animation preview window is rendered on top of the object
- WebGPU Graphics.RenderPrimitives fails on MeshTopology.Quads with Validation errors when exceeding 64k vertices
- Task status is "WaitingForActivation" when awaiting a faulted task inside that task
- 0 is returned when any output from Split Node is input into the Lerp Node
This is a duplicate of issue #940273