It was working fine in 2019.2.6f1. It was so useful I used it all the time.
Doesn’t seem to work at all in 2019.3.2f1.
Steps:
Enable official FBX export package via package manager
Select the thing(s) you want to export
RMB > Export to FBX…
Click on Export (with the default Assets folder set as the export path).
Click Overwrite if prompted a file with the same name already exists.
Result: Nothing happens.
Extra Test 1:
After doing steps 1 to 3, I tried changing the name of the export file and clicking export.
Result: The export button blinks.
Extra Test 2:
Did steps 1 to 4 on a default Unity Cube.
Result: Export button blinks; no Cube.fbx is exported.
This issue happens with Export Format set to Binary or Ascii.
We’ll be stuck on this version of the engine for at least a few months.
Therefore it would be ideal if I could get this to work by making some change locally.
Edit: Same issue happens on both 3.0.1, and 3.0.0. Made sure there was no FbxExporter folder before installing - after each uninstall, I shutdown Unity, rebooted, and verified no FbxExporter existed.
Edit2: Thankfully 2.0.3 still works, but it seems less robust compared to how stable it was on 2019.2.6f1.
Maybe Unity forgot to commit the UnityFbxSdkNative.dll?
Another thing that is strange is this:
According to the package manager, FBX Exporter preview 2 - 3.0.1 is installed.
BUT, according to the console some of the errors are referencing preview 1 - 3.0.0 :
Autodesk.Fbx.NativeMethods+SWIGExceptionHelper…cctor () (at Library/PackageCache/com.autodesk.fbx@3.0.0-preview.1/Runtime/Scripts/NativeMethods.cs:119)
Rethrow as TypeInitializationException: The type initializer for ‘SWIGExceptionHelper’ threw an exception.
Autodesk.Fbx.NativeMethods…cctor () (at Library/PackageCache/com.autodesk.fbx@3.0.0-preview.1/Runtime/Scripts/NativeMethods.cs:139)
Rethrow as TypeInitializationException: The type initializer for ‘Autodesk.Fbx.NativeMethods’ threw an exception.
Autodesk.Fbx.Globals…cctor () (at Library/PackageCache/com.autodesk.fbx@3.0.0-preview.1/Runtime/Scripts/Globals.cs:813)
Rethrow as TypeInitializationException: The type initializer for ‘Autodesk.Fbx.Globals’ threw an exception.
The constants referencing the dll path have incorrect values. If you open the file “Library\PackageCache\com.autodesk.fbx@3.0.0-preview.1\Runtime\Scripts\NativeMethods.cs”, and change the constant DllImportName with the value Packages/com.autodesk.fbx/Runtime/Plugins/x86_64/UnityFbxSdkNative.dll (or the equivalent constants and values for MacOS and Linux), the plugin will work again.
It looks like your fix seems to stick if you make the change here: C:\Users\USER\AppData\Local\Unity\cache\packages\packages.unity.com\com.autodesk.fbx@3.0.0-preview.1\Runtime\Scripts\NativeMethods.cs
Go to the line 243 in the document, or search for “const string DllImportName”. There are the values for each operating system (below the line “#elif UNITY_EDITOR_OSX” for Mac, “#elif UNITY_EDITOR_LINUX” for Linux, and “#elif UNITY_EDITOR_WIN” for Windows; it’s the OS that you use the editor on, not the game target OS).
If you are on the Windows Unity editor, you have to change the line below #elif UNITY_EDITOR_WIN to const string DllImportName = "Packages/com.autodesk.fbx/Runtime/Plugins/x86_64/UnityFbxSdkNative.dll". I haven’t tested the Mac and Linux fixes, but they should be const string DllImportName = "Packages/com.autodesk.fbx/Runtime/Plugins/x86_64/UnityFbxSdkNative.bundle/Contents/MacOS/UnityFbxSdkNative" and const string DllImportName = "Packages/com.autodesk.fbx/Runtime/Plugins/x86_64/UnityFbxSdkNative.so" respectively.
Unfortunately, it does not look like this patch works anymore; at least fully in 2019.4.31f.
Changing the path will allow the Export to FBX option to appear but attempting to export it, the system reports that the .dll is not located at that path: DllNotFoundException: Packages/com.autodesk.fbx/Runtime/Plugins/x86_64/UnityFbxSdkNative.dll
I tried following the path of the .dll you listed and it doesn’t exist: at Packages/com.autodesk.fbx/Runtime/Plugins/x86_64/UnityFbxSdkNative.dll
I am unsure if this path means that within the project’s Packages folder, it should exist or within the AppData/Local folder of Unity.
I’m using FBX Exporter 5.0.0 and still encounter this issue, the annoying point is that my computer has no problem while all my colleagues have this issue!