Jump to content

  • Log In with Google      Sign In   
  • Create Account

Skinning Matrices [Solved]


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
2 replies to this topic

#1 iLikeCarrots   Members   -  Reputation: 100

Like
0Likes
Like

Posted 20 April 2012 - 11:28 PM

I'm attempting to animate a skinned mesh with joints. I have looked at many different materials, and something isn't right with my understanding. All of my nodes hold a local and global matrix. When I load in the joints, I calculate the inverse pose matrix like so:

Pose Matrix = Mesh's Inverse Global * Joint Global
Inverse Pose Matrix = Inverse of Pose Matrix

Then when my joints are updated, I calculate the joint in mesh space and multiply it with the inverse pose matrix.

Joint wrt Mesh = Mesh's Inverse Global * Joint Global
Deform Matrix = Joint wrt Mesh * Inverse Pose Matrix

I uploaded the following video files to demonstrate what is happening to my mesh. Is my algorithm correct in handling the matrices in mesh space and calculating the inverse pose matrix? If I knew that, it would be easier to further study the problem.

Source animation..

My Results..

These are my references -
Introduction to Game Development
UCSD - Skinning powerpoint
Animation in Video Games

Sponsor:

#2 Lichtso   Members   -  Reputation: 118

Like
0Likes
Like

Posted 22 April 2012 - 05:47 AM

Hi, the solution in my game engine is the following:
struct Bone {
	Matrix4 staticMat;
	unsigned int jointIndex;
	std::string name;
	std::vector<Bone*> children;
};

struct Skeleton {
	Bone* rootBone;
	std::map<std::string, Bone*> bones;
};

struct BonePose {
	Matrix4 poseMat, dynamicMat;
};

class SkeletonPose {
	public:
	std::map<std::string, BonePose*> bonePoses;
	SkeletonPose(Skeleton* skeleton);
	~SkeletonPose();
	void calculateBonePose(Bone* bone, Bone* parentBone);
	void calculateDisplayMatrix(Bone* bone, Bone* parentBone, Matrix4* mats);
};

void SkeletonPose::calculateBonePose(Bone* bone, Bone* parentBone) {
	BonePose* bonePose = bonePoses[bone->name];
	bonePose->dynamicMat.setIdentity();
	if(parentBone) {
		bonePose->dynamicMat = bonePose->poseMat;
		bonePose->dynamicMat.translate(bone->staticMat.pos-parentBone->staticMat.pos);
		bonePose->dynamicMat *= bonePoses[parentBone->name]->dynamicMat;
	}else{ //Is root bone
		bonePose->dynamicMat = bonePose->poseMat;
		bonePose->dynamicMat.translate(bone->staticMat.pos);
	}
	for(unsigned int i = 0; i < bone->children.size(); i ++)
		calculateBonePose(bone->children[i], bone);
}

void SkeletonPose::calculateDisplayMatrix(Bone* bone, Bone* parentBone, Matrix4* mats) {
	Matrix4 mat;
	mat.setIdentity();
	mat.translate(bone->staticMat.pos*-1);
	mats[bone->jointIndex] = mat * bonePoses[bone->name]->dynamicMat;
	for(unsigned int i = 0; i < bone->children.size(); i ++)
		calculateDisplayMatrix(bone->children[i], bone, mats);
}



//Draw Frame

//Calculate the hierarchical transformations of the skeleton
skeletonPose->calculateBonePose(humanModel->skeleton->rootBone, NULL);

//Calculate the matrices used in the shader
Matrix4* mats = new Matrix4[skeleton->bones.size()];
skeletonPose->calculateDisplayMatrix(skeleton->rootBone, NULL, mats);
currentShaderProgram->setUniformMatrix4("jointMats", mats, skeleton->bones.size());
delete [] mats;
for(unsigned int i = 0; i < meshes.size(); i ++)
	meshes[i]->draw();

I hope you can understand my code Posted Image.

#3 iLikeCarrots   Members   -  Reputation: 100

Like
0Likes
Like

Posted 22 April 2012 - 11:23 AM

Thank you - I'll look over this and see where my code differs. Posted Image

EDIT: I found that my code is correct, but I didn't notice that all of the joints were using global positions, which is why the rotations appear to be offset. In Modo 401 'weightmap deformers' were used to rig geometry, and I didn't realize that the center of all the deformers was zero while the pivot position was always relative to the model center.




Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS