OTOY Forums

I know i've asked this before, but is there any smart ways of keeping cameras set ut in cinema when exporting orbx to render on ORC? And as I often use Cinemas Stage object to render several angles - this is quite needed to take advantage of ORCs full potential.

martincarlson wrote:I know i've asked this before, but is there any smart ways of keeping cameras set ut in cinema when exporting orbx to render on ORC? And as I often use Cinemas Stage object to render several angles - this is quite needed to take advantage of ORCs full potential.

I think that not possible yet through export commands. I can take a look for next versions

Awesome!

Ahmed,
please could you explain what exactly is happening when exporting an ORBX from C4D?
What kind of data is stored into the ORBX file?
Why is the GPU working while exporting a file?

Thank you

Ron

Ron wrote:Ahmed,
please could you explain what exactly is happening when exporting an ORBX from C4D?
What kind of data is stored into the ORBX file?
Why is the GPU working while exporting a file?

Thank you

Ron

There is two system to export:
1- We export as how plugin build a octane scene. As you can this when you call "Edit in Standalone". This support single frame.
2- We use a internal exporter. It supports animations. In this method resulting octane scene is little different. Meshes are collecting to a internal package(similar to alembic). You can't edit this conten from SA, etc.. But you can just read in SA. Also an Orbx can hold any kind data. Geometry, materials, light meshes, textures, animations, etc..

We don't use gpu on export. But we are using Octane core to translate to Octane scene. If you say the message in status bar, that's working very similar to standard export in LV.

aoktar wrote: There is two system to export:
1- We export as how plugin build a octane scene. As you can this when you call "Edit in Standalone". This support single frame.
2- We use a internal exporter. It supports animations. In this method resulting octane scene is little different. Meshes are collecting to a internal package(similar to alembic). You can't edit this conten from SA, etc.. But you can just read in SA. Also an Orbx can hold any kind data. Geometry, materials, light meshes, textures, animations, etc..

We don't use gpu on export. But we are using Octane core to translate to Octane scene. If you say the message in status bar, that's working very similar to standard export in LV.

Thanks for the very quick response!
Exporting animations takes a decent amount of time with bigger scenes. Could those be rendered on OCR and if so: are all used plugins translated somehow into the ORBX file?

Ron wrote: Thanks for the very quick response!
Exporting animations takes a decent amount of time with bigger scenes. Could those be rendered on OCR and if so: are all used plugins translated somehow into the ORBX file?

Yes, most likely. I haven't tried very big scenes but even with smaller scenes are generating really big orbx files. Also not logical to be faster than doing a direct rendering in plugins. Because you are doing very much file writing operation. I don't know all other plugins, but some of them can do this. Orbx is a general packaging format to hold Octane scenes.

Also, animation export is not complete. It's not supporting material animations, also can't export arealight materials. It's not a old feature and hadn't found much time to complete. Also some of features are not so simple to implement.

aoktar wrote:
Yes, most likely. I haven't tried very big scenes but even with smaller scenes are generating really big orbx files. Also not logical to be faster than doing a direct rendering in plugins. Because you are doing very much file writing operation. I don't know all other plugins, but some of them can do this. Orbx is a general packaging format to hold Octane scenes.

Also, animation export is not complete. It's not supporting material animations, also can't export arealight materials. It's not a old feature and hadn't found much time to complete. Also some of features are not so simple to implement.

Even if its not in final stage atm it's great and I am sure it will become a good solution.
Thank you very much for doing all that great work for the Octane/C4D community!
Just being curious: are you working as a one man show or having a development team around you?

Last one off-topic: the new node editor is so cool - I really, really appreciate it.

Ron

Thanks for appreciation. I'm one and also Dobs helps for tutorials. Separately we should thanks to Marcus, Thomas and other guys from Otoy. We couldn't have this renderer without their efforts.

Btw, I'm still working on the node editor to improve more. I'll publish a few next versions until make it much better.