Geometry instancing

Starting in Direct3D version 9, Microsoft included support for geometry instancing. This method improves the potential runtime performance of rendering instanced geometry by explicitly allowing multiple copies of a mesh to be rendered sequentially by specifying the differentiating parameters for each in a separate stream. The same functionality is available in Vulkan core, and the OpenGL core in versions 3.1 and up but may be accessed in some earlier implementations using the EXT_draw_instanced extension.

Geometry instancing in Houdini, Maya or other 3D packages usually involves mapping a static or pre-animated object or geometry to particles or arbitrary points in space, which can then be rendered by almost any offline renderer. Geometry instancing in offline rendering is useful for creating things like swarms of insects, in which each one can be detailed, but still behaves in a realistic way that does not have to be determined by the animator. Most packages allow variation of the material or material parameters on a per instance basis, which helps ensure that instances do not appear to be exact copies of each other. In Houdini, many object level attributes (e.g. such as scale) can also be varied on a per instance basis. Because instancing geometry in most 3D packages only references the original object, file sizes are kept very small and changing the original changes all of the instances.

In many offline renderers, such as Pixar's PhotoRealistic RenderMan, instancing is achieved by using delayed load render procedurals to only load geometry when the bucket containing the instance is actually being rendered. This means that the geometry for all the instances does not have to be in memory at once.

• GeForce 6000 and up (NV40 GPU or later)
• ATI Radeon 9500 and up (R300 GPU or later).
• PowerVR SGX535 and up (found in Apple iPhone 3GS and later)[1]

• EXT_draw_instanced documentation
• A quick overview on D3D9 instancing on MSDN
• VkVertexInputRate specifies vertex or instance rate