File optimization, FBX Python SDK 2020.3.2

[claytonsrobot]

The problem is that the FBX files exported by my code are too complex somehow. Opening an FBX file takes several minutes, if they open at all. I need to limit the number of shapes generated to about 50 to make the FBX able to open at all.

This shouldn't be an issue. It's a problem with the characteristics I'm including somehow.

[ross-g]

We found there to be a massive performance regression in the pre-built bindings that Autodesk supply at some point.

For a scene with 327 blendshapes, with Python 3.7 and FBX SDK 2020.2.1 we were seeing 800 second import times!

Testing Python 3.3 and FBX SDK 2019.2 gives import times of 30 seconds... but Python 3.3 and FBX SDK 2020.1.1 import time suddenly jumps up to 900+ seconds.

We have solved this by simply rebuilding the Python bindings from source ourselves and now see reasonable import speed again in SDK 2020.3.2.

Good luck!

[claytonsrobot]

Thank you for this information!

Can you please direct me toward resources on how to rebuild Python bindings?

Also, do you know: What will be different inside of the FBX file, when the binding is rebuilt? My exported FBX files are not encrypted and can be read in a text editor. Which elements of the FBX file, in terms of the text, would differ or be imperfect?