I've implemented this feature but something weird about it is the following scenario (which would be common) ... if you have a parent joint that's scaled along, say the Z axis ... and you rotate a child joint that runs (initially) along the X axis ... then the logic result is the child will grow longer as it rotates to be more oriented along the Z axis.
This is the logical result, but it seems like an undesirable result to me. Is this how MD5 works for example?
I've implemented all of the features I have planned (a large number of them were unplanned that I had to implement just for completeness sake) and am now trying to wrap up my work just by doing a quick Linux test and publishing my code.
I will need to integrate the changes to this code base but I want to go ahead and publish first before that. I will do some patches over the next weeks including a solution to this Issue.
I've implemented this feature but something weird about it is the following scenario (which would be common) ... if you have a parent joint that's scaled along, say the Z axis ... and you rotate a child joint that runs (initially) along the X axis ... then the logic result is the child will grow longer as it rotates to be more oriented along the Z axis.
This is the logical result, but it seems like an undesirable result to me. Is this how MD5 works for example?
I've implemented all of the features I have planned (a large number of them were unplanned that I had to implement just for completeness sake) and am now trying to wrap up my work just by doing a quick Linux test and publishing my code.
I will need to integrate the changes to this code base but I want to go ahead and publish first before that. I will do some patches over the next weeks including a solution to this Issue.