OTOY Forums

Please give a try to the built-in wavefront exporter. If it works fine I probably can easily fix my plugin.

Cheers,
Lionel

I can confirm that exporting works just fine.

I've also included a zip of the .blend which will, hopefully, help.

Hello, I have chosen a Blender file of a vehicle that I am currently modelling, and I have compared the Unsuported Blender plugin v1.12 with the Wavefront exporter built in Blender 2.62.

With the same settings and the unofficial plugin set to not create OCS file, I have to say that the official Wavefront exporter is still faster :

24.22 s versus 33.22 s with v1.12.

The files produced are a bit different in size :

Blender Wavefront Official :
obj : 30.542 ko.
mtl : 3 ko.
Export time : 24.22 seconds.

Unsupported 1.12 :
obj : 32.061 ko.
mtl : 2 ko.
Export time : 33.22 seconds.

I have not tested the files in Octane, though...

Any idea about this difference in the export time between the two exporters ?

I think that Lionel's scripts do more than the standard wavefront export. So you can forgive them for taking a bit longer. You end up with a better result from Lionel's script.

The issue is a bit more complex than I initially thought and seems related to normals being wrongly exported now... I also notice that my exporter outputs much more geometry than the wavefront one and that's also pretty strange to me.

I'm on both issue but pretty busy with my job while also preparing to move into a new house. In the meantime you can disable the 'Rotate X90' in 'Octane Export settings' sub-panel, it should do the job until I can cleanup the script.

No worries Lionel. I can wait it just means that I will have to keep my hands off of BMesh for a while

My Blender with BMesh breaks exporting (v. 1.13) with error (see attached file).

I Just haven't noticed the moment when is started... Scene created in previous versions was rendering normally in my r44308.
I added some mesh objects to my complex scene and now this message appears.
But if I open this changed file with Blender 2.62 official build (r44136) exporting works just fine with no errors.

I just thought that this iformation can be useful.

This is because of bmesh... old mesh objects are still using the old mesh code, new objects are using the new bmesh code...

Right now, there is limited python api for bmesh objects... if your wanting octane support, stay with the official build of blender and wait until yoyoz says its supported to the trunk...

convergen wrote:This is because of bmesh... old mesh objects are still using the old mesh code, new objects are using the new bmesh code...

Right now, there is limited python api for bmesh objects... if your wanting octane support, stay with the official build of blender and wait until yoyoz says its supported to the trunk...

I understand that )
I posted that error just to point the differences — maybe this can be helpful in finding code differences. If it's not... so, at least it will warn somebody that BMesh causes not only normal problems.

I just discovered that the built-in wavefront exporter has same issue: if you select 'export normals' you'll get same result as octane plugin.

Even worse, I got some scenes I cannot export anymore with both plugins... I've to report this to Campbell. In the meantime, you can disable export of normals in my plugin and cross fingers so you don't get hit by the geometry bug.