# OpenGL Simple OpenGL matrix question

## Recommended Posts

Deliverance    387
I'm kind of confused about how opengl matrices work. Say i have a rotation around the Z axis. _mij are sequential in memory, that is _m12 follows immediately after _m11 and _m21 follows just after _m14.

_m11 = cosAngle; _m12 = sinAngle; _m13  = 0.0f; _m14 = 0.0f;
_m21 = -sinAngle; _m22 = cosAngle; _m23 = 0.0f; _m24 = 0.0f;
_m31 = 0.0f; _m32 = 0.0f; _m33 = 1.0f; _m34 = 0.0f;
_m41 = 0.0f; _m42 = 0.0f; _m43 = 0.0f; _m44 = 1.0f;


If i load this with glLoadMatrixfv i obtain the same results as when calling glRotatef(30,0,0,1).When calling glGetFloatf with GL_MODELVIEW_MATRIX i obtain the same results with both methods(glLoadMatrixf and glRotatef). But if i want to correctly transform a column vector and obtain the same results as when opengl transforms it with this matrix i have to post multiply with the my matrix, like this: transformedVertex = Transpose(Transpose(transformedVertex) * myMatrix). but opengl Premultiplies a vector with a matrix like this: transformedVertex = myMatrix * transformedVertex. Why is this difference? Does OpenGL store my matrix inverted in memory? What about retriveal of the matrix from OpenGL?

##### Share on other sites
Brother Bob    10344
The matrix you show, given the linear order of the elements, is a row-major matrix. Elements are linearized row by row. OpenGL's matrices are column major, and they are the transpose of what you presented aswell.

This transposed and majorness change cancel each other, which means you can upload the matrix stored in row-major order, and get the same result as OpenGL's rotation matrix stored in column-major order.

There will, however, be a difference if you try to multiply the matrices something. The matrix you show must be multiplied by a row vector on the left hand side to get the same result as OpenGL, which multiplies a column-vector on the right side.

##### Share on other sites
Deliverance    387
Quote:
 Original post by Brother BobThe matrix you show, given the linear order of the elements, is a row-major matrix. Elements are linearized row by row. OpenGL's matrices are column major, and they are the transpose of what you presented aswell.This transposed and majorness change cancel each other, which means you can upload the matrix stored in row-major order, and get the same result as OpenGL's rotation matrix stored in column-major order.There will, however, be a difference if you try to multiply the matrices something. The matrix you show must be multiplied by a row vector on the left hand side to get the same result as OpenGL, which multiplies a column-vector on the right side.

Please excuse my noobiness but i did not catch it completely. Say i have this matrix in row major order(laid continous in memory):

X.x X.y X.z t.x
Y.x Y.y Y.z t.y
Z.x Z.y Z.z t.z
0 0 0 1

I need to convert it to column major order(laid continous in memory):
X.x Y.x Z.x 0
X.y Y.y Z.y 0
X.z Y.z Z.z 0
t.x t.y t.z 1

Now what?! As far as i understand OpenGL stores the basis vectors one after another in memory and if this would be so then it effectively becomes:
X.x X.y X.z t.x
Y.x Y.y Y.z t.y
Z.x Z.y Z.z t.z
0 0 0 1

which is the form we started with in the first place.
Is this right?! :D

##### Share on other sites
Brother Bob    10344
The matrix you presented in your original post is a row base vector matrix and must be transposed to match the matrices used by OpenGL. Base vectors in OpenGL are column. So a matrix for a rotation about the Z-axis is in OpenGL is (s and c means sine and cosine of the angle to rotate):
c -s  0  0s  c  0  00  0  1  00  0  0  1

This is transposed to your matrix. Linearize this in column-major order, you get this array.
c  s  0  0 -s c  0  0  0  0  1  0  0  0  0  1

If you linearize your matrix in row-major order, you get the same memory layout (which is why you can pass "double-wrong" to OpenGL and get correct result), but multiplication with a column vector to the right is different, because the matrices are transposed.

##### Share on other sites
Deliverance    387
Quote:
 Original post by Brother BobThe matrix you presented in your original post is a row base vector matrix and must be transposed to match the matrices used by OpenGL. Base vectors in OpenGL are column. So a matrix for a rotation about the Z-axis is in OpenGL is (s and c means sine and cosine of the angle to rotate):c -s 0 0s c 0 00 0 1 00 0 0 1This is transposed to your matrix. Linearize this in column-major order, you get this array.c s 0 0 -s c 0 0 0 0 1 0 0 0 0 1If you linearize your matrix in row-major order, you get the same memory layout (which is why you can pass "double-wrong" to OpenGL and get correct result), but multiplication with a column vector to the right is different, because the matrices are transposed.

YEY! I finally understand it! I've been struggling with this thing for quite a time :D.

## 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

• ### Similar Content

• 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.

• By KarimIO
Hey guys. I'm trying to get my application to work on my Nvidia GTX 970 desktop. It currently works on my Intel HD 3000 laptop, but on the desktop, every bind textures specifically from framebuffers, I get half a second of lag. This is done 4 times as I have three RGBA textures and one depth 32F buffer. I tried to use debugging software for the first time - RenderDoc only shows SwapBuffers() and no OGL calls, while Nvidia Nsight crashes upon execution, so neither are helpful. Without binding it runs regularly. This does not happen with non-framebuffer binds.
GLFramebuffer::GLFramebuffer(FramebufferCreateInfo createInfo) { glGenFramebuffers(1, &fbo); glBindFramebuffer(GL_FRAMEBUFFER, fbo); textures = new GLuint[createInfo.numColorTargets]; glGenTextures(createInfo.numColorTargets, textures); GLenum *DrawBuffers = new GLenum[createInfo.numColorTargets]; for (uint32_t i = 0; i < createInfo.numColorTargets; i++) { glBindTexture(GL_TEXTURE_2D, textures[i]); GLint internalFormat; GLenum format; TranslateFormats(createInfo.colorFormats[i], format, internalFormat); // returns GL_RGBA and GL_RGBA glTexImage2D(GL_TEXTURE_2D, 0, internalFormat, createInfo.width, createInfo.height, 0, format, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); DrawBuffers[i] = GL_COLOR_ATTACHMENT0 + i; glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0 + i, textures[i], 0); } if (createInfo.depthFormat != FORMAT_DEPTH_NONE) { GLenum depthFormat; switch (createInfo.depthFormat) { case FORMAT_DEPTH_16: depthFormat = GL_DEPTH_COMPONENT16; break; case FORMAT_DEPTH_24: depthFormat = GL_DEPTH_COMPONENT24; break; case FORMAT_DEPTH_32: depthFormat = GL_DEPTH_COMPONENT32; break; case FORMAT_DEPTH_24_STENCIL_8: depthFormat = GL_DEPTH24_STENCIL8; break; case FORMAT_DEPTH_32_STENCIL_8: depthFormat = GL_DEPTH32F_STENCIL8; break; } glGenTextures(1, &depthrenderbuffer); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); glTexImage2D(GL_TEXTURE_2D, 0, depthFormat, createInfo.width, createInfo.height, 0, GL_DEPTH_COMPONENT, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, depthrenderbuffer, 0); } if (createInfo.numColorTargets > 0) glDrawBuffers(createInfo.numColorTargets, DrawBuffers); else glDrawBuffer(GL_NONE); if (glCheckFramebufferStatus(GL_FRAMEBUFFER) != GL_FRAMEBUFFER_COMPLETE) std::cout << "Framebuffer Incomplete\n"; glBindFramebuffer(GL_FRAMEBUFFER, 0); width = createInfo.width; height = createInfo.height; } // ... // FBO Creation FramebufferCreateInfo gbufferCI; gbufferCI.colorFormats = gbufferCFs.data(); gbufferCI.depthFormat = FORMAT_DEPTH_32; gbufferCI.numColorTargets = gbufferCFs.size(); gbufferCI.width = engine.settings.resolutionX; gbufferCI.height = engine.settings.resolutionY; gbufferCI.renderPass = nullptr; gbuffer = graphicsWrapper->CreateFramebuffer(gbufferCI); // Bind glBindFramebuffer(GL_DRAW_FRAMEBUFFER, fbo); // Draw here... // Bind to textures glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, textures[0]); glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, textures[1]); glActiveTexture(GL_TEXTURE2); glBindTexture(GL_TEXTURE_2D, textures[2]); glActiveTexture(GL_TEXTURE3); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); Here is an extract of my code. I can't think of anything else to include. I've really been butting my head into a wall trying to think of a reason but I can think of none and all my research yields nothing. Thanks in advance!

• Hi everyone, I've shared my 2D Game Engine source code. It's the result of 4 years working on it (and I still continue improving features ) and I want to share with the community. You can see some videos on youtube and some demo gifs on my twitter account.
This Engine has been developed as End-of-Degree Project and it is coded in Javascript, WebGL and GLSL. The engine is written from scratch.
This is not a professional engine but it's for learning purposes, so anyone can review the code an learn basis about graphics, physics or game engine architecture. Source code on this GitHub repository.
I'm available for a good conversation about Game Engine / Graphics Programming
• By C0dR
I would like to introduce the first version of my physically based camera rendering library, written in C++, called PhysiCam.
Physicam is an open source OpenGL C++ library, which provides physically based camera rendering and parameters. It is based on OpenGL and designed to be used as either static library or dynamic library and can be integrated in existing applications.

The following features are implemented:
Physically based sensor and focal length calculation Autoexposure Manual exposure Lense distortion Bloom (influenced by ISO, Shutter Speed, Sensor type etc.) Bokeh (influenced by Aperture, Sensor type and focal length) Tonemapping
You can find the repository at https://github.com/0x2A/physicam

I would be happy about feedback, suggestions or contributions.

• 12
• 10
• 18
• 9
• 9