OpenGL custom projection matrix

Recommended Posts

Hello everyone! I want to create a custom projection matrix, and load it with glLoadMatrix* function. There are two difficulties that I encountered: 1) I have found no guidelines for doing this in the red book, at the viewing chapter. So I started searching the web, but I found nothing that would satisfy me. My problem is that I am really used to OpenGL GlFrustum and glOrtho calls to change the projection matrix, which define a "canonical volume" for viewing,and I don't really understand how I can use glLoadMatrix to load a matrix, and to "bypass" the canonical volume stuff. 2) I read in an article on the net - sorry I don't know how to use VB codes on this forum , are they turned on? - [url]http://sjbaker.org/steve/omniv/projection_abuse.html[/url] I read here that "You *could* use glLoadMatrix to set up your own projection matrix (if you understand the restrictions and consequences)" So what are those "restrictions and consequences"? 3) Even though I am interested in the general aspect of the problem, I can be even more specific: I want to use in an opengl app an "oblique projection". Has anyone any idea how this can be done in OpenGL - an axonometric projection with default parameters, let's make it like an orthographic projection, but the angle between the normal and the viewing direction to be say 60 degrees - can anyone tell me how this can be done, eventually with some sample source code?

Share on other sites
Details on the OpenGL matrix and how various ones are setup can be found in the appendix of the OpenGL Red Book.

Share on other sites
This isn't really an 'answer' per se, but I thought I'd mention that I've also thought about the oblique projection problem (although I never derived the matrix for it). Basically I think you'll need to derive a matrix which does essentially what the standard frustum and orthographic matrices do, which is to map coordinates from one space (view space) to another (clip space). Your 'oblique' matrix will need to do the same, except that the space you're mapping from is not a frustum or rectangular prism, but an oblique rectangular prism. The first step will be understanding the frustum and orthographic matrices and how they're derived; then, you should be able to apply the same principles to derive the oblique version.

Note that this is all speculative; I haven't actually tried this myself.

Share on other sites
anyone any ideas?

to be more specific: I want to use the following matrix as a perspective matrix:

GLdouble g_dOblicProj[]={
1 , 0 , -0.5 , 0 ,
0 , 1 , 3.25 , 0 ,
0 , 0 , 0 , 0,
0 , 0 , 0 , 1
};

I load this one using glLoadmatrix, but the result looks the same as though I were using glOrtho :(

I can do the math in order to compute the matrices of various projection matrices, but I don't understand how can I define the "viewing volume" - the one that is a frustum in perspective projection, and a box in orthographic projection

Share on other sites
I believe after projection the viewing volume is -1<=x<=1, -1<=y<=1 and 0<=z<=1. You can verify that using the orthographic or prespective projection matrices used by OpenGL and running the corners of the viewing volume through it. Someone posted it is w, not 1, but since the perspective divide is done for you I don't know how you get w to be anything but 1.

Create an account

Register a new account

• Partner Spotlight

• Forum Statistics

• Total Topics
627662
• Total Posts
2978519
• 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
• 10
• 12
• 22
• 13