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.
CloseDefault ComputeBuffer type (structured buffer).
In HLSL shaders, this maps to StructuredBuffer<T>
or RWStructuredBuffer<T>
.
When you construct a ComputeBuffer of this type, the value of stride
must match the stride of the corresponding StructuredBuffer
struct type in your HLSL code.
The value of stride
must also be a multiple of 4, and less than 2048.
To meet requirements on some platforms and avoid performance issues, stride
should be a multiple of 16. Use float4 and float4x4 variables to create a multiple of 16, and put smaller variables inside them. Avoid the use of 'padding' variables to create a multiple of 16, for example using a float3 variable to pad a struct containing a single float, because some data types may be different sizes on different platforms.
If you use a mix of variable sizes, the data layout of a shader's structured buffer may be different depending on the graphics API. This means ComputeShader.SetBuffer or Material.SetBuffer might overwrite data or set variables to the wrong values. See Writing shaders for different graphics APIs for more information.
See Microsoft's HLSL documentation on StructuredBuffer and RWStructuredBuffer.
Additional resources: ComputeBuffer, ComputeShader, Material.SetBuffer.
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.