I’ll try to answer for Oglu here, since we work on the same project:
-
We are currently in the process of seperating static and animated geometry which will allow us to update the geometry at least much faster (geometry alone takes ~ 90seconds). Animations are the expensive thing here and it seems to become exponentially slower the more frames we have to export (as Oglu said we are at around 8000 frames of animation)
-
Geometry isn’t that much of a problem (currently ~30000 tris), we are using one skeleton with ~50 bones (one mesh is driven by that skeleton) and around 12 animated transformation nodes. We have ~30 animationGroups and tried with and without baking (baking makes the export about 10% slower)
-
Animation export is considerably faster with smaller timeranges (timerange of 800 takes < 2 minutes). FBX export of the whole scene with 8000 framerange takes ~ 4 minutes
The main factor seems to be the framerange of the export (or maybe the count of animation groups, haven’t tested that yet), and we would very much like to export the animation groups individually, but then we would export the animated geometry and skeleton time and time again too, which would result in additional loading time and logic on import. That’s actually the reason why we would like to be able to script the exporter (mentioned here ) because that way we could automate the process of seperating the animation groups and delete everything not-animation related from the export.
Thanks for looking into this!