OTOY Forums

Please find below v1.15 of the plugin:
- fixed uv exports (not based on official fix for wavefront yet)
- fixed crash with error "TypeError: Can't convert 'bytes' object to str implicitly"

Issues with normals should be OK with latest builds.

NOTE: THIS VERSION IS ONLY FOR VERY RECENT BUILDS (tested with 44639 and 44651).

[EDIT] now v1.16:
- the exporter will create a material named 'Null' assigned to objects without a material

Lionel, THANK YOU VERY MUCH!
It seems that owing to you Blender's "unsupported" exporter is the most up-to-dated.
Thank you!

We salute you Lionel.

I just tried a scene that was working with 1.12 but now gives an error. Blender build 44136. I'll go and grab the latest SVN to see it that helps.

steveps3 wrote:Blender build 44136

The error is here. This Exporter is for lastest builds:

yoyoz wrote:tested with 44639 and 44651

Just tried 44639, works a treat.

oh wait, blender works a treat but Octane crashes. I suspect that it is the export that has caused it because Octane hasn't changed in quite some time. If it helps the problem even name is BEX64. There really isn't much else in the report but here it is just in case someone can spot something.


Problem signature:
Problem Event Name: BEX64
Application Name: octane.exe
Application Version: 0.0.0.0
Application Timestamp: 4f0f8aec
Fault Module Name: octane.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4f0f8aec
Exception Offset: 0000000000182ec8
Exception Code: c0000417
Exception Data: 0000000000000000
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057
Additional Information 1: 26a3
Additional Information 2: 26a372e8c7cc15d92f5da5669afe8010
Additional Information 3: def1
Additional Information 4: def17d671c20862cfc1916e6cb0b25d7

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I confirm. Octane crashes while loading scene.

I just tried the default cube and that worked fine. I will slowly work on this to see if I can find what it that is causing the problem.

I am a bit concerned that all these Blender code changes are confusing to people trying to find the right plugin.
I wonder if Lionel could edit the titles of his posts to include the build range or the official Blender no. which it is made for. For example.
'Plugin v1.12 for Blender 2.61 or rXXXXX to rXXXXX'.
'Plugin v1.13 for Blender 2.62 or r42800 to r442455.

I think I have the answer. It appears to happen when the object being rendered has no material. I found that one of the objects in my scene didn't have a material. I put this on its own layer and rendered just that layer and sure enough it crashed. I then gave it a material and it rendered with no problems.