Thanks for the tips. So are the files you mentioned (tr_animation.c,
tr_surface.c, etc.) the current Icculus files or are you referring to
the EF source code files there?<br><br><div><span class="gmail_quote">On 2/28/06, <b class="gmail_sendername">Thilo Schulz</b> <<a href="mailto:arny@ats.s.bawue.de">arny@ats.s.bawue.de</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tuesday 28 February 2006 17:04, Tim Stowell wrote:<br>> I may have used the wrong term, but I was thinking of the ability to blend<br>> one animation into another, i.e. blend from running animation to jumping in<br>
> a smooth transition dynmaically as a lot of games can do. Maybe this is<br>> already handled in the engine, but I would appreciate any input.<br><br>Yes, you have to take care of the "transitions", but the way this is being
<br>done has not been changed, as far as I can tell looking at the EF source<br>code. The engine does some basic lerping between animation frames. It only<br>needs to be told which frame to lerp from.<br><br>I suggest you take a look at renderer/tr_animation.c (MD4 format),
<br>renderer/tr_surface.c (the lerping functions for MD3 format) and<br>cgame/cg_players.c to see what is basically being done :)<br>The engine only understands a few variables you can use to control animation:<br>The current frame (frame), oldorigin, oldframe (previous played frame) and
<br>backlerp, the latter being used to indicate how far we've gone into animating<br>from the old to the new frame and uses that to do a linear interpolation from<br>the old bone position (or vertex coordinates in the MD3 format) to the new
<br>one.<br><br>--<br>Thilo Schulz<br><br><br></blockquote></div><br>