Hello,
Part of the point of skeletal animation formats like Cal3D is the
resource-sharing inherent in them.
Instead of each unique animated mesh being driven by unique keyframes,
meshes are driven by "skeletons." This enables multiple meshes to share
skeletons and animations, saving memory.
Soya's Cal3D support doesn't allow you to share these resources because
of the way it stores Cal3D files: in individual directories. So when my
artist sends me half a dozen quaduped forest creatures that all share
the same skeleton and animation sets, I'm wasting disk space and memory
by having to break it all up into separate directories and duplicate the
skeleton and animation files.
Why isn't there a data/cal3d directory like there is for obj and 3ds?
And does Soya's internal implementation support properly sharing these
resources?
Thanks,
Vito
