Sign in to follow this  
bryanedds

OpenGL Having trouble with OpenGL matrices...

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();
	{
		glLoadMatrixf(camera.GetView());
		glPushMatrix();
		{
			glLoadMatrixf(camera.GetProjection());
			glPushMatrix();
			{
				glTranslatef(0, 0, -10);
				// render sphere - works, but probably shouldn't!

				glLoadMatrix(sphere.GetWorld());
				// 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 this post


Link to post
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 this post


Link to post
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 this post


Link to post
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 this post


Link to post
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 this post


Link to post
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);
glLoadMatrixf(camera->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);
glLoadMatrix(camera->view());
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 this post


Link to post
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!

Share this post


Link to post
Share on other sites

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

Sign in to follow this  

  • Announcements

  • Forum Statistics

    • Total Topics
      628345
    • Total Posts
      2982200
  • Similar Content

    • By test opty
      Hi all,
       
      I'm starting OpenGL using a tut on the Web. But at this point I would like to know the primitives needed for creating a window using OpenGL. So on Windows and using MS VS 2017, what is the simplest code required to render a window with the title of "First Rectangle", please?
       
       
    • By DejayHextrix
      Hi, New here. 
      I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc.... 
      I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn? 
      How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want? 
      Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn. 
      So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started. 
      Thanks, 
      Dejay Hextrix 
    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
       
       
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
      Thanks!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
      Thanks.
  • Popular Now