By default, Unity GPU instances GameObjectsThe fundamental object in Unity scenes, which can represent characters, props, scenery, cameras, waypoints, and more. A GameObject’s functionality is defined by the Components attached to it. More info
See in Glossary with different Transforms in each instanced draw call. To add more variation to the instances, modify the shaderA program that runs on the GPU. More info
See in Glossary to add per-instance properties such as color. You can do this both in surface shadersA streamlined way of writing shaders for the Built-in Render Pipeline. More info
See in Glossary and in vertex/fragment shaders.
Custom shaders don’t need per-instance data, but they do require an instance ID because world matrices need one to function correctly. Surface shaders automatically set up an instance ID, but custom vertex and fragment shaders don’t. To set up the ID for custom vertex and fragment shaders, use UNITY_SETUP_INSTANCE_ID at the beginning of the shader. For an example of how to do this, see Vertex and fragment shader.
When you declare an instanced property, Unity gathers all the property values from the MaterialPropertyBlock objects set on GameObjects into a single draw call. For an example of how to use MaterialPropertyBlock objects to set per-instance data at runtime, see Changing per-instance data at runtime.
When adding per-instance data to multi-pass shaders, keep the following in mind:
When you use multiple per-instance properties, you don’t need to fill all of them in MaterialPropertyBlock
objects. Also, if one instance lacks a property, Unity takes the default value from the referenced material. If the material doesn’t have a default value for the property, Unity sets the value to 0. Don’t put non-instanced properties in the MaterialPropertyBlock
, because this disables instancing. Instead, create different materials for them.