Beta 2.2 RC1: Blender 2.49 Export Script testing thread

[face]

How can I set daylight and path trace mode and multi-gpu?

Path trace and daylight only in Octane.
Do it and save the scene.
After that you can export the light as the sun.
GPU under "GPU Devices to use"
eg. "0 1 2 3 4 5 6 7" without the "

face

[YoonKyung]

How can I set daylight and path trace mode and multi-gpu?

Path trace and daylight only in Octane.
Do it and save the scene.
After that you can export the light as the sun.
GPU under "GPU Devices to use"
eg. "0 1 2 3 4 5 6 7" without the "

face

Thank you ..

By the way, how can I set daylight and path trace mode, if I want to render animation?

[face]

Use the Project Configuration.
Select the Octane binary and click on Use existing project.
With that you can load your saved Octane scenefile.
The script will use that and it will then loaded into Octane with your saved settings.

face

[YoonKyung]

Use the Project Configuration.
Select the Octane binary and click on Use existing project.
With that you can load your saved Octane scenefile.
The script will use that and it will then loaded into Octane with your saved settings.

face

Thank you ..

[saikafu]

sorry..when the script support the 2.2 release?

the current script supports 1.0 beta2.2

Radiance

really!???
but i can't export file with this script
my os is win7
ps:the message is --> space in octane binary path !

[radiance]

sorry..when the script support the 2.2 release?

the current script supports 1.0 beta2.2

Radiance

really!???
but i can't export file with this script
my os is win7
ps:the message is --> space in octane binary path !

hi,

enrico has just told me he's fixing this and will post a new version of the blender script later today.

Radiance

[saikafu]

radiance:
ok~~thanks

[enricocerica]

New script version available, see top of the thread

[ROUBAL]

Hi, I report this here as well as in the Octane section, because I don't know if there arean exporter problems or Octane bugs : When rendering from the Blender Export script, for the same settings events are happening at random :
1 - Export open Octane and display a runtime error.
2 - Export open and close Octane without creating the ocs file.
3 - Export, open Octane and puts the Mesh node and the Preview nodes on a different layer, not allowing to interconnect them !
4 - Export open and close Octane after creating the ocs file, requiring Manual reopening and reloading ocs.
5 - Export open Octane and display directly the scene, not allowing to select the GPUs before clicking on the Mesh node.
6 - Export, Open Octane and do nothing more (not loading scene).

So far, I have been able to export an render correctly only a very small animation with 3 cubes, a lamp and a ground plane. With last version of the exporter and Octane 1.022 b2.2 RC2 I had rendered a 50 frames scene with a detailed animated character.

I also noticed that there is a Typo in the script on a Button : Written Eport instead of Export...

About the script, I also have a request (It may also require some modifications in Octane) :

The ability to render all frames of an animations as a serie of OBJ files, without rendering.

This would require from Octane the ability of relinking automatically the next obj after rendering a frame, but would allow to separate export and rendering process,and for example do the export (that may be very long) on a machine, while rendering or preparing materials on the machine where Octane is installed. It would also allow export one day and render the day after or during thenight,for example. For animations of heavy scenes, the export time per frame is very long, and the current workflow alternating exporting and rendering is not practical at all in my opinion.

Thanks in advance !

Philippe.

[Faizol]

The ability to render all frames of an animations as a serie of OBJ files, without rendering.

This would require from Octane the ability of relinking automatically the next obj after rendering a frame, but would allow to separate export and rendering process,and for example do the export (that may be very long) on a machine, while rendering or preparing materials on the machine where Octane is installed. It would also allow export one day and render the day after or during thenight,for example. For animations of heavy scenes, the export time per frame is very long, and the current workflow alternating exporting and rendering is not practical at all in my opinion.

Thanks in advance !

Philippe.

This is readily available in Blender. Check obj export menu. However if you're using Blender 2.5, the mesh is not updated for the next frame which resulted in the initial mesh exported again and again for the whole frame range selected for export. The workaround is to update a mesh for the frame, then export it out. This can easily be scripted out via python.

As per relinking the next obj in Octane, a batch rendering script can be written out for the whole export with all the parameters.