Hi KE and Bwian

Quote Originally Posted by KnightErrant
@Bwian
Ok, inspiration IS striking. Just checked some dates on an e-mail
from GrumpyOldMan. 5-22-2007 he says we need to check rotations.
I find a problem with my quats to euler and euler to quats conversions.
I update my utility and voila! the feudal knight slashing animation is ok
now. Problem is, the dwarf animation .cas files I have are dated 5-21-2007
so I never applied the updated transformations to any of the cas files.

Your copy of my utility must also be outdated. This shouldn't make a difference
for small angles but maybe it is affecting the foot bone and lower leg for
animations. I've been updating my stuff all along to deal with the new
header/footers in Caliban's directory so I don't know how to backtrack
on this. Could you check the creation date on your copy of
animationlibrary.py and see if it is about 5-21-2007? Might help to narrow
down the culprit here. We can compare the algorithm in the function
computeeulers to be sure. Hope this might be it. Would make life
easier except I've got animmerge torn apart at the moment trying to
deal with the animations in new_2h_axe_halberd which have bones out
of order.
If you'd like a fresh (relatively speaking ) set of eyes to look over the anims, you could send me the basepose and one of the affected anims and I can run my multifocals over them.

With the new_2h_axe_halberd anim would you like me to extract it and do a cut and paste to get the anim working correctly? It's probably easier to do in milkshape ascii rather than try to get your converter working with a few rogue anims.

Just while I've got your attention, I've been chewing on the end of my pencil to get an overall view of how the template system will work. Basically I was going to set up the converter to extract and write templates from Milkshape files. How I was going to deal with those templates probably requires some user input. Converting from mesh to ms3d is fairly straightforward, after you select a mesh to convert you're then asked what template you'd like to apply. How we deal with the other conversions/mergers requires some thought though. One of my original ideas was to record the template as a fifth line in the model comments so that after the initial conversion everything was then automatic. I've had second thoughts now (but not after doing some extensive recoding - curses) and my inclination now is that the user specifies at merger or conversion to mesh what template they'd like to apply. This is a more flexible system because you won't be stuck with what was recorded at the initial conversion. Any input guys?

Cheers

GrumpyOldMan