Search Issue Tracker
Not Reproducible
Votes
0
Found in
2019.1.0a1
2019.1.0b1
2019.2.0a1
Issue ID
1122291
Regression
No
[Custom SRP] CommandBuffer.DrawMeshInstancedIndirect does not draw Mesh when Graphics API is set to Direct3D11
To reproduce:
1. Open attached project
2. Open IndirectRenderingTest Scene
3. Change API from Direct3D11 to Vulkan and see that there are no mesh
4. Change API from Vulkan to Direct3D11 and see that mesh appears
Reproducible with: 2019.1.0b1, 2019.2.0a3
Not compatible with 2017.4 and 2018.3
Actual results: mesh isn't drawn
Notes: works with Direct3D12
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
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
- Files in the target folder are deleted without a proper warning when building an iOS project
- Character animation freezes when toggling animator on/off in a coroutine
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
Resolution Note (2019.2.X):
CommandBuffer.DrawMeshInstancedIndirect need to use ComputeBuffer with type IndirectArguments