Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.3f1
Issue ID
1048601
Regression
No
[Profiler] Graphics.DrawMeshInstancedIndirect rendering info cannot be collected in Profiler window
To reproduce:
1. Download attached project "DrawInstanceIndirect.zip" and open in Unity
2. Open "1" scene
3. Enter Play mode
4. Open Profiler window
Expected results: In Rendering part, there will be all Instancing info collected
Actual results: In Rendering part, there will be no Instancing info collected
Notes:
- This issue appears both on Windows and OSX
- It seems that Draw call, triangles, and vertices info can't be collected when using Graphics.DrawMeshInstancedIndirect to draw objects
Reproduced on Unity 2017.1.4p1, 2017.2.3p1, 2017.3.2f1, 20174.5f1, 2018.1.5f1, 2018.2.0b8 and 2018.3.0a1
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (2018.3.X):
We didn't count any stats for "indirect" draw because indirect means the data (number of primitives & instances count) is generally generated by the GPU. So we don't want to stall the GPU to read back data from GPU to CPU.