IQM and animating on the QC side
Moderator: InsideQC Admins
17 posts
• Page 2 of 2 • 1, 2
by mh » Wed Oct 27, 2010 12:00 am
Or store them in the model and just send a frame number same as before. AlienArena's IQM does this and it seems to work quite well. Of course you don't have complete freedom to manipulate bones in gamecode this way (and therefore lose the whole "animating on the QC side" thing), but it seems an acceptable halfway point.
We had the power, we had the space, we had a sense of time and place
We knew the words, we knew the score, we knew what we were fighting for
We knew the words, we knew the score, we knew what we were fighting for
-
mh - Posts: 2292
- Joined: Sat Jan 12, 2008 1:38 am
by mankrip » Wed Nov 10, 2010 5:28 am
A middle ground would be to not define values for all joints on each frame, but only the values for the specific joints that needs to be changed, with the others being set according to a kind of "priority list" defined into the model.
Example:
self.frame = $rockrun1; // always sets the animation for the legs, but only sets the animation for the rest of the body if the previous self.frame is either $stand* or $axstnd*
However, it would probably be a pain to code support for this into the engine.
Example:
self.frame = $rockrun1; // always sets the animation for the legs, but only sets the animation for the rest of the body if the previous self.frame is either $stand* or $axstnd*
However, it would probably be a pain to code support for this into the engine.
-
mankrip - Posts: 915
- Joined: Fri Jul 04, 2008 3:02 am
17 posts
• Page 2 of 2 • 1, 2
Who is online
Users browsing this forum: No registered users and 1 guest