Beta 2.2 RC1: Blender 2.49 Export Script testing thread

[enricocerica]

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?

Have you installed the Python 2.6 ( http://www.python.org/download/ ) or are you using the basic library provided with Blender ?

[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?

Have you installed the Python 2.6 ( http://www.python.org/download/ ) or are you using the basic library provided with Blender ?

I was using the basic library that was included with Blender 2.49b. I figured out that I needed to install Python to get rid of the error, but now I have run into another problem - I am getting the error about spaces in the project path. I can't really change the name of the path. Is there any workaround for this? I tried to change the Python code to skip this step, but then Octane crashes during the rendering step.

[enricocerica]

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?

Have you installed the Python 2.6 ( http://www.python.org/download/ ) or are you using the basic library provided with Blender ?

I was using the basic library that was included with Blender 2.49b. I figured out that I needed to install Python to get rid of the error, but now I have run into another problem - I am getting the error about spaces in the project path. I can't really change the name of the path. Is there any workaround for this? I tried to change the Python code to skip this step, but then Octane crashes during the rendering step.

Sorry, no way to workaround, spaces in the project are not allowed.

[radiance]

enrico -> can't you fix this in the exporter ? you should be able to give octane what it needs by enclosing the full pathnames in double-quotes, eg "c:\my dir\my file.ocs" ?

Radiance

[GeoPappas]

enrico -> can't you fix this in the exporter ? you should be able to give octane what it needs by enclosing the full pathnames in double-quotes, eg "c:\my dir\my file.ocs" ?

FYI: I tried to enclose the path in quotes within the dialog window that is run by the script, but it didn't work. It still complained about spaces in the path, but I didn't try to do this within the Python code. If I get a chance this weekend, I will try that out and see if that works.

Radiance:

Any chance of fixing this from Octane's side in the near future? That is, allowing Octane to use paths with spaces.

[radiance]

enrico -> can't you fix this in the exporter ? you should be able to give octane what it needs by enclosing the full pathnames in double-quotes, eg "c:\my dir\my file.ocs" ?

FYI: I tried to enclose the path in quotes within the dialog window that is run by the script, but it didn't work. It still complained about spaces in the path, but I didn't try to do this within the Python code. If I get a chance this weekend, I will try that out and see if that works.

Radiance:

Any chance of fixing this from Octane's side in the near future? That is, allowing Octane to use paths with spaces.

you can use paths with spaces as long as you use double quotes from the command line.
in most areas spaces in paths work, the only area where there are issues is with textures in the MTL file.
however, i'm not sure, there might be other places.

maybe we should start a thread to collect all these spaces issues,
but i think we should wait a while as we're changing a few things on 2.3 which might fix a fair bit of them already.

Radiance

[enricocerica]

A new script version is available (see top of this thread), it mainly solves the Text material issue.

[Elvissuperstar007]

blender 2.53 plug-in will?

[enricocerica]

A new script version is available (see top of this thread). IPO curves can now be used for Lens Aperture and Focal Depth. See the post for usage.

[kivig]

Are texture sequences supported?