Ok, now that is making a lot more sense. So rather than the frame
controlling vertex positions as in md3, in md4, the frame stores the
position of the bone which then deforms during gameplay?<br><br><div><span class="gmail_quote">On 1/27/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 Friday 27 January 2006 18:32, Tim Stowell wrote:<br>> That makes sense. I guess I'm a bit confused, as I thought the model format
<br>> itself was the same as that used by the EliteForce models, and that to use<br>> the skeletal model system at all required a change to cgame.<br><br>I am quite sure that the most significant changes are limited to the loading
<br>of the models themselves. Other areas, like doing the animations don't need<br>many changes.<br>Like the original md3 format the md4 format uses frames. In MD4 it's the<br>position of each bone that is saved.<br>The current frame number is stored in the
backend.currentEntity->e structure<br>of the renderer. It is up to the cgame to select which frame is to be played<br>at the moment.<br><br>--<br>Thilo Schulz<br><br><br></blockquote></div><br>