Unity auto .blend-to-.fbx fail to export
Closed, InvalidPublic


System Information
Windows 7
GTX 770 OC

Blender Version
Broken: 2.77 RC2 1e1118e
Worked: 2.76b

Short description of error
Unity automatically converts .blend files to a .fbx (meta file) using Blender's fbx script.
Since 2.77, Unity fails to import the .blend file and leaves it empty/unknown

Exact steps for others to reproduce the error
Import a .blend file into Unity


¿? (edtion) updated the task description. (Show Details)
¿? (edtion) raised the priority of this task from to Needs Triage.
¿? (edtion) added a project: Addons.
¿? (edtion) set Type to Bug.
¿? (edtion) added a subscriber: ¿? (edtion).
Bastien Montagne (mont29) claimed this task.

That’s Unity problem, not Blender problem. Please report bug to them!

While trying to report this to unity, I found that the same problem occurred in 2.71. Someone else reported the bug to blender and was redirected to report it to Unity, then was told to tell Blender.

Thread for previous issue: http://forum.unity3d.com/threads/blender-2-71-blend-to-unity-broken.254632/
The user said someone found an issue with the way Blender was compiled or something and it was fixed in a Blender update.
Thread for Blender report: https://developer.blender.org/T40907

Unity tries to open Blender to auto-import the .blend (sometimes Blender crashes), so maybe it doesn't use the fbx script in Blender's folder, either way, something changed in the 2.77 that causes the error but I don't know how to find it.

Yeah, but we cannot do anything with 'sometime blender crash when launched from Unity', that’s not a bug report. If issue is same as T40907, then it’s a python bug - but I’d really doubt it… This is most likely not the same issue - though it could be caused by python again, since only meaningful changes I can think off here from 2.76 to 2.77 are:

  • Refactor of the command-line handling of Blender.
  • Switch to Python 3.5

Anyway, it’s up to Unity guys to first investigate that issue - and then, if they find an actual bug in Blender, they’ll report it to us. That would imply a way to reproduce it without having to use Unity at all.

Btw, I did not see any Unity staff answer in http://forum.unity3d.com/threads/blender-2-71-blend-to-unity-broken.254632/, only users afaict.

¿? (edtion) reopened this task as Open.Mar 27 2016, 10:17 PM

Okay, I reported it to Unity and I was told they'd forward it to the devlopers to see if it's a problem on their end and said a workaround would be to export fbx in Blender. It's been over 2 weeks since then and I've heard nothing and found that they marked it as "solved" with that export in Blender thing, which doesn't solve anything, just ignores the problem. https://issuetracker.unity3d.com/issues/unity-fails-to-import-blend-when-blender-2-dot-77-is-installed

You marked it closed and they marked it solved but 2.77 is final and the problem is still there. All you need to do to reproduce the results is load any .blend file into Unity 5 while Blender 2.77 is installed. Beyond that, I only know that .blend files would successfully import as fbx-metadata in Unity 5 while 2.76b and prior were installed.

I’m sorry you had that experience with their support (also tried to deal with them when I was rewriting FBX exporter two years ago, was not much enthousiasming).

But the point remains exactly the same: Blender FBX exporter works - it’s Unity's own coocked script to fake “native” support of .blend files which fails, so it’s their problem to fix it, or at least, investigate the issue. We do not support Unity products here! And please do not reopen tasks yourself.

Same issue here with both 5.3 and 5.4 beta unity.
Will stick to 2.76b until something occurs.

Yeah, Unity emailed me saying "Fix branch needs to land to our main branch for fix to get released. This might take some time."
So I don't know if that means during 5.4 Beta, release or a dot release afterwards.