Blender Exporter 2.02

[steveps3]

I've tweaked the Blender exporter so that it will now create a new .OCS if the project that you have supplied doesn't exist.

If you've not been following my other thread, a quick summary. Lionel's Blender export script got broken. It no longer works for Octane above version 1.20. The main reason for this is that Lionel's script tried to export all the materials inside the .OCS file. The format of the .OCS has changed and so the script stopped working. I have stripped out all the writing of materials etc. Now all that happens is that the .OBJ/.MTL files are generated and Octane called.

Give it a go if you want. You install it just like the old exporter straight from the .ZIP file.

[vinz]

THANKS YOU SO MUCH !!! Steve.

So i suppose this one is working with the lastest octane standalone.
I'll make a try asap.

That's wonderfull to see someone keeping the exporter up to date.
Thanks for your time and talent.

[simdal]

Hello, I need an exporter for instances. The octinstances_v019 version does not work with the latest version of blender. Can anyone help me? (I ask the mythical EnricoCerica?)
Thank you.
Hello, Sim

EDIT: sorry, I made ​​a mistake. working properly.

[ROUBAL]

Hello, I need an exporter for instances. The octinstances_v019 version does not work with the latest version of blender. Can anyone help me? (I ask the mythical EnricoCerica?)
Thank you.
Hello, Sim

I confirm that it works fine with Blender 2.69, but I encountered a weird trouble when switching to 2.69, that I fixed by deleting the addon and loading it again : The first time, the button for obj export was not available in the addon GUI.

[ROUBAL]

Well, bad news : I encounter the problem of the octinstances_v019 not working with the Blender 269 for Octane version. This instances exporter still works fine for me with the official Blender 2.69, but refuses absolutely to work with the plugin version.

I deinstalled and reinstalled everything many times : Blender 2.69 for Octane, the Octane Unsupported Plug-in v1.20 by Lionel (also tested with the more recent v2.02), and the unoffical Instances exporter octinstances_v019 by Matej.

I also deleted the content of the Blender roaming folder (copy of the python script) without any success. Blender for Octane choses itself the path and rewrites the folder content.

I can't export instances (csv files). The little plugin panel also doesn't show the Write dupli objects to file. This last point is not a problem for me as I never use this feature, but the main problem is that the script doesn't work at all.

The weirdest thing is that whatever path I type in the field, the python file isn't installed at the specified location, but instead in the Users\...\AppData/Roaming\... path.

Here are the screen shots :

[kavorka]

I have a problem now (I just updated to this version from the 1.17).
Now it exports my whole scene, where as before it only exported the layers I currently have selected. Is this just how it works now, or do I need to go back to 1.17?

The reason why I want to update is because I can't rename materials when in Octane render mode, I need to change back to blender internal every time I want to rename a material.
Is there a better way to do all of this?

[ROUBAL]

The select option has been disabled since 1.18 if I remember well. All objects set to visible even if on hidden layers are exported.

So, the best method to make sure you export only what you need is as following :

1 : Enable visibility of all layers.
2 : Select the objects you want to export.
3 : Ctrl I to inverse selection.
4 : H for hiding all unwanted objects.

Select only meshes. An Empty or something which is not a mesh can put troubles in the export. Theorically it should be ignored, but it is better to avoid problems.

Important : The camera must be hidden as well, but always keep a camera in the scene, even if you only want to export without rendering anything. If you remove the camera, the script will gives an error message and will not export.

Except if you want a whole scene to be exported as it is to Octane's world, individual objects have to be put a the origin of the 3D space : it is very important if you want to move them easily in Octane and absolutely necessary if you use them as instances.

I hope this helps you.

Philippe.

[kavorka]

Man, 0.o.
I think I will just stay with 1.17.
That's too much work for not enough upside.

[ROUBAL]

You'll see that it is not a big deal once you'll be used to this process.

[r-username]

Hello, I need an exporter for instances.[/b]

+1, having the instances extra script work with 2.02 would be great or just a instance exporter py.

thanks in advance