Textures and samplers aren’t separate objects in Unity, so to use them in compute shadersA program that runs on the GPU. More info
See in Glossary you must follow one of the following Unity-specific rules:
Use the same name as the Texture name, with sampler
at the beginning (for example, Texture2D MyTex
; SamplerState samplerMyTex
). In this case, the sampler is initialized to that Texture’s filter/wrap/aniso settings.
Use a predefined sampler. For this, the name has to have Linear
or Point
(for filter mode) and Clamp
or Repeat
(for wrap mode). For example, SamplerState MyLinearClampSampler
creates a sampler that has Linear filter mode and Clamp wrap mode.
For more information, see documentation on Sampler States.
You can use keywords to produce multiple variants of compute shaders, the same as you can for graphics shaders.
For general information on variants, see Shader variantsA verion of a shader program that Unity generates according to a specific combination of shader keywords and their status. A Shader object can contain multiple shader variants. More info
See in Glossary. For information on how to implement these features in compute shaders, see Declaring and using shader keywords in HLSL and the ComputeShader API documentation.
Usually, compute shader files are written in HLSL, and compiled or translated into all necessary platforms automatically. However, it is possible to either prevent translation to other languages (that is, only keep HLSL platforms), or to write GLSL compute code manually.
The following information only applies to HLSL-only or GLSL-only compute shaders, not cross-platform builds. This is because this information can result in compute shader source being excluded from some platforms.
Compute shader source surrounded by CGPROGRAM
and ENDCG
keywords is not processed for non-HLSL platforms.
Compute shader source surrounded by GLSLPROGRAM
and ENDGLSL
keywords is treated as GLSL source, and emitted verbatim. This only works when targeting OpenGL or GLSL platforms. You should also note that while automatically translated shaders follow HLSL data layout on buffers, manually written GLSL shaders follow GLSL layout rules.
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.