Instances
Introduction
Instances are lightweight copies of an object that do not contain any geometry data, but rather maintain a link to the original object. Because each instance only stores a limited amount of data – such as a transform matrix and sometimes material assignment information – they have several advantages over regular copies:
- Instances use much less disk space for scene files.
- Edits to the original are automatically applied to all of its instances, making editing many identical objects much simpler.
- Instances use very little memory when rendering using Redshift and can significantly improve performance.
A scene with 1300 instances of a high resolution Buddha model (approximately 880,000 triangles per instance). Over a billion instanced triangles.
How To Use
Redshift for Houdini can render instanced geometry using the powerful Redshift native instancing or point clouds features.
|
Parameters
Instance Using
Controls whether it's using the instance object type or point clouds
Instances/Particles Motion Blur
- Compute sub-frame geometry (deformation): Use deformation motion blur, use for curved motion blur but uses more memory
- Use point velocity attribute: Use transformation motion blur
Lights Instancing
- Attributes support individual shaders: Light shaders comes from user attributes and can support different shaders per-light
- Using a common shared shader: Light shader comes from the referenced light, all lights use the same shader
'instancefile' Mode
- Instance Redshift Proxy Objects: Use when loading Redshift proxy files
- Instance Houdini Compatible Objects: Use when loading houdini BGEO files
Ignore Pivot Point Attribute
When enabled the Pivot Point attribute is ignored which can be helpful for controlling instance placement.
Override 'instancefile' Proxy Materials From Scene Materials
When enabled, a material in the instance file can be overwritten with a directly applied material.
Process 'instance' and 'instancefile' Attrs. Inside Packed Primitives
When enabled, Redshift uses the "instance" or "instancefile" point attributes to render instances inside packed objects. This requires the packed primitive to be expanded which can result in longer render times.
Instance SOP Level Packed Primitives
When enabled, packed primitives can be instanced at the SOP level, like when using a Copy SOP.
Instance Subnets
When enabled, it allows you to instance an entire subnet without the need to merge the object. Making it easier to instance complex objects with multiple parts.
Instance Procedural Packed Alembics
When enabled this allows for the instancing of procedural packed alembics.
Note, the alembic procedural must still be installed properly and Procedural Alembics must first be enabled in the Redshift ROP. For more information, see the Alembic Procedural page.