Page MenuHome

Switching Input style to "Maya" in Preferences causes models not to load correctly in Unity on MacOSX
Closed, ResolvedPublic

Description

System Information
Operating system and graphics card
MacOSX Version 10.9
Graphics Card: NVIDIA GeForce GTX 775M 2048 MB

Blender Version
Broken: 2.69.0 r60991
Worked: (optional)

Simply changing the Input type in Preferences to "Maya" and then saving "User Preferences" causes the object (that previously imported ok) to now fail on import into Unity.

Open a new scene, and use the default cube. Choose File -> User Preferences. Click on the "Input" tab at the top, then right below, set the dropdown box that defaults to "Blender" to now be "Maya" Next, click on "Save User Settings" at the bottom. Save scene somewhere so it can be used in a Unity scene. Open Unity, and drag this blender model into the scene, and it will say that it failed to convert the file into an FBX.

You might be thinking at this point that this is obviously a Unity bug (and it very well may be) HOWEVER. If you now go back into your same exact Blender scene, and simply set the Input type back to Blender, then save User Preferences, then save the file.....it will now load perfectly fine in Unity. Again, no changes to the model or anything else other than that User Preferences.

The reason this has come up is we're an educational facility for kids, so it's much nicer for them to use Maya's Input style since it matches Unity. But if the models don't import correctly, then we're kind of dead in the water in that aspect.

Based on a (as simple as possible) attached .blend file with minimum amount of steps. Please use the "default" scene.

Event Timeline

Michael Kawas (Necromancer) raised the priority of this task from to 90.
Michael Kawas (Necromancer) updated the task description. (Show Details)
Michael Kawas (Necromancer) edited a custom field.

Since Unity imports .blend files through Blender (it must be installed) perhaps it utilises macros with the default bindings on a particular command?

Campbell, do you know how the Unity .blend file importer works? It seems quite strange that keymaps would influence it. Best I can think of is that some error is printed and Unity interprets that as a failure.

@Michael Kawas (Necromancer), you could also try a more recent build than 2.69, perhaps it was a temporary issues in that release:
http://builder.blender.org/download/

Brecht Van Lommel (brecht) lowered the priority of this task from 90 to Normal.Jan 13 2014, 11:05 PM
Brecht Van Lommel (brecht) changed the task status from Unknown Status to Resolved.Jan 21 2014, 5:34 PM
Brecht Van Lommel (brecht) claimed this task.

I managed to reproduce the issue now with Blender 2.69. There's a crash when running Blender from the command line when the Maya keymap is used. However this crash was fixed in {106699ecd7c904dedd1a25606c072d5570faa629}.

That means the next release or the latest build from http://builder.blender.org/download/ will fix the issue.

I couldn't figure out how Unity detects which Blender executable to use, it somehow magically found my blender.app even though it's not in any standard location. So you may need to replace your existing blender.app to ensure that Unity is using the newest Blender version, instead of installing side by side with the existing Blender 2.69.