Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.2
2019.2.11f1
2019.3
2020.1
Issue ID
1197326
Regression
Yes
[Vulkan] Using DrawMeshInstanced draws only one Mesh and then throws maximum instance count reached error
Reproduction steps:
1. Open the attached project named Case_1197326
2. Open the instancing Scene
3. Observe the Spheres in the Scene
4. Change the Graphics API used by the project to Vulkan
5. Observe the Spheres again
Expected result: The number of rendered spheres matches(Screenshot_1197326_V1)
Actual result: The number of spheres rendered does not match when using Vulkan(Screenshot_1197326_V2)
Reproducible with: 2018.4.13f1, 2019.2.15f1, 2019.3.0f1, 2020.1.0a14
Not reproducible with: 2017.4.35f1
Could not test with: 2020.1.0a15(project crashing due to another issue)
Notes:
- Does not reproduce on Direct3D11, Direct3D12, OpenGLCore and Metal
- Inspecting the mesh render process using a Frame Debugger displays the following error: "The previous instanced draw call has reached its maximum instance count"
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
- The cursor moves into wrong place when renaming folder/asset
- Assertion error "(dx - width < padding) || (dy - height < padding)" when using Pack Preview
- [Memory Profiler] The EntryType.NativeAllocationSites_MemoryLabelIndex of snapshots only reports -1 or 0 instead of the MemLabel used for allocations made from any call site.
- [Vulkan] Artifacts appear in the Player when using Screen Space shadows with orthographic camera
- Errors OnGUIDepth changed & GUIUtility:ProcessEvent when opening Textures with Third Party App
Resolution Note (2020.1.X):
After investigating the project attached to the bug report, it was found that the shaders use SV_InstanceID-semantics directly. This kind of usage is currently not supported.