Non-offical Blender 2.56 plugin Tweet

[Aenima]

Hi yoyoz. I ask for it because of teamwork. I try to figure out how it possible to work on large scenes.

[yoyoz]

I think you need a 'master' blend file that has links to the parts that are created by team members. Octane will only accept to render only one obj at a time anyway, so there's nothing we can do to merge at its level, it must be done prior to the export. Links seems to work well providing you reload the master file before export, but you should probably try by yourself before using this method into production.

Happy blending!

[Rosie]

Hi, I'm using the latest version of the script (octanerender.v0.93.for_2.56a_from blender).
It only exports materials as glossy now, no diffuse or specular.

Thanks for the neat script btw

[yoyoz]

Would you mind sharing your blend and mtl files for having a look?

[regionfive]

Hello,

I am trying to render an animation. But somehow, the exporter complains about my output directory.
What am I doing wrong? I tried a lot of different ones and relative/not relative, but nothing worked.
When I pressed animate the first time, it seemed to work, but i cancelled it because I missed something.

the log says:

Image output directory is invalid or contains spaces "H:\Projects\grohe\Animation\" ("E:\dof")
Traceback (most recent call last):
File "E:\PROGRA~1\Blender\2.56\scripts\addons\octanerender\engine.py", line 64, in render
error('Image output directory is invalid or contains spaces "%s" ("%s")' % (octane_render.path,animPath))
File "E:\PROGRA~1\Blender\2.56\scripts\addons\octanerender\utils.py", line 82, in error
raise Exception("Octane plug-in: "+error)
Exception: Octane plug-in: Image output directory is invalid or contains spaces "H:\Projects\grohe\Animation\" ("E:\dof")

location:<unknown location>:-1


Thank you.

René

[yoyoz]

Hi René,

does the directory E:\dof exist?

Yoyoz

[pixelrush]

I was looking at grohe and wondering if that had some non latin dangly bits over the o or e?

[yoyoz]

that was my first though as it looks very german but the path with 'grohe' is the project path which should not have been displayed here (bug in my script - just a wrong copy/paste but has no impact on export) and has succesfully been tested a couple of lines before. The error thrown from line 64 of engine.py is really about E:\dof which is the absolutized and normalized output diretory for images (below 'render' button) and is tested against the two following conditions:
- os.path.isdir (must exist and must be a directory)
- name.find(' ') < 0 which means no space have been found in path

[r0ug3r]

hi guys! i have the same problem since v2.43, all materials seems to load only glossy and specular. it ignores diffuse even if it is assigned diffuse in blender. as i understand it is the octane way. not the exporters problem.

one question though if u may help me, if I will make material macro with image as texture then save the material node. will the image appear again in the texture when i load it to octane even if i remove the image to its location.?

Thankszz...
Chow!!

[radiant]

yoyoz can u please evaluate this problem