Unity shaders are written in HLSL.
Unity supports the standard vertex, geometry, fragment shader pipeline.
They also have their own variation of fragment shaders called surface shaders which automatically handle lighting.
Compute shaders are useful for doing parallel computation on the GPU.
Results from compute shaders can be used on the graphical shaders without being copied back to the CPU.
To use a compute shader, add a
ComputeShader reference to your C# script.
To copy data to and from the GPU, use a
You can copy standard floats arrays as well as Unity Vector2, Vector3, and Vector4 structs.
All loading of streaming assets should be done in a background thread. See C# Multithreading for more details on multithreading.
I've found that Unity's job system doesn't perform as well as C#'s ThreadPool when stressed with thousands of small tasks so I recommend using C# APIs over Unity APIs whenever possible.
Ciela Spike's Thread Ninja may be used to run coroutines in the background when you only need a single, but complex, task.
Much of Unity's API such as
new Mesh() and
new Texture2D() cannot be called from background threads. I suggest caching textures as
Color32 which can then be loaded with
Texture2D.LoadRawImageData(). Similarly, you can cache a Mesh by caching a struct of vertices, triangles, normals, and tangents.
If you need multiple instances of the same object, make sure that the material is instanced so that all objects only consume one draw call.
See Unity: GPUInstancing.
Do not attach scripts to thousands of objects. Instead use one script on one object.
If you need thousands of simple objects, one way is to use a mesh with one vertex per object and expand them in the geometry shader.
You can use one compute shader to animate and move the objects instead of using Unity scripts. The compute shader edits a single compute buffer which can be read by your vertex or geometry shader.