Table Of Contents
The Proxy File Objects
The plugin supports export and render Redshift proxy object files, that can also be instanced using instancing or point clouds. The proxy objects supports animated sequences, and the plugin has a custom SOP nodes to preview them in the viewports. The proxy options are available in the OBJ spare parameters, but the plugin has an icon in the shelf to add an empty proxy OBJ container, ready to be used with the preview SOP node inside.
You can save the proxy files enabling the export function in the ROP node and rendering the frame or sequence. By default the not used attributes are discarded, but there is an option to disable this behavior in case you are exporting proxy objects with dummy materials.
The “instancefile” Attribute
The plugin can use the “instancefile” point attribute to instance Redshift proxy objects. If this attribute is available, the object will be extracted as a instancer using the file path pointed by the “instancefile” attribute string to load the proxy objects at render time. Like any other instancing object, using the RS OBJ spare parameters, the “instancefile” proxy instancing can be configured to be extracted using Redshift Instances or Redshift Point Clouds.
Using the same spare parameters of the instancer object, the proxy visibility, matte and tessellation options can be overridden. Enable the “Enable Proxy File” option to expose the proxy override controls, leaving the “Proxy Filename” field empty. Currently the materials override feature is not supported while working with the “instancefile” feature.
Using the Redshift Proxy SOP Node
The proxy SOP is used only to display in the viewports the Redshift proxy object files. Any OBJ node can be used as placeholder for a proxy object using the options available in the RS OBJ spare parameters, that you can add using the icon in the shelf. Also in the shelf there is a tool to add a full proxy OBJ node with the spare parameters and the SOP node inside, ready to be used.