Page 1 of 1

Feature Request: Proxies (just like a Redshift Proxy)

Posted: Thu Sep 12, 2024 1:10 pm
by Heerko
I would love to see a feature equivalent to Redshift Proxy implemented in Octane for C4D. From what I understand, this would first need to be developed in Octane Standalone before being available in the C4D plugin, which is why I’m making this feature request.

During my freelance work at a studio, we utilized a Redshift Proxy workflow where multiple artists worked on various scenes. For instance, we often had a model, like a pair of headphones, loaded as a proxy. When the client provided an updated CAD model or requested material changes, we only needed to update the master file and re-export/overwrite the proxy. All linked scene files would automatically reference the updated model when opened, saving time and ensuring consistency.

This functionality is incredibly powerful and would be a valuable addition to Octane's toolkit. It would streamline collaborative workflows and improve efficiency when dealing with frequent updates. I think Octane could greatly benefit from having a similar proxy system.

Re: Feature Request: Proxies (just like a Redshift Proxy)

Posted: Thu Sep 12, 2024 1:52 pm
by skientia
It has been requested and is still relevant.

This is how imported geo works in Octane Standalone by default and perhaps, a more developed USD could provide that standard "deferred /referenced" workflow à la Katana or Clarisse without the necessity to implement an actual proxy system.

The downside is that USD has been so far synonymous of uncertainty and unreliability across major programs and mainly shining at studios with in-house development.

Re: Feature Request: Proxies (just like a Redshift Proxy)

Posted: Fri Sep 13, 2024 3:07 pm
by J.C
Have you tried using Octane ORBX object or use built-in C4D Xref object?

Re: Feature Request: Proxies (just like a Redshift Proxy)

Posted: Mon Sep 16, 2024 3:52 pm
by frankmci
J.C wrote:Have you tried using Octane ORBX object or use built-in C4D Xref object?
I was about to bring up XRefs, too. They only work within C4D, but if you are not bouncing back and forth from Octane Render to C4D Plugin, they work pretty well. It takes some practice to get used to the loading/unloading/updating etc, and being aware of how you manipulate an embedded XRef vs the source file it points to, but it sure does make managing shared resources between users, project stages, and multiple scenes much less of a headache.