material | 使用する Material |
bounds | The bounding volume surrounding the instances you intend to draw. |
topology | プロシージャルジオメトリのトポロジー |
camera | If null (default), the mesh will be drawn in all cameras. Otherwise it will be rendered in the given Camera only. |
bufferWithArgs | Draw Arguments のバッファ |
argsOffset | Draw argument があるバッファのバイトオフセット |
properties | このメッシュを描画する前にマテリアルに適用するマテリアルプロパティーを追加します。 MaterialPropertyBlock を参照してください。 |
castShadows | Determines whether the mesh can cast shadows. |
receiveShadows | Determines whether the mesh can receive shadows. |
layer | 使用する Layer |
Draws procedural geometry on the GPU.
This function is now obsolete. For non-indexed rendering, use RenderPrimitivesIndirect instead.
For indexed rendering, use RenderPrimitivesIndexedIndirect.
This function only works on platforms that support compute shaders.
DrawProceduralIndirect does a draw call on the GPU, without any vertex or index buffers. If the shader requires vertex buffers one of the following occurs depending on platform: If the vertex buffer is declared but compiler can optimize it away then the normal DrawProcedural call will occur. If the compiler is not able to optimize the vertex buffer declaration away then this will be converted into a normal mesh drawing call with emulated vertexbuffers injected. The latter option has performance overhead so it is recommended not to declare vertex inputs in shaders when using DrawProceduralIndirect.
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 mainly 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.
There's also similar functionality in CommandBuffers, see CommandBuffer.DrawProceduralIndirect.
Additional resources: Graphics.RenderPrimitivesIndirect, Graphics.RenderPrimitivesIndexedIndirect, Graphics.DrawProcedural, ComputeBuffer.CopyCount, SystemInfo.supportsComputeShaders.
material | 使用する Material |
bounds | The bounding volume surrounding the instances you intend to draw. |
topology | プロシージャルジオメトリのトポロジー |
indexBuffer | Index buffer used to submit vertices to the GPU. |
camera | If null (default), the mesh will be drawn in all cameras. Otherwise it will be rendered in the given Camera only. |
bufferWithArgs | Draw Arguments のバッファ |
argsOffset | Draw argument があるバッファのバイトオフセット |
properties | このメッシュを描画する前にマテリアルに適用するマテリアルプロパティーを追加します。 MaterialPropertyBlock を参照してください。 |
castShadows | Determines whether the mesh can cast shadows. |
receiveShadows | Determines whether the mesh can receive shadows. |
layer | 使用する Layer |
Draws procedural geometry on the GPU.
DrawProceduralIndirect does 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 mainly 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.
There's also similar functionality in CommandBuffers, see CommandBuffer.DrawProceduralIndirect.
Additional resources: Graphics.DrawProcedural, 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.