Redshift Proxies allow you to place previously exported Redshift Proxy Files (.rs) files in your scenes without actually loading the geometry until it is actually needed at render time.
Using proxies has several advantages over in-scene objects, namely:
- Proxies are loaded by Redshift on demand and will therefore only use resources when they are needed (when a ray intersects the proxy's bounding box).
- Proxies have almost no time cost during scene translation. Extracting large amounts of geometry from Maya, 3ds Max Softimage can be slow and using proxies means you pay that cost only once when you export the Redshift Proxy File.
- Proxies are stored in an optimized format on disk so that the renderer can immediately use the data after loading from disk without additional processing or memory overhead.
The main disadvantages of using proxies:
- Making edits to the proxy can be more time consuming than if the original data is part of the scene (as it requires making changes in another file and re-exporting the Redshift Proxy File)
- Proxies cannot be deformed or otherwise modified. For example, you cannot animate components inside a proxy (but you can animate the position, rotation and scale of the proxy as a whole rigid object).
Note Previously Redshift proxies worked with pre-export Redshift Mesh files (.rsmesh). While powerful, the system was somewhat limited in that a .rsmesh file could contain only a single mesh. As of version 1.2.00, the proxy system has been completely re-written to support "Redshift Archives", generally referred to as Redshift Proxy Files. Unlike Redshift Mesh files (which are no longer supported), Redshift Proxy Files can contain any number of meshes. In fact, Redshift Proxy Files describe an entire scene and support object types including hair, strands, instances, volume containers, lights and any materials/shaders applied to these objects. A Redshift Proxy Files can even contain other proxies!
Redshift Proxies provide the option to use either the materials embedded in the Redshift Proxy File, or to replace those materials with materials from the scene where the proxy is placed.
Redshift Proxy File s are DCC-independent, so you can export a Redshift Proxy File from Maya and place it as a proxy in Softimage, or vice-versa, though there are currently some important limitations you should be aware of.
WARNINGThere are currently some important limitations in sharing Redshift Proxy Files between DCCs:The embedded shaders in a Redshift Proxy File from one DCC may not be available in another DCC. For example a Redshift Proxy File containing a Softimage Lambert material will not render correctly when placed as a proxy in Maya. Similarly certain light types native to a particular DCC may cause errors when rendered in another DCC. To avoid this issue, we recommend always using one of the From Scene material modes when sharing Redshift Proxy Files between DCCs until we resolve this limitation.
When working with Redshift Proxies, it is helpful to follow these guidelines:
- You cannot retrieve the original Maya, 3ds Max or Softimage mesh from a Redshift Proxy File, so it is generally advisable to keep the original source data that was used to export the Redshift Proxy.
- When placing multiple copies of a Redshift Proxy in a scene, it is much more efficient for memory and performance to create a single Redshift Proxy and then create multiple instances of this proxy and place them as desired.