# OpenGL from matrix to radians

## Recommended Posts

QuadMV    168
I have a 4x4 matrix with the orientation and location of an object. It's a ms directx style matrix (I think it's the opposits of opengl if I remember correctly) Anyway, how do I convert my orrientation into radians (or degrees) along any of the 3 axis? For my specific instance I want to determine how far I'm rotated around the Y axis, so I can convert that to a compass heading. Thanks

#### Share this post

##### Share on other sites
d000hg    1199
Well you can get the local X, Y and Z axes and the world position of the local origin from the matrix using:
D3DXMATRIX m = GenerateYourMatrix();D3DXVECTOR3 X(m._11,m._12,m._13);D3DXVECTOR3 Y(m._21,m._22,m._23);D3DXVECTOR3 Z(m._31,m._32,m._33);D3DXVECTOR3 Pos(m._41,m._42,m._43);

This relies on there being no scaling.

But generating this back to Euler angles is a bit tricky. I recommend you look here although I don't know which way rounf their matrices are and I don't have time to check. But if you look at the previous point that may help you...

#### Share this post

##### Share on other sites
QuadMV    168
Yes, I actually had that doc, and created the GetEular function. However, I see some wierd behavior. I suspect I'm missing another step in using eular angles?

It seems to flip flop every 90 degrees, so if I try and rotate around the y axis, it seems to flip as I cross the X or Z axis. I kind of understand what it's doing, but I don't know the math to compinsate so I get an ever incrementing value from 0-360 (or 0-3.14 (that's rads right?)) without flip flop? I'm trying to display my heading or compass reading.

Do I somehow need to combine the x and z eular angles to get a consistent reading as I rotate around the Y, or should the y eular angle be sufficient?

Thanks

#### Share this post

##### Share on other sites
Drakex    273
Here's the function I use, translated to C++. I hope I've got it right (I never really used references in C++).

void eulerAnglesFromMatrix(D3DXMATRIX& mat, float& x, float& y, float& z){	if(mat.m[2][1]>1)		mat.m[2][1]=1;	if(mat.m[2][1]<-1)		mat.m[2][1]=-1;	x=asin(mat.m[2][1]);	const double epsilon=0.01;	if(x+epsilon<(3.1415926535/2))	{		if(x-epsilon>(-3.1415926535/2))		{			z=atan2(-mat.m[0][1],mat.m[1][1]);			y=atan2(-mat.m[2][0],mat.m[2][2]);		}		else		{			z=-atan2(mat.m[0][2],mat.m[0][0]);			y=0;		}	}	else	{		z=atan2(mat.m[0][2],mat.m[0][0]);		y=0;	}	x=-x;	y=-y;	z=-z;}

It works well. I had the flip-flop problem with some other methods as well. The epsilon in this method is to counter a strange problem when the object is pointing in one of the cardinal directions, and it is kind of indeterminate as to which solution to use, so the epsilon skews the result to one side or the other. Lastly, the checks on mat.m[2][1] at the beginning are because of floating point inaccuracies - sometimes that element can be something like 1.0000001, when it really should be 1.0, and atan2() will then return a NAN.

[Edited by - Drakex on July 21, 2005 11:13:14 AM]

#### Share this post

##### Share on other sites
QuadMV    168
DrakeX,

That worked perfectly. I wish I understood the math, and why the document in http://skal.planet-d.net/demo/matrixfaq.htm#Q37 doesn't work, considering it seems to be a very popular document, but thanks.

Also, you're returning more of a radian value than a eular angle, right? It seems to be +/- pi/2, right? I actually wanted radians, so it works for me.

#### Share this post

##### Share on other sites
Drakex    273
I know, that document seems to be very popular, and it's never worked correctly for me. I think it's because of rotation order - different rotation orders require different ways of getting the angles out of the matrix. We both seem to be using YXZ :)

The function I posted does return radians, yes. If you're wondering about the name of the function, it does return degrees in my project, but I just removed that conversion for you.

#### Share this post

##### Share on other sites
thedodgeruk    124
[quote name='Drakex' timestamp='1121850834' post='3165384']
Here's the function I use, translated to C++. I hope I've got it right (I never really used references in C++).

void eulerAnglesFromMatrix(D3DXMATRIX& mat, float& x, float& y, float& z)
{
if(mat.m[2][1]>1)
mat.m[2][1]=1;
if(mat.m[2][1]<-1)
mat.m[2][1]=-1;
x=asin(mat.m[2][1]);
const double epsilon=0.01;
if(x+epsilon<(3.1415926535/2))
{
if(x-epsilon>(-3.1415926535/2))
{
z=atan2(-mat.m[0][1],mat.m[1][1]);
y=atan2(-mat.m[2][0],mat.m[2][2]);
}
else
{
z=-atan2(mat.m[0][2],mat.m[0][0]);
y=0;
}
}
else
{
z=atan2(mat.m[0][2],mat.m[0][0]);
y=0;
}

x=-x;
y=-y;
z=-z;
}

It works well. I had the flip-flop problem with some other methods as well. The epsilon in this method is to counter a strange problem when the object is pointing in one of the cardinal directions, and it is kind of indeterminate as to which solution to use, so the epsilon skews the result to one side or the other. Lastly, the checks on mat.m[2][1] at the beginning are because of floating point inaccuracies - sometimes that element can be something like 1.0000001, when it really should be 1.0, and atan2() will then return a NAN.

[Edited by - Drakex on July 21, 2005 11:13:14 AM]
[/quote]

cheers , this solved a problem that i had

## Create an account or sign in to comment

You need to be a member in order to leave a comment

## Create an account

Sign up for a new account in our community. It's easy!

Register a new account

## Sign in

Already have an account? Sign in here.

Sign In Now

• ### Similar Content

• Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
Skype: Mangodoor408
• By tyhender
Hello, my name is Mark. I'm hobby programmer.
So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine).
And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
Sorry for late replies.
I mostly give more information when people PM me,but this post is REALLY short,even for me =D
So here's few more points:
Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me.

• By Zaphyk
I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?

• I'm trying to get some legacy OpenGL code to run with a shader pipeline,
The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
I've got a version 330 vertex shader to somewhat work:
#version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
Question:
What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?

Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.

• Hi i am new to this forum  i wanted to ask for help from all of you i want to generate real time terrain using a 32 bit heightmap i am good at c++ and have started learning Opengl as i am very interested in making landscapes in opengl i have looked around the internet for help about this topic but i am not getting the hang of the concepts and what they are doing can some here suggests me some good resources for making terrain engine please for example like tutorials,books etc so that i can understand the whole concept of terrain generation.

• 20
• 15
• 17
• 10
• 18