The short and to the point version: I have the 3 axes (the X, Y and Z axes) describing the orientation of an object. The information I have is in the form of a vector for each axis. These vectors are not normalized but I can do that if needed. What I want to get is the equivalent yaw, pitch and roll that would create the same orientation, using that information. The gorey details (in case I am asking the question wrongly): I am trying to load models from 3DS files into my game engine. I have all the vertices, materials and textures working The only thing left is to transform the model into position. Each 3DS file can contain multiple meshes, each with their own transformation matrix (e.g. one for the arm of a character, one for the head etc. to allow skeletal animation hopefully). According to the official 3DS SDK, the mesh matrix is a: "3-by-4 matrix describing object orientation. Used by the Keyframer to determine object rotation and center" According to another source, this matrix is in the following format: " vector X1 vector X2 vector X3 vector O X1, X2 and X3 represent the axes, O the origin." At least I can deal with that origin But the axes do not work with my existing engine, it does all transformations using (via the external interface) yaw, pitch and roll (but internally it stores it as a D3DMATRIX which is a 4 x 4 matrix, which I could access if neccessary). I don't expect someone to post a whole solution and mathmatical proof here, but any help would be appreciated because its the last piece of the puzzle for me! Even some words to google would help, because I'm not even sure what I should be looking for (scary words like quaternions come to mind, is that related to this problem at all?). Or maybe some links to tutorials. Thanking the clever dude who answers this in advance, - Bazee [edited by - bazee on September 16, 2002 3:09:02 PM]

Im not 100% positive about this, but this is what i understand from my linear algebra course:

well, a 4x4 transformation matrix basically consists of 4 column vectors:

[v1 v2 v3 T]

where v1=[x1.x x1.y x1.z 0] transposed.
v2=[x2.x x2.y x2.z 0] transposed.
v3=[x3.x x3.y x3.z 0] transposed.
T=[O.x O.y O.z 1] transposed.

to recap: v1, v2, v3 and T are columns. If that doesnt work, transpose the matrix (i believe DX uses a transposed one). One warning though... this does not always have to be an orthogonal orientation. nor does it have to be free of scaling. In other words, file could contain a skewed matrix, or a matrix that stretches the model... you can always make sure that the axis are normalized to remove scaling. But to remove skewing, you must choose one vector to stay constant and choose others using it.


Good Luck,
Salman.

Thanks for your answer! :-) It''s all making sense now, I thought it was strange that it contained no scaling information, but ofcourse the scale is defined by the magnitude of the axis vectors. I''m going to try your suggestion and see if it works. If you''re correct, the problem was simpler than I thought, and I feel ignorant not knowing this stuff already.

Oh dear before the arms were slightly bent, but now all bits of body are just exploded everywhere in random directions! I think your suggestion is probably correct, I''m just doing something wrong. I think it''s because I am misunderstanding. In particular, I don''t understand

quote:
But to remove skewing, you must choose one vector to stay constant and choose others using it.

and also what does the word transpose mean?

Anybody else have any other ideas? Thanks

OK, I''ve been reading the DX SDK very carefully and I''m beginning to understand more but still not getting any correct results, even though I''ve tried everything. I can see why the axes might be skewed and how to solve that, although I don''t really mind. If the file is skewed I''ll assume it''s done for a reason. In my basic test model, theres no skewed axes anyway.

What on earth is wrong with this thread?

Hmm seems the forum bug was fixed Now can anybody answer my question?

I decided to try various freeware and shareware 3DS file viewers, and guess what, they ALL have the same bug as my engine! So I guess it''s a difficult problem that very few people know how to fix. Except when I load the files in 3DS Max, they look correct.

Thankyou Yann

The way you''ve drawn that matrix, is like 90 degrees rotated from the way the DirectX SDK draws it. I think thats just a difference in your style, I doubt I''m filling my matrices in the wrong side up (I''ve tried both ways just in case).

What does transpose actually mean? I know theres a D3DXMatrixTranspose function, and I''ve tried using it in all sorts of places, but what does it do?

3DS files have no object hierachy. There are "chunks" and even though these chunks are nested inside each other in a hierachy, no mesh or object chunk is allowed to contain another mesh or object (according to the 3DS SDK, and also all my test files comply to that rule). So if the matrices are not relative to world space (rather than parent object space), it will be impossible for me to find the real locations of objects.

I''m not too concerned if the conversion process loses some accuracy, because I will only do this conversion upon loading, not every frame.

What my screen looks like now for example: I load a character, most of it is OK, but an arm or leg might be totally bent in the wrong direction. If I load the file in 3DS Max, it looks OK. The really discouraging thing is as I said, any other 3DS viewer (yes even commerical ones) also show the bent version in the exact same position as my engine does.

I''ll keep working at it!