• Advertisement
Sign in to follow this  

OpenGL Setting Shader Registers

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

If you intended to correct an error in the post then please contact us.

Recommended Posts

In D3D when we set a GPU register with the WorldViewProjection matrix first we have to transpose the matrix. Is that true in OpenGL also? Thanks

Share this post


Link to post
Share on other sites
Advertisement
afaik all matrix in OpenGL stay as column major all the time with no transposes in shaders (which makes me wonder if OGL reflects the underlaying hardware better... )

Share this post


Link to post
Share on other sites
Thanks.

This gets me to the question that is really bugging me.

If D3D uses row vectors and openGL uses col vectors, then when D3D transposes its WorldViewProj matrix before sending it to the shader it is sending the same Matrix as OpenGL. However, OpenGl is col-major (as you mentioned) and D3D is row major. Which means that if registers c0-c3 were set with the WorldViewProj matrix from D3D they would hold the rows of the matrix and if they were set with OpenGL they would hold the cols of the matrix. So, why don't you have to write two versions of the same shader?

Thanks
Todd

Share this post


Link to post
Share on other sites
Here is my understanding, which I believe to be flawed, but don't understand why it is flawed:

An OpenGL translation matrix would be as follows:

1 0 0 tx
0 1 0 ty
0 0 1 tz
0 0 0 1

A D3D translation matrix would be as follows:

1 0 0 0
0 1 0 0
0 0 1 0
tx ty tz 1

So, when you transpose the D3D matrix it becomes the same as the OpenGL matrix.

But, D3D is row-major and OpenGL is col-major. So, when you set the registers using D3D each register holds a row but when you set the registers using OpenGL each register holds a column. Therefore, if we set registers c0-c3 they would hold different values for OpenGL and D3D.


Thanks for the help.
Todd

Share this post


Link to post
Share on other sites
you're right about the transposing of the matrix, as to why the loading works I dont know, i'd have to see the code for D3D to see how you load it and how you access it, chances are its just driver voodoo making sure things work as you expect

Share this post


Link to post
Share on other sites
Hey Phantom,

Here is the answer to my question, I think I just confused everyone by lack of understanding/use of OpenGL!

The following comment was made by Joakim Hårsman on FlipCode:

"LHS vs RHS isn't the only difference between D3D and OpenGL that can cause differences. First of all, OpenGL treats vertices as column vectors, so transformations are concatenated by left multiplying: M'=TM, v'=Mv and this causes the typical tranformation matrix to be the transpose of the Direct3D standard. However, since OpenGL treats matrices as they were stored in column major order (vs D3D's row major), everything works out the same anyway (ignoring coord system orientation) provided you're consistent in how you construct the matrix you load into OpenGL/D3D. "

Thanks for your help.
Todd

Share this post


Link to post
Share on other sites
What some people don't seem to realise, is that the actual memory configuration of OGL and D3D matrices are the same, just one represents a column matrix, and one a row matrix.

Share this post


Link to post
Share on other sites
http://www.opengl.org/resources/faq/technical/transformations.htm#tran0005

9.005 Are OpenGL matrices column-major or row-major?

For programming purposes, OpenGL matrices are 16-value arrays with base vectors laid out contiguously in memory. The translation components occupy the 13th, 14th, and 15th elements of the 16-element matrix.

Column-major versus row-major is purely a notational convention. Note that post-multiplying with column-major matrices produces the same result as pre-multiplying with row-major matrices. The OpenGL Specification and the OpenGL Reference Manual both use column-major notation. You can use any notation, as long as it's clearly stated.

Sadly, the use of column-major format in the spec and blue book has resulted in endless confusion in the OpenGL programming community. Column-major notation suggests that matrices are not laid out in memory as a programmer would expect.

A summary of Usenet postings on the subject can be found here.

Share this post


Link to post
Share on other sites
There is actually a point to treating vectors as column vectors like OpenGL does as well. This means you can view transformations like a function v'=P*V*M*v is the same thing as v'=P(V(M(v))) and is somewhat of a standard in linear algebra. So, originally, the spec was just supposed to be mathematically elegant and saying that are stored in column major order was just a clever way of maintaining backwards compatability with IrisGL. The actual matrices you provide are identical! The whole story is here http://stevehollasch.com/cgindex/math/matrix/column-vec.html

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By LifeArtist
      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
      Thanks in advance
    • 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:
      Vertex Shader:
      #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
       
    • By dpadam450
      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;
    • By Devashish Khandelwal
      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?
  • Advertisement