Page 1 of 1

Camera position error when exporting OBJ

Posted: Wed Jun 20, 2012 8:44 pm
by skibbbi
Hi TIG,

I found a bug when exporting obj from sketchup to octane (file 1 and 2).
1 export obj.png
2 import mesh in octane.png
When I click "render frame" all is well (file 3).
3 render frame.png
Or maybe I'm doing something wrong?

Regards,

Re: Camera position error when exporting OBJ

Posted: Wed Jun 20, 2012 10:00 pm
by TIG
That's not a bug. :shock:

If you choose the dialog's 'Render Frame' it exports the OBJ File [with supporting MTL/texture-files etc] and then runs a 'cmd' file that uses that data in an Octane OCS - i.e. using whatever camera, shadows etc that you have set in the dialog. It is of course possible to do this with no camera set, so that the default Octane camera is then used.
If you choose the export the OBJ/MTL only etc only there is no render done: if you open this OBJ in an Octane OCS there is no camera data with it. An OBJ file contains' geometry info' and the MTL has the associated 'materials/textures' etc - there is no camera or shadow settings etc in these types of file - so you must either set these manually OR activate Octane via a 'cmd' file that passes suitable details to it as it runs.
Thus when you choose "Render Frame" from the dialog you pass whatever settings you have ticked from the SKP to the OCS - typically the camera.
BUT running an OCS on a 'raw' OBJ will have no built-in camera data at all...
Octane is not psychic.........

Re: Camera position error when exporting OBJ

Posted: Thu Jun 21, 2012 6:54 am
by skibbbi
Thank you for the clarification :D ,

Apparently I misunderstood the documentation (my English is not the best).
documentation of octane.png
After reading this I thought the only difference between the "Export OBJ / MTL Only" and "Render Frame" is the automatic start rendering.

I checked carefully and "Render Frame" actually generates additional file octane.cmd and there are camera settings.

Regards,