• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
ehsan2004

OpenGL
row major vs.column major

9 posts in this topic

If we send a row major matrix to glMultMatrix() and again get the matrix using glGet() function, we get the same matrix. For example 12th, 13th and 14th elements always consist of translation elements for both row major and column major matrices. But here's a quote from the book "More OpenGL game programming": Also note that the product of the projection matrices is transposed before being passed to glTexGenv(). This is necessary because all three matrices store data in column major order. After transposing, the result is in row major order which is what glTexGenfv() expects. ... The author uses this way to get the projection matrix: gluPerspective( fovy, aspect_ratio, 1, 100 ); glGetFloatv( GL_PROJECTION_MATRIX, ( GLfloat*)&mat4_projection ); But I'm wondering! Both row major and column major matrices store the data the same way. ( m[0], m[1], etc ). But the way that they deal with rows or columns is different. I have seen an Open Source example that simply works with row major matrices and pre multiplies them and then sends the result to glMultMatrix(). I guess that something is going wrong in his article.
0

Share this post


Link to post
Share on other sites
But he just gets the result from OpenGL:

gluPerspective( fovy, aspect_ratio, 1, 100 );
glGetFloatv( GL_PROJECTION_MATRIX, ( GLfloat*)&mat4_projection );

So we don't need to transpose it.

OpenGL always store the translation elements in 12ths, 13th and 14th elements:

array[12] = x

array[13] = y

array[14] = z

array[15] = 1

I have tried it, OpenGL uses row major matrices, but the first row is m[0], m[4], m[8] and m[12] for example.

I guess passing the result to glTexGen() is independent of row major and column major matrices( Assuming that we work with row major ordering ).

The second argument of glTexGen() in his example is GL_EYE_PLANE, So I guess that we need to transpose the matrix to send the correct "plane equation" to this function.
You can find his source code here:
http://glbook.gamedev.net/moglgp/code.asp
Download chapter 5 and search for projective texturing.

[Edited by - ehsan2004 on March 28, 2010 8:51:25 AM]
0

Share this post


Link to post
Share on other sites
Wavarian, are you sure?

src/mesa/main/matrix.c: * -# 4x4 transformation matrices are stored in memory in column major order.
0

Share this post


Link to post
Share on other sites
Quote:
Original post by tori
Wavarian, are you sure?

src/mesa/main/matrix.c: * -# 4x4 transformation matrices are stored in memory in column major order.


I read some comments from the OpenGL moderator that both row major and column major matrices use the same 1D array.

But the first row of row major matrices are m[0],m[1], m[2] and m[3] and the first row of column major matrices are m[0], m[4], m[8] and m[12]. After computing the matrix mathes( whether we use row major or column major ) , the values of m[0] to m[15] are the same for both matrices ( OpenGL uses post multiplication and DirectX uses Pre multiplication, so we get the same results ).

0

Share this post


Link to post
Share on other sites
The quote from that book seems to be out of context. It sounds like the author is manually inverting the matrix before sending it to OpenGL rather than expecting OpenGL to invert it or him. Note that there's no way for OpenGL to know if a matrix (given as a 1D array) is row- or column-major, so there's no way for it to know whether to invert your matrix.
0

Share this post


Link to post
Share on other sites
Regardless whether you have a D3D matrix
[  0  1  2  3 ]
[ 4 5 6 7 ]
[ 8 9 10 11 ]
[ 12 13 14 15 ]
or a OpenGL matrix (the transpose of the above one)
[  0  4  8 12 ]
[ 1 5 9 13 ]
[ 2 6 10 14 ]
[ 3 7 11 15 ]
in linear memory (i.e. from lower address to higher address) the layout is
{ 0, 1, 2, 3, 4, ..., 15 }

This means that you need not re-order to use that for either D3D or OpenGL (but you need to do so for e.g. Collada!) because if you use it in D3D you would do a row vector multiplication
              [  0  1  2  3 ]
[ x y z w ] * [ 4 5 6 7 |
[ 8 9 10 11 ]
[ 12 13 14 15 ]
, and in OpenGL a column vector multiplication
[  0  4  8 12 ]   [ x [
[ 1 5 9 13 ] * [ y ]
[ 2 6 10 14 ] [ z ]
[ 3 7 11 15 ] [ w ]
so that the results are identical, aren't they? The quintessence is, that row vectors together with row major order on the one hand, and column vectors together with column major order on the other hand produce the same layout in memory.

Quote:
Original post by ehsan2004
I have seen an Open Source example that simply works with row major matrices and pre multiplies them and then sends the result to glMultMatrix().

Maybe the following mathematical rule was used:
( A * B )T = BT * AT


BTW: Whether the elements 12, 13, 14 store the translation depends additionally on the conventation that the homogeneous co-ordinate is store at the 4th place in a 4D vector. Both D3D as well as OpenGL use this convention, but other APIs/formats may use another one.
1

Share this post


Link to post
Share on other sites
But I don't see any matrix inversion there:

mat4(const mat4 &m) {
mat[0] = m[0]; mat[4] = m[4]; mat[8] = m[8]; mat[12] = m[12];
mat[1] = m[1]; mat[5] = m[5]; mat[9] = m[9]; mat[13] = m[13];
mat[2] = m[2]; mat[6] = m[6]; mat[10] = m[10]; mat[14] = m[14];
mat[3] = m[3]; mat[7] = m[7]; mat[11] = m[11]; mat[15] = m[15];
}



mat4 operator*(const mat4 &m) const {
mat4 ret;
ret[0] = mat[0] * m[0] + mat[4] * m[1] + mat[8] * m[2] + mat[12] * m[3];
ret[1] = mat[1] * m[0] + mat[5] * m[1] + mat[9] * m[2] + mat[13] * m[3];
ret[2] = mat[2] * m[0] + mat[6] * m[1] + mat[10] * m[2] + mat[14] * m[3];
ret[3] = mat[3] * m[0] + mat[7] * m[1] + mat[11] * m[2] + mat[15] * m[3];
ret[4] = mat[0] * m[4] + mat[4] * m[5] + mat[8] * m[6] + mat[12] * m[7];
ret[5] = mat[1] * m[4] + mat[5] * m[5] + mat[9] * m[6] + mat[13] * m[7];
ret[6] = mat[2] * m[4] + mat[6] * m[5] + mat[10] * m[6] + mat[14] * m[7];
ret[7] = mat[3] * m[4] + mat[7] * m[5] + mat[11] * m[6] + mat[15] * m[7];
ret[8] = mat[0] * m[8] + mat[4] * m[9] + mat[8] * m[10] + mat[12] * m[11];
ret[9] = mat[1] * m[8] + mat[5] * m[9] + mat[9] * m[10] + mat[13] * m[11];
ret[10] = mat[2] * m[8] + mat[6] * m[9] + mat[10] * m[10] + mat[14] * m[11];
ret[11] = mat[3] * m[8] + mat[7] * m[9] + mat[11] * m[10] + mat[15] * m[11];
ret[12] = mat[0] * m[12] + mat[4] * m[13] + mat[8] * m[14] + mat[12] * m[15];
ret[13] = mat[1] * m[12] + mat[5] * m[13] + mat[9] * m[14] + mat[13] * m[15];
ret[14] = mat[2] * m[12] + mat[6] * m[13] + mat[10] * m[14] + mat[14] * m[15];
ret[15] = mat[3] * m[12] + mat[7] * m[13] + mat[11] * m[14] + mat[15] * m[15];
return ret;
}



For example, he has also calculated the texture matrix for the shader( When using shader ), But he has not transposed the results:

void CProjector :: SetupTexMatrix()
{
float offset[16] = { 0.5f, 0, 0, 0,
0, 0.5f, 0, 0,
0, 0, 0, 0,
0.5f,0.5f, 0.0f, 1 };

mat4 m_offset = mat4(offset);
mat4 m_result = m_offset * mat4_projection * mat4_view;

glMatrixMode(GL_TEXTURE);
glLoadMatrixf((GLfloat*) &m_result);
glMatrixMode(GL_MODELVIEW);
}



You can find his source code here:
http://glbook.gamedev.net/moglgp/code.asp
Download chapter 5 and search for projective texturing.

0

Share this post


Link to post
Share on other sites
I'm agree with haegarr.
Again I add the comments of the author :

Also note that the product of the projection matrices is transposed before being passed to glTexGenv(). This is necessary because all three matrices store data in column major order. After transposing, the result is in row major order which is what glTexGenfv() expects.
...

I don't agree with the author. I guess It's about passing the correct equation to glTexGen(), It's not about the DirectX or OpenGL matrices.
0

Share this post


Link to post
Share on other sites
Quote:
This means that you need not re-order to use that for either D3D or OpenGL (but you need to do so for e.g. Collada!)


Yes, I don't know why Collada has used that ordering. I also transposed the bind shape matrices because Collada stores the transpose of the standard row major ordering! (For example regarding the Collada spec, translation elements are stored in m[3], m[7] and m[11] !
I remember that someone reported the bug to Collada forum, but we still see the same rule in Collada specification.
0

Share this post


Link to post
Share on other sites
Quote:
Original post by ehsan2004
Yes, I don't know why Collada has used that ordering. I also transposed the bind shape matrices because Collada stores the transpose of the standard row major ordering! (For example regarding the Collada spec, translation elements are stored in m[3], m[7] and m[11] !
I remember that someone reported the bug to Collada forum, but we still see the same rule in Collada specification.
I'm not sure whether that is really a bug. In fact, you have 2 binary criteria (if neglecting esoteric ones), allowing for 4 combinations:
row vectors and row major order
row vectors and column major order
column vectors and row major order
column vectors and column major order

No one is really superior w.r.t. the others. OpenGL has picked one, D3D another, and Collada a third.
0

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  
Followers 0

  • Similar Content

    • By Solid_Spy
      Hello, I have been working on SH Irradiance map rendering, and I have been using a GLSL pixel shader to render SH irradiance to 2D irradiance maps for my static objects. I already have it working with 9 3D textures so far for the first 9 SH functions.
      In my GLSL shader, I have to send in 9 SH Coefficient 3D Texures that use RGBA8 as a pixel format. RGB being used for the coefficients for red, green, and blue, and the A for checking if the voxel is in use (for the 3D texture solidification shader to prevent bleeding).
      My problem is, I want to knock this number of textures down to something like 4 or 5. Getting even lower would be a godsend. This is because I eventually plan on adding more SH Coefficient 3D Textures for other parts of the game map (such as inside rooms, as opposed to the outside), to circumvent irradiance probe bleeding between rooms separated by walls. I don't want to reach the 32 texture limit too soon. Also, I figure that it would be a LOT faster.
      Is there a way I could, say, store 2 sets of SH Coefficients for 2 SH functions inside a texture with RGBA16 pixels? If so, how would I extract them from inside GLSL? Let me know if you have any suggestions ^^.
    • By KarimIO
      EDIT: I thought this was restricted to Attribute-Created GL contexts, but it isn't, so I rewrote the post.
      Hey guys, whenever I call SwapBuffers(hDC), I get a crash, and I get a "Too many posts were made to a semaphore." from Windows as I call SwapBuffers. What could be the cause of this?
      Update: No crash occurs if I don't draw, just clear and swap.
      static PIXELFORMATDESCRIPTOR pfd = // pfd Tells Windows How We Want Things To Be { sizeof(PIXELFORMATDESCRIPTOR), // Size Of This Pixel Format Descriptor 1, // Version Number PFD_DRAW_TO_WINDOW | // Format Must Support Window PFD_SUPPORT_OPENGL | // Format Must Support OpenGL PFD_DOUBLEBUFFER, // Must Support Double Buffering PFD_TYPE_RGBA, // Request An RGBA Format 32, // Select Our Color Depth 0, 0, 0, 0, 0, 0, // Color Bits Ignored 0, // No Alpha Buffer 0, // Shift Bit Ignored 0, // No Accumulation Buffer 0, 0, 0, 0, // Accumulation Bits Ignored 24, // 24Bit Z-Buffer (Depth Buffer) 0, // No Stencil Buffer 0, // No Auxiliary Buffer PFD_MAIN_PLANE, // Main Drawing Layer 0, // Reserved 0, 0, 0 // Layer Masks Ignored }; if (!(hDC = GetDC(windowHandle))) return false; unsigned int PixelFormat; if (!(PixelFormat = ChoosePixelFormat(hDC, &pfd))) return false; if (!SetPixelFormat(hDC, PixelFormat, &pfd)) return false; hRC = wglCreateContext(hDC); if (!hRC) { std::cout << "wglCreateContext Failed!\n"; return false; } if (wglMakeCurrent(hDC, hRC) == NULL) { std::cout << "Make Context Current Second Failed!\n"; return false; } ... // OGL Buffer Initialization glClear(GL_DEPTH_BUFFER_BIT | GL_COLOR_BUFFER_BIT); glBindVertexArray(vao); glUseProgram(myprogram); glDrawElements(GL_TRIANGLES, indexCount, GL_UNSIGNED_SHORT, (void *)indexStart); SwapBuffers(GetDC(window_handle));  
    • By Tchom
      Hey devs!
       
      I've been working on a OpenGL ES 2.0 android engine and I have begun implementing some simple (point) lighting. I had something fairly simple working, so I tried to get fancy and added color-tinting light. And it works great... with only one or two lights. Any more than that, the application drops about 15 frames per light added (my ideal is at least 4 or 5). I know implementing lighting is expensive, I just didn't think it was that expensive. I'm fairly new to the world of OpenGL and GLSL, so there is a good chance I've written some crappy shader code. If anyone had any feedback or tips on how I can optimize this code, please let me know.
       
      Vertex Shader
      uniform mat4 u_MVPMatrix; uniform mat4 u_MVMatrix; attribute vec4 a_Position; attribute vec3 a_Normal; attribute vec2 a_TexCoordinate; varying vec3 v_Position; varying vec3 v_Normal; varying vec2 v_TexCoordinate; void main() { v_Position = vec3(u_MVMatrix * a_Position); v_TexCoordinate = a_TexCoordinate; v_Normal = vec3(u_MVMatrix * vec4(a_Normal, 0.0)); gl_Position = u_MVPMatrix * a_Position; } Fragment Shader
      precision mediump float; uniform vec4 u_LightPos["+numLights+"]; uniform vec4 u_LightColours["+numLights+"]; uniform float u_LightPower["+numLights+"]; uniform sampler2D u_Texture; varying vec3 v_Position; varying vec3 v_Normal; varying vec2 v_TexCoordinate; void main() { gl_FragColor = (texture2D(u_Texture, v_TexCoordinate)); float diffuse = 0.0; vec4 colourSum = vec4(1.0); for (int i = 0; i < "+numLights+"; i++) { vec3 toPointLight = vec3(u_LightPos[i]); float distance = length(toPointLight - v_Position); vec3 lightVector = normalize(toPointLight - v_Position); float diffuseDiff = 0.0; // The diffuse difference contributed from current light diffuseDiff = max(dot(v_Normal, lightVector), 0.0); diffuseDiff = diffuseDiff * (1.0 / (1.0 + ((1.0-u_LightPower[i])* distance * distance))); //Determine attenuatio diffuse += diffuseDiff; gl_FragColor.rgb *= vec3(1.0) / ((vec3(1.0) + ((vec3(1.0) - vec3(u_LightColours[i]))*diffuseDiff))); //The expensive part } diffuse += 0.1; //Add ambient light gl_FragColor.rgb *= diffuse; } Am I making any rookie mistakes? Or am I just being unrealistic about what I can do? Thanks in advance
    • By yahiko00
      Hi,
      Not sure to post at the right place, if not, please forgive me...
      For a game project I am working on, I would like to implement a 2D starfield as a background.
      I do not want to deal with static tiles, since I plan to slowly animate the starfield. So, I am trying to figure out how to generate a random starfield for the entire map.
      I feel that using a uniform distribution for the stars will not do the trick. Instead I would like something similar to the screenshot below, taken from the game Star Wars: Empire At War (all credits to Lucasfilm, Disney, and so on...).

      Is there someone who could have an idea of a distribution which could result in such a starfield?
      Any insight would be appreciated
    • By afraidofdark
      I have just noticed that, in quake 3 and half - life, dynamic models are effected from light map. For example in dark areas, gun that player holds seems darker. How did they achieve this effect ? I can use image based lighting techniques however (Like placing an environment probe and using it for reflections and ambient lighting), this tech wasn't used in games back then, so there must be a simpler method to do this.
      Here is a link that shows how modern engines does it. Indirect Lighting Cache It would be nice if you know a paper that explains this technique. Can I apply this to quake 3' s light map generator and bsp format ?
  • Popular Now