face_off wrote:There are no texturemap limits in Octane 2.01, so no need to display them.
This is very good news indeed.
This is the first time this feature has been requested. At the moment you can copy and paste proxy info via the 'C' and 'P' buttons on the Material tab (if the selection is a copy). If you want this functionality expanded, pls provide a very clear and detailed description of what you want and I can look at how it can be implemented.
What we need is the proxy to behave just as materials - since you configure a material as default, every time this material renders as specified into the plugin. This way, every instance of a determined object (rfa) will be converted to the specified proxy into the plugin, no need to manual copy or substitution. If the need to another similar, but not equal proxy conversion arises, a new "type" is created inside the Revit (or other bim), with all the info needed, including info about the proxy if needed too.
This is the most logical way to use a bim architecture. It's impossible to manually convert every one of 50.000 seats of a stadium, and the multiple copy isn't any better since the project is done inside the bim platform, not into the plugin. There are several bim automation tools not aware of what a rendering proxy is, or even that it exists.