Masoud Posted March 6 Share Posted March 6 Hi guys, I would like to create a Redshift Proxy from my object (which contains multiple components) and load it into Solaris, with the goal of assigning materials to each component individually. The issue I'm encountering is that in Solaris, the proxy is displayed as a single mesh, which prevents me from assigning materials to the individual components. At the SOP level, I used the "Redshift Proxy Output" SOP, and in Solaris, I applied the "Redshift Proxy" LOP. How can I fix this? Thanks for helping. Redshift Proxy to Solaris_01.hip Quote Link to comment Share on other sites More sharing options...
Earller Posted July 3 Share Posted July 3 The issue likely stems from how the proxy is exported — it’s being treated as a single mesh without preserving per-component hierarchy. To fix this: In SOPs, ensure each component has a unique path or name attribute (use Name SOP or Attribute Create). In the Redshift Proxy Output SOP, disable "Export as Packed Primitives" to avoid flattening the geometry. In Solaris, when using the Redshift Proxy LOP, set it to "Load as Reference" and confirm that hierarchy is preserved in the Scene Graph Tree. Each component should appear as a separate prim. Once you have separate prims, use Material Library LOP and Material Assign LOP to assign materials to individual components. If the proxy continues to load as a single mesh, consider exporting as USD with proper hierarchy and assigning Redshift materials directly in Solaris for more flexibility. Hope this helps! forward proxy Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.