I'm trying to tame the FBX exporter so that we can wrap it neatly into our exporter systems for ProPack but, as usual whenever we delve into fbx there are issues and you end up pulling your hair out. What we're trying to do is to offer a neat fbx export pipeline that then ties into all the MetaData systems within Red9, this is all running nicely but we want to expand the fbx support and thats where things start to look flaky...
So there are a few things that are currently breaking and I'm not sure if it's just fbx or if there's something else going on here, all of the issues we're seeing are also evident just from the standard exportSelection call from the file menu.
Firstly even with a simple referenced rig in the scene tand the skeleton selected he 'BakeAnimation' from the default export UI doesn't actually run at all in Maya 2016 sp6, it does in SP2 though, is this a known thing? It runs from the gameExporter UI but not the native fbx export options. Now when called in code it's fine so that's not a big worry, just strange that it doesn't run from default UI's.
The big issue is that if I save as FBX ASCII the file doesn't actually load the data back, in binary all is good, but I'll be damned if I can actually get an fbx ASCII to load any data back. Again it doesn't seem to matter if it's done in code or from the UI.
Can anybody else either confirm these issues or throw any light on them