Official New FBX Exporter in 2017.2

Hey there,

So I installed the plugin. However, I do not get any installed Maya versions displayed in the Settings. I have Maya LT 2018 installed. So then I tried to do it manually but no luck either. What am I missing here?

Thomas

 

Currently, we only support the regular version of Maya. We are working on adding supporting Maya LT.

 

When can we expect LT to be supported? What time frame are we looking at?

 

I have exactly the same problem as Thomas plus a bunch of errors in the console everytime I interact with FBX Export Settings window like moving my mouse into and out of that window area or checking and unchecking options. The errors are below, and I'm using Maya 2018 and Unity 2017.2.0f3

--------------------------------------------------------------------------------------------------------------

Unexpected top level layout group! Missing GUILayout.EndScrollView/EndVertical/EndHorizontal?
UnityEngine.GUIUtilityrocessEvent(Int32, IntPtr)

GUI Error: You are pushing more GUIClips than you are popping. Make sure they are balanced)
UnityEngine.GUIUtilityrocessEvent(Int32, IntPtr)

ArgumentOutOfRangeException: Argument is out of range.
Parameter name: index
System.Collections.Generic.List`1[System.String].RemoveAt (Int32 index) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Collections.Generic/List.cs:538)
FbxExporters.EditorTools.ExportSettings.GetMayaOptions ()
FbxExporters.EditorTools.ExportSettingsEditor.OnInspectorGUI ()
UnityEditor.InspectorWindow.DrawEditor (UnityEditor.Editor[] editors, Int32 editorIndex, Boolean rebuildOptimizedGUIBlock, System.Boolean& showImportedObjectBarNext, UnityEngine.Rect& importedObjectBarRect) (at C:/buildslave/unity/build/Editor/Mono/Inspector/InspectorWindow.cs:1240)
UnityEngine.GUIUtilityrocessEvent(Int32, IntPtr)

 

Hi there,
Is this going to be a Autodesk softwares only workflow or can we expect it to work with other softwares in future? I'm particularly interested in Blender.
Does any of the FBX exporter features work at runtime? or is this editor only ?

 

We're investigating the issue and we'll let you know when we have a resolution.

 

The Unity FBX exporter package will work with Blender's existing FBX import/export scripts. We're looking giving you some Blender love but after we've done with Autodesk DCCs.

The FBX exporter features are available in editor only so, no runtime support.

 

Plus One for Maya LT support !

 

BTW. even without Maya LT support, can we still export mesh.asset into FBX file? So I can try load it manually from Maya LT? I need this feature so I can export procedurally generated Unity mesh into FBX file.

 

Yes, with the FBX Exporter Package you can Export Model as FBX from Unity.

The Maya integration adds the single click import & export to the Maya File menu. If you have Maya LT just use the native import FBX; for now

 

HI, im also having problems with the plugin. When I export from Maya 2018 I get this:

# Error: RuntimeError: file <string> line 2: TypeError: file C:\Program Files\Autodesk\Maya2018\bin\python27.zip\ntpath.py line 115: object of type 'int' has no len() #

Can anyone help me out?

 

Can you get us a stack trace, please:
- open the script editor (Windows | General Editors | Script Editor)
- from the script editor's menu bar, turn on stack trace (History | Show Stack Trace)

Now you should get a much longer error message. Please copy & paste all of it in this thread.

 

When I heard of this plugin I was excited to start using it. The plugin seems to work fine on my local machine but when sharing an FBX with at least 2 other computers via Perforce it gives us this error:

ImportFBX Errors:
Couldn't import file D:/Perforce Projects/Shopkeeper/Unity/Assets/Art/Models/Furniture/Anvil/Anvil.fbx.
File is corrupted (or invalid)

These were generally the steps I took:
I have downloaded the FBX Exporter from the Asset Store and imported everything except the integrations folder. After importing I created a cube and exported the model to an FBX. I opened this FBX with Autodesk 3ds Max 2016. In 3ds Max I removed the cube and built a new model. This model I exported to Anvil.fbx and it shows up just fine. After some changes in the import settings I committed the model using Perforce. After committing the file gives the error above on my colleagues computer and my home computer. It's worth noting that when transferring the file with a USB stick it works just fine on at least 1 computer.

I hope this plugin goes on to support more Autodesk software and continues to improve workflows and pipelines.

 

Hi, i get an error when the tangents of the original model are messed up or not there. Though the workaround is simple (set to calculate at import for instance), you might want to catch it.

IndexOutOfRangeException: Array index is out of range.
FbxExporters.Editor.ModelExporter+MeshInfo.get_Binormals ()
FbxExporters.Editor.ModelExporter.ExportComponentAttributes (FbxExporters.Editor.MeshInfo mesh, Unity.FbxSdk.FbxMesh fbxMesh, System.Int32[] unmergedTriangles)
FbxExporters.Editor.ModelExporter.ExportMesh (FbxExporters.Editor.MeshInfo meshInfo, Unity.FbxSdk.FbxNode fbxNode)
FbxExporters.Editor.ModelExporter.ExportMesh (UnityEngine.GameObject gameObject, Unity.FbxSdk.FbxNode fbxNode)
FbxExporters.Editor.ModelExporter.ExportInstance (UnityEngine.GameObject unityGo, Unity.FbxSdk.FbxNode fbxNode, Unity.FbxSdk.FbxScene fbxScene)
FbxExporters.Editor.ModelExporter.ExportComponents (UnityEngine.GameObject unityGo, Unity.FbxSdk.FbxScene fbxScene, Unity.FbxSdk.FbxNode fbxNodeParent, Int32 exportProgress, Int32 objectCount, Vector3 newCenter, TransformExportType exportType)
FbxExporters.Editor.ModelExporter.ExportAll (IEnumerable`1 unityExportSet)
FbxExporters.Editor.ModelExporter.ExportObjects (System.String filePath, UnityEngine.Object[] objects)
FbxExporters.Editor.ModelExporter.OnExport ()
FbxExporters.Editor.ModelExporter.OnContextItem (UnityEditor.MenuCommand command)
UnityEditor.GenericMenu:CatchMenu(Object, String[], Int32)

 

Hi Binary42,

We'll take a look and get it fixed for the next update.

thanks for reporting.

Simon

 

Hi Tinovdk,

Can you share the corrupted Anvil.fbx file with us so we can take a look?

Simon

 

To follow up on Mark's reply

I would guess there's something missing from the plugin's configuration, like it didn't configure correctly. If you run this python script what do you get? (they should all be strings)

Code (python):

1.  
2. import maya.cmds
3. for a in  maya.cmds.optionVar(list=True):
4.     if 'Unity' in a:
5.         print a, type(a), maya.cmds.optionVar(q=a)
6.  

Simon

 

Sure.

Here it is: https://www.dropbox.com/s/6vpkz39q8wh5i0c/Anvil.fbx?dl=0

Hope you find the issue!

 

Maya 2013 doesn't appear to work.

 

Awesome thx guys!! 3Ds Max integration close?

 

I've got a 3D model in unity. It consists of several 3D buildings, trees, and streets. I would like to export all the objects (buildings, trees, and streets) as FBX. In order to do so I use "FBX Exporter (beta)". Some of the objects can be easily exported, but some of them not.
I get the following error when try to export some of the objects:

IndexOutOfRangeException: Array index is out of range.
FbxExporters.Editor.ModelExporter.ExportComponentAttributes (FbxExporters.Editor.MeshInfo mesh, Unity.FbxSdk.FbxMesh fbxMesh, System.Int32[] unmergedTriangles)
FbxExporters.Editor.ModelExporter.ExportMesh (FbxExporters.Editor.MeshInfo meshInfo, Unity.FbxSdk.FbxNode fbxNode)
FbxExporters.Editor.ModelExporter.ExportMesh (UnityEngine.GameObject gameObject, Unity.FbxSdk.FbxNode fbxNode)
FbxExporters.Editor.ModelExporter.ExportComponents (UnityEngine.GameObject unityGo, Unity.FbxSdk.FbxScene fbxScene, Unity.FbxSdk.FbxNode fbxNodeParent, Int32 exportProgress, Int32 objectCount, Vector3 newCenter, TransformExportType exportType)
FbxExporters.Editor.ModelExporter.ExportComponents (UnityEngine.GameObject unityGo, Unity.FbxSdk.FbxScene fbxScene, Unity.FbxSdk.FbxNode fbxNodeParent, Int32 exportProgress, Int32 objectCount, Vector3 newCenter, TransformExportType exportType)
FbxExporters.Editor.ModelExporter.ExportComponents (UnityEngine.GameObject unityGo, Unity.FbxSdk.FbxScene fbxScene, Unity.FbxSdk.FbxNode fbxNodeParent, Int32 exportProgress, Int32 objectCount, Vector3 newCenter, TransformExportType exportType)
FbxExporters.Editor.ModelExporter.ExportAll (IEnumerable`1 unityExportSet)
FbxExporters.Editor.ModelExporter.ExportObjects (System.String filePath, UnityEngine.Object[] objects)
FbxExporters.Editor.ModelExporter.OnExport ()
FbxExporters.Editor.ModelExporter.OnContextItem (UnityEditor.MenuCommand command)
UnityEditor.GenericMenu:CatchMenu(Object, String[], Int32)

Somebody told that "it seems one of the objects you are trying to import to FBX has a script in which you may have an array that is null or is getting out of range. I will advise checking the objects you have a script attached to see if that is the case." I removed all the scripts from the model. But still does not work.

Do you have any idea?

Regards,

 

Hey, we are a team (DADIU) having problems with linked prefab instances. Specifically we want to have model updates AND texture updates be reflected in Unity after they are updated in Maya. Model updates, and the material itself is updated, but textures are never embedded when using this plugin.

The showcase video highlights using a Stingray PBS shader, but from I gather from the documentation, a lambert material with a texture should work aswell. I cannot seem to get it to work. Have anyone gotten it to work yet, and would like to share their knowledge?

 

Hi Tinovdk,

Thank you, I've downloaded the file and logged the issue. We will check it out and get back to you.

Best,
Viktoria

 

Hi @laurentlavigne,

The plugin supports Maya 2017 or later. We still allow the option to try installing to earlier versions of Maya, however, it is not guaranteed that they will work.

Best,
Viktoria

 

Hi @GMax

Yes we will release a new version of the package soon which will include the integration for 3Ds Max 2017 or later. We would love to get your feedback once it's out

Best,
Viktoria

 

Hi unity_ikjJtsxUu_cS4A,

Could you please share a package containing a prefab for one of the objects that you are unable to export?

An easy way to create the package is to create a prefab for your object if you haven't already, then right click on the prefab in the project view and select "Export Package...". This should export the prefab and any dependencies to a .unitypackage.

Best,
Viktoria

 

AWESOME!! Will do! Thx guys!

 

Hi @TheFragen ,

In order for Unity to find textures added in Maya the textures will have to either be placed in the Unity project or embedded into the FBX file.

For more information on where Unity searches for textures you can check out these links:
http://answers.unity3d.com/questions/47733/importing-from-maya-textures-gone.html
https://docs.unity3d.com/Manual/class-Mesh.html

If you would like to export textures as embedded from Maya using the Maya Unity plugin, it's possible to change the export settings by modifying the following file in the FBX exporter package: "FbxExporters/Integrations/Autodesk/maya/scripts/unityFbxExportSettings.mel"
In the file you should see a line that says

Code (csharp):

1.  
2. FBXExportEmbeddedTextures -v false;
3.  

if you change the "false" to "true" then textures will be embedded on export.

Let me know if this doesn't fix the problem or if you have any other issues.

Yes you're right, lambert material with a texture should work as well.

Best,
Viktoria

 

Great thank you, that did indeed solve the issue. Very much appreciated.
I want to add, that when we export models with animations, we have to bake them manually first. Baking is done automatically when exporting to fbx through File -> Export. Further, when the model is imported in Unity, we have to find the model in Project, go to Rig, and set Animation Type to Generic to get animations, rather than it being set automatically.

 

My pleasure, glad it solved the issue.

For exporting animations from Maya, you can again modify the "FbxExporters/Integrations/Autodesk/maya/scripts/unityFbxExportSettings.mel" file in the FBX exporter package.
Adding these lines to the file will let you set the same bake animation options as in File->Export:

Code (csharp):

1.  
2. // Set to true to bake animation on export
3. FBXExportBakeComplexAnimation -v true;
4. // set the start time for baking the animation
5. FBXExportBakeComplexStart -v [int];
6. // set the end time for baking the animation
7. FBXExportBakeComplexEnd -v [int];
8. // set how many keys are created per frame
9. FBXExportBakeComplexStep -v [int];
10. // turn resample all on or off
11. FBXExportBakeResampleAll -v false;
12.  

You can replace [int] with the appropriate start, end, and step values.

Alternatively, you can comment out or remove the first line of the unityFbxExportSettings.mel file which is:

Code (csharp):

1. FBXResetExport;

This will make it so that the File->Unity->Export button uses the same settings as the File->Export for everything that is not explicitly set in the unityFbxExportSettings.mel file.

I'm assuming you are exporting an inanimate object such as a spaceship with animation, correct?
Are you seeing this when exporting the model from Unity as well (i.e. if you check the model import settings immediately after you export or convert to linked prefab instance)?

I'm trying to recreate the issue and so far I have done the following:
1. Create Cube in Unity scene
2. Convert Cube to linked prefab instance
3. Check created fbx import settings -> Animation Type is set to none
4. Import into Maya
5. Export from Maya with animation
6. Check fbx in Unity -> Animation Type is still set to none

It looks like the issue is related to the fact that we currently don't support export of animations from Unity, however we will have to investigate further to know for sure.

 

Hey vkovec, apologies for the late reply. Your suggest to add bake animation options to unityFbxExportSettings.mel successfully exports models with animations.

You are right that it is inanimate objects (without a rig) we try to export. I can recreate your step-by-step guide, but as I said, animations are fully imported, once we set Animation Type to Generic. This option sticks for all future re-imports. It's fine we have to change the setting, I just wanted to make you aware of it.

For anyone Googling this in the future, here are the export settings we ended up using for exporting animations:

Code (csharp):

1.  
2. // Animations
3. FBXExportBakeComplexAnimation -v true;
4. FBXExportBakeComplexStart -v 0;
5. FBXExportBakeComplexEnd -v `playbackOptions -query -animationEndTime`;
6. FBXExportBakeComplexStep -v 1;
7.  

 

please! make it runtime! and importer too!

 

runtime importer.. that's my dream come true. haha

 

I got the same problem, here is the stack trace. Also, it is working fine with OSX + Maya 2018, but errors with Windows 10 + Maya 2018


select -r Cube ;
exportCmd.('__init__',) [()]
exportCmd.('__del__',) [()]
# Error: object of type 'int' has no len()
# # Traceback (most recent call last):
# # File "C:\Users\Peter\Documents\project\Assets\FbxExporters\Integrations\Autodesk\maya\scripts\UnityFbxForMaya\commands.py", line 276, in doIt
# # if not self.loadUnityFbxExportSettings():
# # File "C:\Users\Peter\Documents\project\Assets\FbxExporters\Integrations\Autodesk\maya\scripts\UnityFbxForMaya\commands.py", line 83, in loadUnityFbxExportSettings
# # fileName = os.path.join(projectPath,"Assets", maya.cmds.optionVar(q="UnityFbxExportSettings"))
# # File "C:\Program Files\Autodesk\Maya2018\bin\python27.zip\ntpath.py", line 67, in join
# # p_drive, p_path = splitdrive(p)
# # File "C:\Program Files\Autodesk\Maya2018\bin\python27.zip\ntpath.py", line 115, in splitdrive
# # if len(p) > 1:
# # TypeError: object of type 'int' has no len()
# Traceback (most recent call last):
# File "<maya console>", line 1, in <module>
# File "<string>", line 2, in unityExport
# RuntimeError: object of type 'int' has no len()
# # Traceback (most recent call last):
# # File "C:\Users\Peter\Documents\project\Assets\FbxExporters\Integrations\Autodesk\maya\scripts\UnityFbxForMaya\commands.py", line 276, in doIt
# # if not self.loadUnityFbxExportSettings():
# # File "C:\Users\Peter\Documents\project\Assets\FbxExporters\Integrations\Autodesk\maya\scripts\UnityFbxForMaya\commands.py", line 83, in loadUnityFbxExportSettings
# # fileName = os.path.join(projectPath,"Assets", maya.cmds.optionVar(q="UnityFbxExportSettings"))
# # File "C:\Program Files\Autodesk\Maya2018\bin\python27.zip\ntpath.py", line 67, in join
# # p_drive, p_path = splitdrive(p)
# # File "C:\Program Files\Autodesk\Maya2018\bin\python27.zip\ntpath.py", line 115, in splitdrive
# # if len(p) > 1:
# # TypeError: object of type 'int' has no len() #

 

I got the same issue and ran the script, here's what I got:

UnityAsset <type 'unicode'> C:/Users/Peter/Documents/project/Assets/Export_From_Unity/Assets
UnityExportFileType <type 'unicode'> FBX export
UnityProject <type 'unicode'> C:/Users/Peter/Documents/project

When I ran it on OSX I got:

1. 
   UnityApp <type 'unicode'> /Applications/Unity2017_2/Unity.app
   UnityAsset <type 'unicode'> /Users/ben/project/Assets/PrototypeScene_01/Models
   UnityExportFileType <type 'unicode'> FBX export
   UnityFbxExportSettings <type 'unicode'> FbxExporters/Integrations/Autodesk/maya/scripts/unityFbxExportSettings.mel
   UnityFbxForMaya_Headless <type 'unicode'> 0
   UnityInstructionPath <type 'unicode'> _safe_to_delete/_temp.txt
   UnityProject <type 'unicode'> /Users/ben/project
   UnityTempSavePath <type 'unicode'> _safe_to_delete

 

I just ran the installation again and it now works fine. I can't be sure, but maybe the wrong Maya version was selected in the first installation.

 

Hi @TheFragen great I'm glad animation is exporting now

This was an interesting find, I've logged it as an issue. Thanks for letting us know!

 

Hi @mrbenn , thank you for sending the stack trace and variable values. It looks like the configuration did not set all the necessary variables on Windows. Particularly, the problem you are seeing is due to the "UnityFbxExportSettings" optionVar not being set.

I'm glad it ended up working. I just tried installing to Maya 2017 then opening Maya 2018 and it does in fact cause this problem if I try to use the plugin in Maya 2018. Another possible cause could be resetting the Maya preferences after installing the Unity integration.

Best,
Viktoria

 

Hi @tufeixp,

I'll pass on the request.

Best,
Viktoria

 

Great plugin. Here is my request for future versions:
-Possibility to export UVW coordinates (as it seems, right now it expoorts only UV). I know that standard UV mapping is done via Vector 2, but Unity internally can use Vector3 or Vector4. Exporting Vector4 probably isn't supported by FBX format, but having atleast Vector3 as output would mean much.
-Possibility to export all UV channels supported by unity mesh: UV0, UV1, UV2 and UV3.

Why?
We are currently using a system that generates dynamic mesh in editor, and it has to write to those adittional channels in Vector3 format (for later use with shaders). Because of it's dynamic nature, it would be great to be able to export mesh to a file for later usage as final mesh. Also, having a possibility to export mesh as it is inside unity would be more consistent way of doing it (with all limits that apply from a file format).

 

Hi @olix4242,

Thank you for the request, we'll add this in a future version.

The FBX exporter should already be exporting all populated UV channels in the mesh. Are you seeing only one being exported even though you have several set?

Best,
Viktoria

 

Good to know. I was exporting with UV3 set to Vector4, so probably, as it isn't implemented, it discarded that channel.

BTW, one question that seems important in this case: does Unity importer supports UVW (vector3) coordinates? (I haven't had a time to test this yet)

 

Hi Olix,

The FBX file format only supports UV (vector2) values and this is the only source UV data used by the Unity FBX Importer and Exporter.

I've seen it handled in other 3d application by sending the UVW values to the vertex color map but that would require a change to both the importer and exporter code.

You said you're using the UVW values for 'later' use by a shader. Does that mean you're reading the UVW values from a texture image? If so, a workaround would be for you to create sidecar image file, on FBX export, containing the UVW values encoded into the RGB values - would that work?

Simon

 

3ds max close? "please say yes... 2 weeks now.."

 

Hi there,

Is it on the roadmap at all to preserve skinned mesh renderers and their bones when exporting?

Ben

 

Yes!!!!!!!!!!!!!!!! Thank you Sir!!