I exported that FBX out of 3ds Max 2018, using the latest version of FBX available (from the dia. box, it showed version 2018). When I tested it; saving the same file name, different file name, loading > saving, etc. I did not hit any errors, everything worked without issue (using the most recent version of Unfold3d, etc.)
I'm guessing the Modo FBX format version is hitting some kind of issue with Unfold3d trying to save to an FBX version it might not have/use? (but, I have no clue ).
I don't have Modo, but does Modo give you some options when exporting the FBX? Can you use different versions of FBX to save out in? Example; Max exporting FBX will show these versions;
It looks like Unfold3d gives a couple of options for different versions of FBX to save as, maybe knowing what version of FBX the Modo version has might help?
The FBX from 3ds Max looks like this in Unfold3d;
RizomUV_VSRS.2018.0.70.g9bf0ea2 i7-4770K CPU 3.50GHz 32 GB RAM Windows 7 64bit SSD GeForce GTX Titan X driver 398.11
below you'll find the current MODO (11.2v1) FBX import/export options. the file <test.fbx> is loading in Unfold3d and Modo. Modo identifies <test.fbx> as fbx2018 file and correctly reimports the file.
The Testmax.fbx file is loadable/saveable but triangulated, loadable in Modo too. If I save the loaded file testmax.fbx in Modo as fbx again, I can save the file in Unfold3d too. Have attached the modified file <testMaxmodo.fbx>.
As it seems, the FBX sdk used by Unfold3D is different, Foundry uses 2018.1.17 versus V 2016.1 ...
The problem seems to be linked to the FBX SDK version that is linked with Unfold3D.
We need to use a more recent version for Modo. So it will be done in the next release. For now, please be a bit patient, the work on the hotkey and mouse binding customizer is consequent. We will try to make a the new release next month.
Hi. I just bought Unfold 3D and encountered the same problem. Export from Modo using fbx, and having the same error, trying to save it after packing as fbx. Tried different fbx versions. From 2013, to 2018 - same error.