How do you get something you've made in Rhino into Octane Standalone?

[Graham06]

This is a complete newbie question. The manual talks about exporters, but says nothing about where they can be found. The one I'm after might be called Rhino2Octane. A post from a few years back says they can be found in the licensed customer download area, but I can't find anything there.

Another useful question might be: where is the documentation that explains this?

Thanks,

Graham

[face_off]

Rhino2Octane is at http://render.otoy.com/forum/viewtopic.php?f=41&t=4231. Importing meshes is covered in the manual at http://render.otoy.com/manuals/Standalone/?page_id=246.

Paul

[newske]

Hi Graham,
There is one, but it's quite out of date and not maintained anymore. It may still work though, as Paul posted above.

I would recommend just doing things a bit more 'manually' and simply exporting to textured OBJ, and importing (with reference) into Octane. If there is camera data you want too, it's not difficult just to copy/type it in from Rhino.

[Graham06]

Thanks. I'll experiment with both methods.

[FanzunAG]

Hi,

I'd like to ask if there is a way to export .ocs files from Rhino including various rendertargets, geometry variations and material variations?
I'd like to batch render an interior scene that has, let's say, 3 different cameras set as well as 4 different geometry/material variatons. For batch/queue rendering itself I am using a Lua script found here in the forum for which works perfectly.
For the scene loading - so far I am able to export .ocs scene which includes everyting that is ON at the moment of export (camera position, layers and materials that are ON, etc.). I can do this manually for every single option and camera position (that's 12 ocs files) and then combine the nodes from different .ocs files into one. But that's a hell of a work I have to say. So I wonder if all this can be done in easier way - like exporting an .ocs with various Rendertargets and all the materials and layers in the scene (even the ones that are OFF at the moment). Or loading previously saved .xml file with Rendertarget settings into standalone?

[face_off]

I'd like to ask if there is a way to export .ocs files from Rhino including various rendertargets, geometry variations and material variations?
I'd like to batch render an interior scene that has, let's say, 3 different cameras set as well as 4 different geometry/material variatons. For batch/queue rendering itself I am using a Lua script found here in the forum for which works perfectly.
For the scene loading - so far I am able to export .ocs scene which includes everyting that is ON at the moment of export (camera position, layers and materials that are ON, etc.). I can do this manually for every single option and camera position (that's 12 ocs files) and then combine the nodes from different .ocs files into one. But that's a hell of a work I have to say. So I wonder if all this can be done in easier way - like exporting an .ocs with various Rendertargets and all the materials and layers in the scene (even the ones that are OFF at the moment). Or loading previously saved .xml file with Rendertarget settings into standalone?

Hi - are you using the OctaneRender for Rhino plugin to export to OCS, or Rhino2Octane?

Paul

[FanzunAG]

Hi Paul,

Perhaps the Octane for Rhino plugin itself (v1.5). Can't remember the other one installing, but I am quite not sure. How/where can I find out, actually?

[face_off]

Perhaps the Octane for Rhino plugin itself (v1.5). Can't remember the other one installing, but I am quite not sure. How/where can I find out, actually?

Hi - I'm sorry - I'm still not clear on what tools you are using to export to OCS from Rhino. Can you post a screenshot pls? If you are using the OctaneRender for Rhino plugin, the "release number" is on the Activation tab.

Paul

[FanzunAG]

Hi Paul,

Here's a screenshot of my Octane plugin in Rhino. I am exporting my models to .ocs by right clicking inside settings tab and choosing "Export Scene to OCS", so perhaps I am using the plugin itself to export.

[face_off]

Hi - thanks for the screenshot.

To answer your original question....

I'd like to ask if there is a way to export .ocs files from Rhino including various rendertargets, geometry variations and material variations?
I'd like to batch render an interior scene that has, let's say, 3 different cameras set as well as 4 different geometry/material variatons. For batch/queue rendering itself I am using a Lua script found here in the forum for which works perfectly.
For the scene loading - so far I am able to export .ocs scene which includes everyting that is ON at the moment of export (camera position, layers and materials that are ON, etc.). I can do this manually for every single option and camera position (that's 12 ocs files) and then combine the nodes from different .ocs files into one. But that's a hell of a work I have to say. So I wonder if all this can be done in easier way - like exporting an .ocs with various Rendertargets and all the materials and layers in the scene (even the ones that are OFF at the moment). Or loading previously saved .xml file with Rendertarget settings into standalone?

I see what you are after - however I don't think there is an easy way to export 3 camera positions from the current version of the plugin. The two options I see are 1) use LUA in Octane Standalone to merge the different OCS files (unsure how easy this would be), or 2) Use Rhino script to automate the process of exporting each OCS file. At the moment saving to OCS is not available as a Rhino command, but I could easily add it....but it would be in the Octane 2.0 version of the plugin.

So in summary - this is possible, but not straightforward.

Paul