Page 13 of 21
Re: Beta 2.2 RC1: Blender Export Script testing thread
Posted: Thu Jun 03, 2010 10:40 am
by ROUBAL
@Enricocerica : Hi, I already reported it in a previous post with detailed explanations :
I know how the selection is supposed to work, the problem is that it doesn't work in the last release of the script : 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.
Results depend of the way selection is done : using selected object doesn't work. Not using hidden objects works.
Re: Beta 2.2 RC1: Blender Export Script testing thread
Posted: Thu Jun 03, 2010 3:55 pm
by enricocerica
@Roubal:Ok thanks, i'll check that deeply and will be back with additional information or will release fixes if required. Don't remember if you are using Windows or Linux ?
Re: Beta 2.2 RC1: Blender Export Script testing thread
Posted: Thu Jun 03, 2010 4:23 pm
by ROUBAL
Thanks, I use Windows XP Pro 32 bits.
Re: Beta 2.2 RC1: Blender Export Script testing thread
Posted: Thu Jun 03, 2010 4:58 pm
by enricocerica
ROUBAL wrote:@Enricocerica : Hi, I already reported it in a previous post with detailed explanations :
I know how the selection is supposed to work, the problem is that it doesn't work in the last release of the script : 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.
Results depend of the way selection is done : using selected object doesn't work. Not using hidden objects works.
Hi Roubal,
5 - Export open Octane and display directly the scene, not allowing to select the GPUs before clicking on the Mesh node.
Yeah indeed, we should probably add a switch to control that over the script for single frame rendering.
For the other problems, it's very strange
I made several tests with a small scene and didn't get any issue. I export with selection only and it works, I export with remove hidden and it works. I crashed octane by activating the selection only but without anything selected, so I probably should add a control over that otherwise I can't reproduce any of the mentioned problem, I'm using Windows 64 bits, duno if it makes a difference. I'll try to make some more tests with a more complicated scene later on.
Hi everybody, does anybody else met some of those reported issues ?
Re: Beta 2.2 RC1: Blender Export Script testing thread
Posted: Thu Jun 03, 2010 5:09 pm
by ROUBAL
Small scenes worked fine. I encountered the problems with a scene around 290 MB if I remember well. Maybe it's a memory amount problem. I don't remember if I tried with only the 260GTX to get less cores, but more memory... I will try.
Re: Beta 2.2 RC1: Blender Export Script testing thread
Posted: Sun Jun 20, 2010 8:13 am
by lechu
Hi, I've wondered if someone else have faced this kind of problem. When I export my scene to Octane and then set up materials in node editor, next time (after saving an octane file) when I reload the scene from Blender, it has material node relinked from my mesh node and displays an C++ something like error. Good thing is that I can simply link them by hand and still render the scene, but when doing an animation, I have to repeat it every time my frame gets exported... Is there any sollution for this?
The scripts works great in any other manner

(maybe except of dof, but it can be fixed).
Re: Beta 2.2 RC1: Blender Export Script testing thread
Posted: Sun Jun 20, 2010 5:22 pm
by geo_n
Is it possible to export from blender but once octane opens up it renders in path tracing mode?
I have an animation scene blender that I want to render in octane in path tracing. Thanks.
Re: Beta 2.2 RC1: Blender Export Script testing thread
Posted: Sun Jun 20, 2010 6:58 pm
by mib2berlin
Hi geo_n, render a single frame, make your settings and save it to .ocs; close octane.
Then go back to blender and start your animation.
Cheers mib
Re: Beta 2.2 RC1: Blender Export Script testing thread
Posted: Mon Jun 21, 2010 8:57 am
by geo_n
mib2berlin wrote:Hi geo_n, render a single frame, make your settings and save it to .ocs; close octane.
Then go back to blender and start your animation.
Cheers mib
Thanks that worked.

Re: Beta 2.2 RC1: Blender Export Script testing thread
Posted: Thu Jul 01, 2010 10:26 pm
by GeoPappas
I just downloaded the Blender script for the first time, installed it into the Blender scripts directory, and tried to run it.
Unfortunately, I am getting the following error:
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "C:\Program Files\Blender 2.49b\.blender\scripts\octane_exporter.py", lin
e 55, in <module>
import os, subprocess
ImportError: No module named os
Anyone know how to solve this?