Avatars group

[Marco Gillies]

Hi,

testing the google group email

I have looked at Cal3d and thought of some things that we should probably do to the core:

* implement repositioning (so that a motion starts at the exact place the previous one ends). This would involve adding a new blending method
* using that implement a motion queuing system
* use the queue to implement motion graphs (though maybe the graphs themselves should be an external library
* Use motion graphs to build various behaviours like path following and proxemics

Marco

[Jeren Chen]

I would definitely agree that repositioning and motion queuing are key features to concatenate motions and should be considered to implement in the core.

I would also agree that motion graphs should be separated from the Cal3D core before we have a generic version. Perhaps we can first come up with an interface so that users can use motion graphs from different implementations with the same mechanism? This may involve a mograph file format (I am looking into the Boost graph library for this) and a motion query interface.

Jeren