We recently discovered this while developing our Dbpro plugin for loading Milkshape objects.
Some models scale during their animations in DBPro because the model file uses Matrix Key Frames and
requires DBpro to calculate the in-between frames of animation. DBPro uses Matrix interpolations to calculate
the in-between frames. Matrix interpolations do not correctly calculate rotations and can cause the geometry to be scaled.
In some cases the geometry can disappear altogether.
The simple solution is to export the model from your modeling program with position and rotation keys instead
of using matrix keys. DBPro correctly calculates the in-between frames using quaternions when a model uses position and rotation keys.
In most of the modeling programs to export with position and rotation keys just uncheck the matrix key export option.
We decided to post here rather than in the modeling forum because it is important for DBPro developers to be aware
of this when loading models as this relates to the way DBPro renders the animation. We have attached an example to show the difference.
Note: If a Model contains a Matrix Key for each frame of animation (including the in-between frames) DBPro does
not need to calculate the in-between frames and the model will not scale during animation. However storing all of the
in-between frames within the model file significantly increases its file size and the amount of ram required when loading
the model in DBPro.
EDIT:Forgot the attachment
[img]
[/img]
WindowsXP SP3,Vista,Windows 7 SP1, DBpro v7.7RC7
Stab In The Dark Editor
The coffee is lovely dark and deep,and I have code to write before I sleep.