Page 1 of 1

ORC & C4DOctane

Posted: Thu Jun 04, 2015 8:15 pm
by brasco
Hi Ahmet,

Since ORC has been opened up to the rest of us I figured it'd be a good idea to start a thread about how the workflow goes.
I realise some stuff is up to OTOY to implement/fix but I'm talking about the C4D Octane side of things.

The biggest deal-breaker so far is that the C4D Camera is lost on ORBX packaging. I've tried going the OCS route and that also loses the camera. Anything I need to do with the scene to get it to work?

cheers
brasc

Re: ORC & C4DOctane

Posted: Thu Jun 04, 2015 8:39 pm
by aoktar
brasco wrote:Hi Ahmet,

Since ORC has been opened up to the rest of us I figured it'd be a good idea to start a thread about how the workflow goes.
I realise some stuff is up to OTOY to implement/fix but I'm talking about the C4D Octane side of things.

The biggest deal-breaker so far is that the C4D Camera is lost on ORBX packaging. I've tried going the OCS route and that also loses the camera. Anything I need to do with the scene to get it to work?

cheers
brasc
Hi, i found what's the mistake. If you export an animated orbx and open that, find abc element and connect camera output to render target's camera input. But plugin has some issues for exports. Can't export arealight's materials. Also don't export material animations. It's that what i could found in my tryouts. I'll try to improve it more.

Re: ORC & C4DOctane

Posted: Thu Jun 04, 2015 8:56 pm
by brasco
Thanks Ahmet,

That's great for now to get it to work, I'll test it out and see.

cheers
brasc

Re: ORC & C4DOctane

Posted: Mon Jun 08, 2015 4:05 pm
by xcaseyx
it doesn't export textures if they are image sequences either. Its very promising though.

if the exporter worked, animated textures were supported, and you didnt have to relink everything in standalone, Id see this being a reason to save money on GPU's. Can't wait to see the pricing structure.