# OpenGL Projection Matrix in OpenGL

## Recommended Posts

My question is in two parts, the first is: Can someone explain to me what all the data in a projection matrix is, or in other words, what each cell actually represents? My second question is: at what point is depth calculated? For example, when I make a call to gluPerspective(...) and the Projection matrix is modified, if I multiply that matrix by some vector (or my point), is the depth factor calculated along with the transform in that same calculation (when the homogeneous coords are yielded); or is it actually (which is how it seems to me) calculated by the hardware at some other point after? I am trying to write a vector shader using cg, and I am having a hard time figuring out why, when I call the gluPerspective(...) and then pass the projection matrix into the shader, and then multiply that matrix by the vertex position, everything is distorted. Now, keep in mind I am not using glut and I did not pass the model view matrix in because it is - in this particular case - only an identity matrix; and when any matrix or vector is multiplied by an identity matrix, that matrix is yielded anyway. So, not calculating the model matrix in my case should not change anything... or maybe is does and I am not aware of something, which might be the case. I hope this is clear. Any help would be greatly appreciated. Thanks!

##### Share on other sites
Adding to my previous question: to concatenate a projection matrix and a view model matrix, do I just need to multiply the two together, which is what it seems to me? If this is the case, in what order do I do this?

##### Share on other sites
Quote:
 Original post by mowenMy question is in two parts, the first is: Can someone explain to me what all the data in a projection matrix is, or in other words, what each cell actually represents?

As you know, the projection matrix is used for transform a 3D point to 2D screen. The elements in the projection matrix are derived for this reason. Please check the following page to see how each element can be calculated. (section of Details of the Projection Transform)
http://www.cs.queensu.ca/~jstewart/454/notes/pipeline/
Quote:
 My second question is: at what point is depth calculated?

Once a point transformed by projection matrix, the z-value of the point represents now the depth of the point. (x and y values are for the coords of 2D screen.) The value will be normalized from -1 to 1 by dividing by w. The depth value of the point come along until it pass through the fragment operation which is the last process to convert the fragment to a pixel on the framebuffer.

Quote:
 Adding to my previous question: to concatenate a projection matrix and a view model matrix, do I just need to multiply the two together, which is what it seems to me? If this is the case, in what order do I do this?

The order of transform is:
Model Matrix (Mm) -> View Matrix (Mv)-> Projection Matrix (Mp) -> 1/w -> Viewport transform

v' = Mp * Mv * Mm * v

##### Share on other sites
Thank you songho!

Your reply along with the link were quite useful and helped give me a clear perspective on what is going on, and in what order. I really appreciate you taking the time do that.

You rock!!!

## Create an account

Register a new account

• ## Partner Spotlight

• ### Forum Statistics

• Total Topics
627655
• Total Posts
2978458
• ### Similar Content

• Both functions are available since 3.0, and I'm currently using glMapBuffer(), which works fine.
But, I was wondering if anyone has experienced advantage in using glMapBufferRange(), which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
• By xhcao
Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness.
• By cebugdev
hi guys,
are there any books, link online or any other resources that discusses on how to build special effects such as magic, lightning, etc. in OpenGL? i mean, yeah most of them are using particles but im looking for resources specifically on how to manipulate the particles to look like an effect that can be use for games,. i did fire particle before, and I want to learn how to do the other 'magic' as well.
Like are there one book or link(cant find in google) that atleast featured how to make different particle effects in OpenGL (or DirectX)? If there is no one stop shop for it, maybe ill just look for some tips on how to make a particle engine that is flexible enough to enable me to design different effects/magic
let me know if you guys have recommendations.
• By dud3
How do we rotate the camera around x axis 360 degrees, without having the strange effect as in my video below?
Mine behaves exactly the same way spherical coordinates would, I'm using euler angles.
Tried googling, but couldn't find a proper answer, guessing I don't know what exactly to google for, googled 'rotate 360 around x axis', got no proper answers.

References:
Code: https://pastebin.com/Hcshj3FQ
The video shows the difference between blender and my rotation:

• By Defend
I've had a Google around for this but haven't yet found some solid advice. There is a lot of "it depends", but I'm not sure on what.
My question is what's a good rule of thumb to follow when it comes to creating/using VBOs & VAOs? As in, when should I use multiple or when should I not? My understanding so far is that if I need a new VBO, then I need a new VAO. So when it comes to rendering multiple objects I can either:
* make lots of VAO/VBO pairs and flip through them to render different objects, or
* make one big VBO and jump around its memory to render different objects.
I also understand that if I need to render objects with different vertex attributes, then a new VAO is necessary in this case.
If that "it depends" really is quite variable, what's best for a beginner with OpenGL, assuming that better approaches can be learnt later with better understanding?

• 10
• 12
• 22
• 13
• 33