Thank you for helping us improve the quality of Unity Documentation. Although we cannot accept all submissions, we do read each suggested change from our users and will make updates where applicable.
CloseFor some reason your suggested change could not be submitted. Please <a>try again</a> in a few minutes. And thank you for taking the time to help us improve the quality of Unity Documentation.
Closematrix | Transformation matrix to use. |
material | Material to use. |
shaderPass | Which pass of the shader to use (or -1 for all passes). |
topology | Topology of the procedural geometry. |
properties | Additional material properties to apply just before rendering. See MaterialPropertyBlock. |
bufferWithArgs | Buffer with draw arguments. |
argsOffset | Byte offset where in the buffer the draw arguments are. |
Add a "draw procedural geometry" command.
When the command buffer executes, this will do a draw call on the GPU, without any vertex or index buffers.
The amount of geometry to draw is read from a ComputeBuffer. Typical use case is generating an arbitrary amount of data from a ComputeShader and then rendering that, without requiring a readback to the CPU.
This is only useful on Shader Model 4.5 level hardware where shaders can read arbitrary data from ComputeBuffer buffers.
Buffer with arguments, bufferWithArgs
, has to have four integer numbers at given argsOffset
offset:
vertex count per instance, instance count, start vertex location, and start instance location.
This maps to Direct3D11 DrawInstancedIndirect and equivalent functions on other graphics APIs. On OpenGL versions before 4.2 and all OpenGL ES versions that support indirect draw, the last argument is reserved and therefore must be zero.
In the vertex shader, you'd typically use SV_VertexID and SV_InstanceID input variables to fetch data from some buffers.
Additional resources: DrawProcedural, MaterialPropertyBlock, Graphics.DrawProceduralIndirect, ComputeBuffer.CopyCount, SystemInfo.supportsComputeShaders.
indexBuffer | Index buffer used to submit vertices to the GPU. |
matrix | Transformation matrix to use. |
material | Material to use. |
shaderPass | Which pass of the shader to use (or -1 for all passes). |
topology | Topology of the procedural geometry. |
bufferWithArgs | Buffer with draw arguments. |
argsOffset | Byte offset where in the buffer the draw arguments are. |
properties | Additional material properties to apply just before rendering. See MaterialPropertyBlock. |
Add a "draw procedural geometry" command.
When the command buffer executes, this will do a draw call on the GPU, without a vertex buffer.
The amount of geometry to draw is read from a ComputeBuffer. Typical use case is generating an arbitrary amount of data from a ComputeShader and then rendering that, without requiring a readback to the CPU.
This is only useful on Shader Model 4.5 level hardware where shaders can read arbitrary data from ComputeBuffer buffers.
Buffer with arguments, bufferWithArgs
, has to have five integer numbers at given argsOffset
offset:
index count per instance, instance count, start index location, base vertex location, and start instance location.
This maps to Direct3D11 DrawIndexedInstancedIndirect and equivalent functions on other graphics APIs. On OpenGL versions before 4.2 and all OpenGL ES versions that support indirect draw, the last argument is reserved and therefore must be zero.
In the vertex shader, you'd typically use SV_VertexID and SV_InstanceID input variables to fetch data from some buffers.
Additional resources: DrawProcedural, MaterialPropertyBlock, Graphics.DrawProceduralIndirect, ComputeBuffer.CopyCount, SystemInfo.supportsComputeShaders.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.