Page 1 of 1

ies lights import

Posted: Sat Aug 13, 2011 1:37 pm
by paulm
Hi Octane,

I am a newbie to the demo, trying to figure out a workflow from Rhino.
I can see how to get objects and materials accross with obj/mtl.

But can lights be imported?
I can write a script to the command line format to give a camera and sun locations.
For lights, one way would be to script an export for a colour, transform and ies file representing the light.
Is there any way to import that information into Octane?

Also, in the command line section of the manual does the presence of these parameters:
--cam-motion-pos-z <float> Camera Motion 2nd Position Z Component
mean that Octane supports camera motion blur?

PaulM

Re: ies lights import

Posted: Sat Aug 13, 2011 3:48 pm
by Refracty
There is a Rhino Exporter for licensed customers by Sam. Texture and Material Information is transfered but no lights.
You could write an exporter that transfers Light info into and .ocs file wich you could import.
Octane supports camera motion blur.

Re: ies lights import

Posted: Sun Aug 14, 2011 1:05 am
by paulm
Thanks Refracty,
Is there a specification somewhere for the .ocs file format?
Paul

Re: ies lights import

Posted: Mon Aug 15, 2011 12:55 am
by radiance
paulm wrote:Thanks Refracty,
Is there a specification somewhere for the .ocs file format?
Paul
Hi, OCS is an internal representation file format that is not documented, nor meant to be implemented, as it changes regularly.
Lights are imported from host apps as emission on a material, as a material property.
Sunlight positions are transfered via command line arguments in our current version, but this will soon change.

Radiance