# OpenGL Having trouble with OpenGL matrices...

This topic is 3375 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

## Recommended Posts

Hello all, I just started learning some OpenGL coming from XNA. I'm trying to get my Matrix struct to be aligned how glLoadMatrixf expects. Here's the relevant parts -
	struct Matrix
{
float
M11, M12, M13, M14,
M21, M22, M23, M24,
M31, M32, M33, M34,
M41, M42, M43, M44;

operator float*();
};

I know that the fields are supposed to be in column-major order, but I'm not sure if this particular order is column-major or not. I think it's not, but when I transpose them, my rendering no longer works. Additionally, I'm not sure if I'm pushing the model, view, and projection matrices in the proper order while rendering. It works when I use glTranslatef, but not when I push my own world matrix instead. Here's my current attempt -
	glPushMatrix();
{
glPushMatrix();
{
glPushMatrix();
{
glTranslatef(0, 0, -10);
// render sphere - works, but probably shouldn't!

// render sphere - doesn't work...
}
glPopMatrix();
}
glPopMatrix();
}
glPopMatrix();

This seems to work, but like I said, when I try transposing the Matrix so that it's seemingly in column-major order, everything breaks down. Anyone have any clues as to what all is going wrong here? Thanks!

##### Share on other sites
You also don't need to use glPushMatrix unless you want to "rewind" the stack to a previous state.

##### Share on other sites
Ok, I have things reformed to what I believe was the suggestion.

Here is a snipped of my current Matrix code -

	struct Matrix	{		operator float*();		float			M11, M21, M31, M41,			M12, M22, M32, M42,			M13, M23, M33, M43,			M14, M24, M34, M44;	};

And here is a snippet of my drawing code -

	glMatrixMode(GL_MODELVIEW);	glLoadIdentity();	glMultMatrixf(Matrix::Transpose(camera.GetProjection()));	glMultMatrixf(Matrix::Transpose(camera.GetView()));	glPushMatrix();	{		glMultMatrixf(Matrix::Transpose(sphereView.GetTransform().GetWorldTransform()));		sphereView.Draw(timeElapsed);	}	glPopMatrix();

My question is: why do I have to transpose each matrix while drawing? My struct now has the fields in column-major order. Any ideas?

[Edited by - bryanedds on November 23, 2008 1:05:39 AM]

##### Share on other sites
In the second post, you simply changed the matrix element names, opengl doesnt refer to these. Transpose, GetProjection() and friends are still probably copying row1 in the first 4, row2 into the next 4, etc. What opengl understands is 16 elements with col1 in the first 4, etc.

float gl[16];
gl[0] = m.r1c1; gl[4] = m.r1c2; gl[8] = m.r1c3; gl[12] = m.r1c4;
gl[1] = m.r2c1; gl[5] = m.r2c2; gl[9] = m.r2c3; gl[13] = m.r2c4;
gl[2] = m.r3c1; gl[6] = m.r3c2; gl[10] = m.r3c3; gl[14] = m.r3c4;
gl[3] = m.r4c1; gl[7] = m.r4c2; gl[11] = m.r4c3; gl[15] = m.r4c4;

thats why the transpose is still needed, opengl doesnt care what you call you matrix class elements. Best to leave them named correctly like the first post, then do the above;

##### Share on other sites
Consider this part of the implementation -

	Matrix::operator float*()	{		return reinterpret_cast<float*>(this);	}

Consider that I'm passing the result of this reinterpret_cast to the gl function directly. From my eye, I didn't change the names of the fields inasmuch as I changed their order inside the struct. To my thinking, therefore, the order in which the fields are declared in the struct do matter. That is, if I do m[1][2] on this reinterpret_casted pointer, it should come out in the expected column-major alignment.

Please let me know if this is not the case :)

##### Share on other sites
Quote:
 This seems to work, but like I said, when I try transposing the Matrix so that it's seemingly in column-major order, everything breaks down.

Column-major vs. row-major is simply semantics. Te important part is that you are consistent in all operations. If your code works with opengl without transposing that means that internally you use column-major matrices and operations (withhout realizing it), and simply have mis-named the values.

##### Share on other sites
1) Supplying OpenGL with matrices is usually done in 2 steps. The projection is set-up usually like here:
glMatrixMode(GL_PROJECTION);
It is often done once, since most application need not change the projection afterwards. The model-view matrix is composed from the view matrix and the model matrices, and often varies from frame to frame, so it is set-up each time at the beginning of the rendering loop:
glMatrixMode(GL_MODELVIEW);
glPushMatrix();
glMultMatrix(someModel->worldFrame());
glPopMatrix();
where the latter 3 lines are repeated for each model that is rendred (it may be more complex, e.g. if deeper frame nesting is used).

2) Mathematically OpenGL uses column vectors with the homogeneous component at the 4th place. A matrix looks like:
[ Rxx Ryx Rzx Tx ][ Rxy Ryy Rzy Ty ][ Rxz Ryz Rzz Ty ][  0   0   0   1 ]
what can be interpreted as [Rxx Rxy Rxz]t denoting the x direction vector, [Ryx Ryy Ryz]t denoting the y direction vector, [Rzx Rzy Rzz]t denoting the z direction vector, and [Tx Ty Tz]t denoting the position. (Here the super-posed t denotes the transpose operator, since I wrote the column vectors as rows; its just for a convenient writing.)

Such a 2D construct has to be mapped to the 1D (linear) computer memory. OpenGL uses the column major order, what means that it walks down a column before it goes to the next one. In summary that means a layout like
Rxx Rxy Rxz 0 Ryx Ryy Ryz 0 Rzx Rzy Rzz 0 Tx Ty Tz 1

Now, if you remember back, D3D uses row vectors as well as row-major order. Notice please that both kinds of handling are changed! That means that the same matrix as above has to be transposed to yield in the mathematical representation:
[ Rxx Rxy Rxz 0 ][ Rxy Ryy Ryz 0 ][ Rzx Rzy Rzz 0 ][ Tx  Ty  Tz  1 ]

When mapping this in row major order to a linear memory, you'll get
Rxx Rxy Rxz 0 Ryx Ryy Ryz 0 Rzx Rzy Rzz 0 Tx Ty Tz 1
what is unsurprisingly the same as with OpenGL. I write "unsurprisingly" because both the vector kind as well as the order kind are changed so that both changes annul each other.

Hence, it is senseful to use the above layout. Notice please that this is nevertheless not the only possible layout. E.g. Collada uses an incompatible layout.

I hope that has cleared the issue.

EDIT: 2 syntax errors corrected.

[Edited by - haegarr on November 24, 2008 6:07:56 AM]

##### Share on other sites
haegar,

Wonderful post! Thank you so much for the time you put it into it! I have things working perfectly now. Thank you as well snoutmate and yngvedh!

Here's my final Matrix snippet -
	struct Matrix	{		float			M11, M12, M13, M14,			M21, M22, M23, M24,			M31, M32, M33, M34,			M41, M42, M43, M44;		operator float*();	};

Here's my final rendering code -
	glMatrixMode(GL_PROJECTION);	glLoadMatrixf(camera.GetProjection());	glMatrixMode(GL_MODELVIEW);	glLoadMatrixf(camera.GetView());	glPushMatrix();	{		glMultMatrixf(sphereView.GetTransform().GetWorldTransform());		sphereView.Draw(timeElapsed);	}	glPopMatrix();

Thank you again to everyone!

• 10
• 12
• 10
• 10
• 11
• ### Similar Content

• Good Evening,
I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
I am really stucked right now because of the fundamental question:
Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on.
In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
Should I treat those debug objects as entities/components?
For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
Regards,
LifeArtist
• By QQemka
Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
Let's go:
Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
There were several more but i forgot/solved them at time of writing
• By RenanRR
Hi All,
I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
#version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);
So, some doubts:
- Why use it like that?
- Is it okay to manipulate the camera that way?
-in this way, are not the vertex's positions that changes instead of the camera?
- I need to pass MVP to all shaders of object in my scenes ?

What it seems, is that the camera stands still and the scenery that changes...
it's right?

Thank you

• Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

int rgbValue = int(textureSample.w);//4 bytes of data packed as color
// algorithm might not be correct and endianness might need switching.
vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
extractedData /= 255.0f;

• While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
Anyone has any idea .. what should I do?