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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #940273