• Advertisement

Archived

This topic is now archived and is closed to further replies.

OpenGL [OPENGL] Using Matricies

This topic is 6205 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

Ok, I''ve been learning a bit about matricies and I think I might be getting close to being able to use them. Currently I''m using 3 vectors to represent my model in 3d space(no roll). I''d like to be able to just store a matrix with each object and call it to transform it''s location\orientation. Here is what I think might be rightCan someone confirm these, I already have something that minimally works and don''t want to break it if I''m wrong) 1) OpenGL will accept 4*4 matricies only. 2) Given the following 4*4 matrix: ABCD EFGH IJKL MNOP the data I plug in to them is: Vectors: Right/Local X axis/Pitch = AEI Up/Local Y axis/Turn = BFJ Direction/Local Z axis/Roll = CGK Point: Position/World location = MNO 3) If I want to turn to the left a bit I add a vector that something like 0,0,~0.7? Or is there an easier way? My data is a signed char[2] representing a mouse delta in x,y? Then multiply the vector against the correct place in the matrix? 4) To use the matrix for an object I do something like: glPushmatrix() glMultMatrix(m_ObjectMatrix) Draw() glPopMatrix() 5) I''ve heard that I should renormalise the matrix occationally. Is this because as your adding all those rotations\tranlations your making the floats say bigger and loosing numerical precision? If I only do this for moving object in a scene then I could probably do it each time the object moves couldn''t I? 6) The red book states that for performance reasons you shouldn''t use glMulMatrix. I''ve seen some people plugging the the values in to gluLookAt and other using glRotate\glTranslate ... Any comments??? Many thanks for replies on any of these questions. Chris

Share this post


Link to post
Share on other sites
Advertisement
I usually don''t use matrixs...but if you wanted to turn the "view camera" to the right or left, or up or down...I find it much simpler (for my mind) to use gllookat. since it takes in a starting and end point. I would store a "heading1" for left and right rotations and a "heading2" for up and down. so what you would do is call gllookat like this:
glLookAt(Camerapos.x, camerapos.y, camerapos.z,
lookat.x, lookat.y, lookat.z, 1);

where lookat is the center of the screen and where it''s pointed
and manipulate lookat with sin and cos of the headings...

It''s really the same as the matrixs, but I figure that the amount of multiply is less. Since you have to multiply every element in the matrix anytime you major changes to it (I assume) and here you would use less memory by using only the 6 floats (the x,y,z of the camera and lookat) where you would need 16 floats for the matrix and one of them is never used. (please somebody correct me if I am wrong, it''s been a while)

Share this post


Link to post
Share on other sites
quote:
Original post by gimp

1) OpenGL will accept 4*4 matricies only.
2) Given the following 4*4 matrix:

ABCD
EFGH
IJKL
MNOP

the data I plug in to them is:

Vectors:
Right/Local X axis/Pitch = AEI
Up/Local Y axis/Turn = BFJ
Direction/Local Z axis/Roll = CGK
Point:
Position/World location = MNO




OpenGL uses column major matrices so the matrix should look like this:

AEIM
BFJN
CGKO
DHLP


The fanatic is incorruptible: if he kills for an idea, he can just as well get himself killed for one; in either case, tyrant or martyr, he is a monster.
--EM Cioran

Opere Citato

Share this post


Link to post
Share on other sites
i use glMultMatrix/glLoadMAtrix instead of gltranslate + rotating cause the first is quicker + more flexable.
some of your understanding about matrices is wrong i suggest checking out a linear algebra maths book or having a search on google,flipcode, this site.matrice + quaternion faq has got good info.
matrices is a very important subject speed some time to understand them now it''ll save u heaps in the future


http://members.xoom.com/myBollux

Share this post


Link to post
Share on other sites
Thanks all. I wasn''t concerned originally in knowing the opengl or mat way of storing matricies, I wanted to use it as a black box.

Without any real knowledge I would have assumed that passing the matricies to opengl would anabled any T&L to take place, so that could mean far less processing. My main reasoning is to make client code easier to use and to abstrack all that math in to a simple inteaction mechanism.

zedzek, yes, this was posted after reading the faq you mentioned. I''ve read 3 game books''s sections on this subject. All of them show you how to calculate the internal mechanics etc, etc but not how to put data in them. My above observations were made from the matrix\quat faq at flipcode.

What did I get wrong? I''d really like to know as I''ve decided to embark on a learning journey about this, and write my own core math classes (vector,matrix,sphere,intersection,distance etc) so I understand whats actually happening. Any hints?

Many thanks

Chris

Share this post


Link to post
Share on other sites
well this

Right/Local X axis/Pitch = AEI
Up/Local Y axis/Turn = BFJ
Direction/Local Z axis/Roll = CGK

and this

3) If I want to turn to the left a bit I add a vector that something like 0,0,~0.7? Or is there an easier way?

though perhaps its something i havent heard about

eg to turn left/right ie on the X axis

make the following matrix
ABC
DEF
GHI

use
A = cos(angle) C = sin(angle) G = -sin(angle) I = cos(angle)
E = 1 and the rest 0

and multiple the current matrix by the above matrix to get the new rotated matrix

http://members.xoom.com/myBollux

Share this post


Link to post
Share on other sites
Thanks again zedzeek,

I now have a class up and running that can do translation and rotations, however when I attempt to tell my matrix class to "rotate about the Y axis" I can''t find a good way to do so.

Additioanlly I''ve heard that this can lead to numerical error problems. Is there some kind of normalisation that I could do on the rotations portion of the matrix to help that?

Here is my example function:

  
void CMatrix::RotateY(const float a_Angle)
{
float c = Cos(a_Angle);
float s = Sin(a_Angle);

m[0] = c;
m[2] = -s;
m[8] = s;
m[10] = c;
}


As you can see I''m merely setting the rotation. I''d like to know how I can safley call this function every frame to spin a cube without numerical accuracy affecting the class.

Share this post


Link to post
Share on other sites
u will need to renormalize your matrice every so often
also the cos + sin functions use radians not degrees
float c = Cos(a_Angle*DEGREES_TO_RADIANS);

http://members.xoom.com/myBollux

Share this post


Link to post
Share on other sites

  • 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