Beta 2.2 RC1: Blender 2.49 Export Script testing thread

[matej]

For your first issue try to create your material in Octane as macro or node, and then pin that to the right position on your mesh node. This works for me.

[Aspen]

Thank You a lot for this advice! Working perfectly

EDIT:
Looks like your way to save materials also works for my second issue which solves all my problems atm. Thanks again!

[enricocerica]

Hi,

I released a new script for 2.49, you'll find several fixes.
See the top of the thread.

Enjoy

[danvica]

I've got a problem during animation.

The exporter "exports" always the same frame even if the filename changes rightly (0001 - 0002 - ...).

[danvica]

I'm the only one having this problem ?

Before the last version of the exporter I could render each frame of the animation (but I had the material's curve problem).

Now I could render curves with the right materialsbut the exporters calls Octane with the same frame to render.

There's not so many button to push/configurate... but could be my fault.

[enricocerica]

I'm the only one having this problem ?

Before the last version of the exporter I could render each frame of the animation (but I had the material's curve problem).

Now I could render curves with the right materialsbut the exporters calls Octane with the same frame to render.

There's not so many button to push/configurate... but could be my fault.

Everything seems to work for me, I tested objects and camera displacement and it changes at each frame ...

[lechu]

Is it possible to update and make some slight changes in the 2.2 RC1 script, that it could be used with the latest Octane versions under Blender 2.49?

I've noticed that everything works fine except camera export - lens angle in Octane differs probably exactly 20 degree from the one I set up in Blender (ie. angle in Blender = 72, angle after export to Octane = 52 so each time while rendering animation I must "fake" the camera angle in Blender). Another small, but VERY disturbing bug/problem that I find, is very slight difference in camera position after exporting it to Octane. It seems that the exporter "loses" some of the coordinates and the camera has little offset towards one of the axis (X axis in my case, when I compare it to Blender's coordinates, the difference is about 0.1 or 0.01). The problem is that when I want to add additional render passes (ie. z-depth) to my final output from Octane, both renders have slight differences, edges are not in exact the same locations, geometry from Octane doesn't match the one I render in Blender. By that, it's impossible to make any post production/compositing in any software...

Could this feature be fixed? I think many people would be grateful, I myself for sure

[danvica]

@enricocerica

Well, you're partially right. The camera is moving but all the meshes (both real mesh + fluid + curves with bevels and animated tapers) are fixed at the end frame situation.

Any idea ?

Can't be linked to the new "nothing" button on advance settings ? It's not activated but... its status is not saved if I close and open Blender... strange.

P.S. Using yafaray (very slow ) render engine the animation is ok.

[enricocerica]

Is it possible to update and make some slight changes in the 2.2 RC1 script, that it could be used with the latest Octane versions under Blender 2.49?

I've noticed that everything works fine except camera export - lens angle in Octane differs probably exactly 20 degree from the one I set up in Blender (ie. angle in Blender = 72, angle after export to Octane = 52 so each time while rendering animation I must "fake" the camera angle in Blender). Another small, but VERY disturbing bug/problem that I find, is very slight difference in camera position after exporting it to Octane. It seems that the exporter "loses" some of the coordinates and the camera has little offset towards one of the axis (X axis in my case, when I compare it to Blender's coordinates, the difference is about 0.1 or 0.01). The problem is that when I want to add additional render passes (ie. z-depth) to my final output from Octane, both renders have slight differences, edges are not in exact the same locations, geometry from Octane doesn't match the one I render in Blender. By that, it's impossible to make any post production/compositing in any software...

Could this feature be fixed? I think many people would be grateful, I myself for sure

I made some quick tests and when I compare the result with blender and octane, I have the same result, except that edges are a bit thicker with Octane probably due to the AA, values for camera position are the same (except that they are rounded in the blender properties window).

Could you give more details about those problems as I really can't point them ?

Does anybody else have the same issues ?

[enricocerica]

@enricocerica

Well, you're partially right. The camera is moving but all the meshes (both real mesh + fluid + curves with bevels and animated tapers) are fixed at the end frame situation.

Any idea ?

Can't be linked to the new "nothing" button on advance settings ? It's not activated but... its status is not saved if I close and open Blender... strange.

P.S. Using yafaray (very slow ) render engine the animation is ok.

Will check that, the new "nothing" shouldn't be there, I forgot to remove it as I use it for personal purposes and it shouldn't affect the result if not ckecked. By the way, as it is there now it may be helpful to animate the camera and sun without re-exporting the whole geometry