I have a rigged model with 3 (animation) actions. The DirectX export interface implies that actions can be exported as animationsets. After much experimentation, I finally got multiple animations exported to the .x file.
Frist, Kudos to Chris Foster (the author whose name appears in the init.py file) as the export DOES work.
However, the export settings are somewhat confusing and it took a bit of experimentation to get multiple animationsets to export at all.
For posterity, in the export dialog, I check:
Export Selected Objects Only (I select the mesh and the armature)
Export UV coordinates
Export Skin Weights
Export Armature Bones
(I skip Export Rest Position)
Include Frame Rate (my app uses this)
Export Actions as AnimationSets
It appears that should do it. However, ONLY IF I check:
Attach Unused Actions to First
will it, in fact, export ANY actions as animationsets! Without that one option checked, only the current animation gets exported. With it checked, it exports all actions, including a (non-existent) Default_Action animationset which has one (static) keyframe, which, I suppose is a generated “unused action.” I have no “unused” actions.
I don’t know python or the API well enough to know if that’s how it’s supposed to work. The init file says it was written for Blender 2.66. Was there some change after that rev (as mentioned in title I’ve got 2.69) that screwed things up? Is there a reason that export option is required? Can it be fixed?
It’s sort of a minor problem, but requires that each exported file be edited to delete the unwanted Default animationset.