I think it will be different for each user. IMO the fastest workflow is to do 100% of the modelling first, then apply Rhino materials to the geometry, then open the plugin (which will assign Octane materials to all the Rhino materials) to render in Octane. Then the Rhino Viewport materials will match the Octane Viewport. You really need to do your modelling in the Rhino viewport - since the Octane viewport does not support the modelling process.Thanks for the reply -- I'm honestly open to using this however it was intended, It's just different than other plugin's so I'm trying to understand it. Is your opinion and intention that the "rendered viewport" in Rhino should be not used, and for us to use the Octane Render window only instead? Just wondering what workflow you reccomend?
Correct - that is described in the manual http://render.otoy.com/manuals/Rhino/?page_id=85.Also, correct me if I'm wrong, but is the intended process, to create a Rhino Material, name it, assign it to geometry, and then tweak the Octane material settings from that point forward?
You can build a library of Rhino/Octane materials. Name the rhino material (say "Leather"), save it, assign it to some geometry, edit the Octane material to tweak (or load Leather from the LiveDb), "Save as Default". Then whenever you load and assign the Rhino "Leather" material, the saved default Octane material will be used. If you need to tweak Octane Leather for a particular scene, that tweaked Octane version will be saved in the Rhino file, and will not change the default version (unless you Save as Default).
The plugin currently supports someone building a large library of Rhino materials, and corresponding Octane materials and distributing them for others' use.
Paul
