# Difference between revisions of "Viewing and Transformations"

(→How does the camera work in OpenGL?) |
(Trigonometric functions are needed for perfect zooming.) |
||

(15 intermediate revisions by 7 users not shown) | |||

Line 1: | Line 1: | ||

+ | {{deprecated}} | ||

===== How does the camera work in OpenGL? ===== | ===== How does the camera work in OpenGL? ===== | ||

− | As far as OpenGL is concerned, there is no camera. More specifically, the camera is always located at the eye space coordinate (0.0, 0.0, 0.0). To give the appearance of moving the camera, your OpenGL application must move the scene with the inverse of the camera transformation. This is commonly referred to as the viewing transformation. | + | As far as OpenGL is concerned, there is no camera. More specifically, the camera is always located at the eye space coordinate (0.0, 0.0, 0.0). To give the appearance of moving the camera, your OpenGL application must move the scene with the inverse of the camera transformation by placing it on the MODELVIEW matrix. This is commonly referred to as the viewing transformation. |

+ | |||

+ | In practice this is mathematically equivalent to a camera transformation but more efficient because model transformations and camera transformations are concatenated to a single matrix. As a result though, certain operations must be performed when the camera and only the camera is on the MODELVIEW matrix. For example to position a light source in world space it most be positioned while the viewing transformation and only the viewing transformation is applied to the MODELVIEW matrix. | ||

===== How can I move my eye, or camera, in my scene? ===== | ===== How can I move my eye, or camera, in my scene? ===== | ||

Line 17: | Line 20: | ||

The [http://www.3dgamedev.com/resources/openglfaq.txt game dev FAQ] has good information on these two matrices. | The [http://www.3dgamedev.com/resources/openglfaq.txt game dev FAQ] has good information on these two matrices. | ||

− | Read Steve Baker's article on [http:// | + | Read Steve Baker's article on [http://sjbaker.org/steve/omniv/projection_abuse.html projection abuse]. This article is highly recommended and well-written. It's helped several new OpenGL programmers. |

===== How do I implement a zoom operation? ===== | ===== How do I implement a zoom operation? ===== | ||

Line 27: | Line 30: | ||

For example, your program might maintain a zoom factor based on user input, which is a floating-point number. When set to a value of 1.0, no zooming takes place. Larger values result in greater zooming or a more restricted field of view, while smaller values cause the opposite to occur. Code to create this effect might look like: | For example, your program might maintain a zoom factor based on user input, which is a floating-point number. When set to a value of 1.0, no zooming takes place. Larger values result in greater zooming or a more restricted field of view, while smaller values cause the opposite to occur. Code to create this effect might look like: | ||

− | < | + | <source lang="c"> |

+ | static float zoomFactor; /* Global, if you want. Modified by user input. Initially 1.0 */ | ||

/* A routine for setting the projection matrix. May be called from a resize | /* A routine for setting the projection matrix. May be called from a resize | ||

Line 33: | Line 37: | ||

dimensions of the drawing area. Creates a projection matrix with correct | dimensions of the drawing area. Creates a projection matrix with correct | ||

aspect ratio and zoom factor. */ | aspect ratio and zoom factor. */ | ||

− | void setProjectionMatrix (int width, int height) | + | void setProjectionMatrix (int width, int height, float conditionalaspect) |

{ | { | ||

glMatrixMode(GL_PROJECTION); | glMatrixMode(GL_PROJECTION); | ||

glLoadIdentity(); | glLoadIdentity(); | ||

− | gluPerspective (50.0*zoomFactor, (float)width/(float)height, zNear, zFar); | + | if ( (float)width / (float)height < conditionalaspect ) { // Adjust zoom factor to extend vertical aspect ratio if below the aspect ratio constraint otherwise extend horizontal. By default, the aspect constraint is 1.0. |

+ | zoomfactor *= ((float)width / (float)height) / conditionalaspect; | ||

+ | } | ||

+ | gluPerspective(atan(tan(50.0 * 3.14159 / 360.0) / zoomFactor) * 360.0 / 3.14159, (float)width/(float)height, zNear, zFar); | ||

/* ...Where 'zNear' and 'zFar' are up to you to fill in. */ | /* ...Where 'zNear' and 'zFar' are up to you to fill in. */ | ||

− | }</ | + | } |

+ | </source> | ||

Instead of gluPerspective(), your application might use glFrustum(). This gets tricky, because the left, right, bottom, and top parameters, along with the zNear plane distance, also affect the field of view. Assuming you desire to keep a constant zNear plane distance (a reasonable assumption), glFrustum() code might look like this: | Instead of gluPerspective(), your application might use glFrustum(). This gets tricky, because the left, right, bottom, and top parameters, along with the zNear plane distance, also affect the field of view. Assuming you desire to keep a constant zNear plane distance (a reasonable assumption), glFrustum() code might look like this: | ||

− | < | + | <source lang="c"> |

− | + | glFrustum(left/zoomFactor, right/zoomFactor, bottom/zoomFactor, top/zoomFactor, zNear, zFar); | |

− | + | </source> | |

glOrtho() is similar. | glOrtho() is similar. | ||

Line 59: | Line 67: | ||

You can simulate an orbit by translating/rotating the scene/object and leaving your camera in the same place. For example, to orbit an object placed somewhere on the Y axis, while continuously looking at the origin, you might do this: | You can simulate an orbit by translating/rotating the scene/object and leaving your camera in the same place. For example, to orbit an object placed somewhere on the Y axis, while continuously looking at the origin, you might do this: | ||

− | < | + | <source lang="c"> |

+ | gluLookAt(camera[0], camera[1], camera[2], /* look from camera XYZ */ | ||

0, 0, 0, /* look at the origin */ | 0, 0, 0, /* look at the origin */ | ||

0, 1, 0); /* positive Y up vector */ | 0, 1, 0); /* positive Y up vector */ | ||

Line 65: | Line 74: | ||

/* ...where orbitDegrees is derived from mouse motion */ | /* ...where orbitDegrees is derived from mouse motion */ | ||

− | glCallList(SCENE); /* draw the scene */</ | + | glCallList(SCENE); /* draw the scene */ |

+ | </source> | ||

If you insist on physically orbiting the camera position, you'll need to transform the current camera position vector before using it in your viewing transformations. | If you insist on physically orbiting the camera position, you'll need to transform the current camera position vector before using it in your viewing transformations. | ||

Line 79: | Line 89: | ||

Next, choose a value for the zNear clipping plane. General guidelines are to choose something larger than, but close to 1.0. So, let's say you set | Next, choose a value for the zNear clipping plane. General guidelines are to choose something larger than, but close to 1.0. So, let's say you set | ||

− | < | + | <source lang="c"> |

− | zFar = zNear + diam;</ | + | zNear = 1.0; |

+ | zFar = zNear + diam; | ||

+ | </source> | ||

Structure your matrix calls in this order (for an Orthographic projection): | Structure your matrix calls in this order (for an Orthographic projection): | ||

− | < | + | <source lang="c"> |

+ | GLdouble left = c.x - diam; | ||

GLdouble right = c.x + diam; | GLdouble right = c.x + diam; | ||

GLdouble bottom c.y - diam; | GLdouble bottom c.y - diam; | ||

Line 93: | Line 106: | ||

glOrtho(left, right, bottom, top, zNear, zFar); | glOrtho(left, right, bottom, top, zNear, zFar); | ||

glMatrixMode(GL_MODELVIEW); | glMatrixMode(GL_MODELVIEW); | ||

− | glLoadIdentity();</ | + | glLoadIdentity(); |

+ | </source> | ||

This approach should center your objects in the middle of the window and stretch them to fit (i.e., its assuming that you're using a window with aspect ratio = 1.0). If your window isn't square, compute left, right, bottom, and top, as above, and put in the following logic before the call to glOrtho(): | This approach should center your objects in the middle of the window and stretch them to fit (i.e., its assuming that you're using a window with aspect ratio = 1.0). If your window isn't square, compute left, right, bottom, and top, as above, and put in the following logic before the call to glOrtho(): | ||

− | < | + | <source lang="c"> |

+ | GLdouble aspect = (GLdouble) windowWidth / windowHeight; | ||

if ( aspect < 1.0 ) { // window taller than wide | if ( aspect < 1.0 ) { // window taller than wide | ||

Line 105: | Line 120: | ||

left *= aspect; | left *= aspect; | ||

right *= aspect; | right *= aspect; | ||

− | }</ | + | } |

+ | </source> | ||

The above code should position the objects in your scene appropriately. If you intend to manipulate (i.e. rotate, etc.), you need to add a viewing transform to it. | The above code should position the objects in your scene appropriately. If you intend to manipulate (i.e. rotate, etc.), you need to add a viewing transform to it. | ||

Line 111: | Line 127: | ||

A typical viewing transform will go on the ModelView matrix and might look like this: | A typical viewing transform will go on the ModelView matrix and might look like this: | ||

− | < | + | <source lang="c"> |

+ | gluLookAt(0., 0., 2.*diam, c.x, c.y, c.z, 0.0, 1.0, 0.0); | ||

+ | </source> | ||

===== Why doesn't gluLookAt work? ===== | ===== Why doesn't gluLookAt work? ===== | ||

Line 121: | Line 139: | ||

It's usually best to experiment with a simple piece of code when you're trying to understand viewing transformations. Let's say you are trying to look at a unit sphere centered on the origin. You'll want to set up your transformations as follows: | It's usually best to experiment with a simple piece of code when you're trying to understand viewing transformations. Let's say you are trying to look at a unit sphere centered on the origin. You'll want to set up your transformations as follows: | ||

− | < | + | <source lang="c"> |

+ | glMatrixMode(GL_PROJECTION); | ||

glLoadIdentity(); | glLoadIdentity(); | ||

− | gluPerspective(50.0, 1.0, 3.0, 7.0); | + | gluPerspective(atan(tan(50.0 * 3.14159 / 360.0) / 1.0) * 360.0 / 3.141593, 1.0, 3.0, 7.0); |

glMatrixMode(GL_MODELVIEW); | glMatrixMode(GL_MODELVIEW); | ||

glLoadIdentity(); | glLoadIdentity(); | ||

gluLookAt(0.0, 0.0, 5.0, | gluLookAt(0.0, 0.0, 5.0, | ||

0.0, 0.0, 0.0, | 0.0, 0.0, 0.0, | ||

− | 0.0, 1.0, 0.0);</ | + | 0.0, 1.0, 0.0); |

+ | </source> | ||

It's important to note how the Projection and ModelView transforms work together. | It's important to note how the Projection and ModelView transforms work together. | ||

− | In this example, the Projection transform sets up a 50.0-degree field of view, with an aspect ratio of 1.0. The zNear clipping plane is 3.0 units in front of the eye, and the zFar clipping plane is 7.0 units in front of the eye. This leaves a Z volume distance of 4.0 units, ample room for a unit sphere. | + | In this example, the Projection transform sets up a 50.0-degree field of view with trigonometric functions to add a zoom factor sub-parameter, with an aspect ratio and zoom factor of 1.0. The zNear clipping plane is 3.0 units in front of the eye, and the zFar clipping plane is 7.0 units in front of the eye. This leaves a Z volume distance of 4.0 units, ample room for a unit sphere. |

The ModelView transform sets the eye position at (0.0, 0.0, 5.0), and the look-at point is the origin in the center of our unit sphere. Note that the eye position is 5.0 units away from the look at point. This is important, because a distance of 5.0 units in front of the eye is in the middle of the Z volume that the Projection transform defines. If the gluLookAt() call had placed the eye at (0.0, 0.0, 1.0), it would produce a distance of 1.0 to the origin. This isn't long enough to include the sphere in the view volume, and it would be clipped by the zNear clipping plane. | The ModelView transform sets the eye position at (0.0, 0.0, 5.0), and the look-at point is the origin in the center of our unit sphere. Note that the eye position is 5.0 units away from the look at point. This is important, because a distance of 5.0 units in front of the eye is in the middle of the Z volume that the Projection transform defines. If the gluLookAt() call had placed the eye at (0.0, 0.0, 1.0), it would produce a distance of 1.0 to the origin. This isn't long enough to include the sphere in the view volume, and it would be clipped by the zNear clipping plane. | ||

Line 146: | Line 166: | ||

===== I put my gluLookAt() call on my Projection matrix and now fog, lighting, and texture mapping don't work correctly. What happened? ===== | ===== I put my gluLookAt() call on my Projection matrix and now fog, lighting, and texture mapping don't work correctly. What happened? ===== | ||

− | + | Often this is caused by placing the transformation on the wrong matrix, look at question 3 for an explanation of this problem. However occasionally, and in particular for lighting, this can be caused because the lights were positioned when the wrong matrix is on the MODELVIEW matrix stack. When a light is positioned in eye space, i.e. relative to the eye, it should be positioned when an identity matrix is on the MODELVIEW stack. When a light is positioned in the world it should be positioned when the viewing matrix is on the MODELVIEW stack. When the light is positioned relative to an object under transformation it should be positioned when that object's model matrix has been multiplied with the viewing matrix on the MODELVIEW stack, remembering that it will have to be positioned before anything lit by it is rendered. If any light moves relative to the eye between frames it must be repositioned each frame using the appropriate matrix. | |

===== How can I create a stereo view? ===== | ===== How can I create a stereo view? ===== | ||

+ | |||

+ | Stereo viewing is accomplished by presenting a different image to the left and right eyes of the viewer. These images must be appropriate for the viewers relationship to the display they are looking at, much moreso than a mono 3D image. In addition the method used is tied closely to the display technology being used. Some graphics systems and display devices support stereo viewing in hardware and support features like left and right framebuffers in addition to the front and back buffers of conventional double buffered systems. Other systems support stereo correctly when two viewports are created in specific screen regions and specific video mode is used to send these to the screen. In conjunction with these modes a viewer often wears glasses either shuttered or polarized to select the displayed image appropriate to each eye. However even without these graphics features a developer can generate stereo views using features like color filtering where colored filters select an image based on red or blue filters and draw left and right eye images to red and blue framebuffer components for example, or even more simply just have multiple systems or graphics cards (or even a single card) generate two entirely separate video signals, for which a separate left and right eye image is drawn. The video is then sent to the appropriate eye either using a display employing polarizing filters or a head mounted display or some other custom display operating on similar principals. | ||

+ | |||

+ | From an OpenGL perspective, the requirements of stereo rendering are to use the appropriate setup to render to left and right eyes (be it color masks, separate contexts or different viewports) and then match the geometry of the OpenGL projection to the relationship of the viewer's left and right eyes with the display. The final OpenGL requirement is that the position of the eyes in the 'virtual' world must be given a pupil separation on the modelview stack, this separation would of course be a translation in eye space, but could be calculated in other equivalent ways. | ||

Paul Bourke has assembled information on stereo OpenGL viewing. | Paul Bourke has assembled information on stereo OpenGL viewing. | ||

Line 154: | Line 178: | ||

* [http://www.swin.edu.au/astronomy/pbourke/stereographics/stereorender/ Calculating Stereo Pairs] | * [http://www.swin.edu.au/astronomy/pbourke/stereographics/stereorender/ Calculating Stereo Pairs] | ||

* [http://www.swin.edu.au/astronomy/pbourke/opengl/redblue/ Creating Anaglyphs using OpenGL] | * [http://www.swin.edu.au/astronomy/pbourke/opengl/redblue/ Creating Anaglyphs using OpenGL] | ||

+ | |||

+ | |||

+ | ===== I can't get transformations to work. Where can I learn more about matrices? ===== | ||

+ | |||

+ | A thorough explanation of basic matrix math and linear algebra is beyond the scope of this FAQ. These concepts are taught in high school math classes in the United States. | ||

+ | |||

+ | If you understand the basics, but just get confused (a common problem even for the experienced!), read through Steve Baker's [http://web2.airmail.net/sjbaker1/matrices_can_be_your_friends.html review of matrix concepts] and his [http://web2.airmail.net/sjbaker1/eulers_are_evil.html article on Euler angles]. | ||

+ | |||

+ | Delphi code for performing basic vector, matrix, and quaternion operations can be found [http://www.lischke-online.de/Graphics.html here]. | ||

+ | |||

+ | ===== 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 [http://research.microsoft.com/~hollasch/cgindex/math/matrix/column-vec.html here]. | ||

+ | |||

+ | ===== What are OpenGL coordinate units? ===== | ||

+ | |||

+ | The short answer: Anything you want them to be. | ||

+ | |||

+ | Depending on the contents of your geometry database, it may be convenient for your application to treat one OpenGL coordinate unit as being equal to one millimeter or one parsec or anything in between (or larger or smaller). | ||

+ | |||

+ | OpenGL also lets you specify your geometry with coordinates of differing values. For example, you may find it convenient to model an airplane's controls in centimeters, its fuselage in meters, and a world to fly around in kilometers. OpenGL's ModelView matrix can then scale these different coordinate systems into the same eye coordinate space. | ||

+ | |||

+ | It's the application's responsibility to ensure that the Projection and ModelView matrices are constructed to provide an image that keeps the viewer at an appropriate distance, with an appropriate field of view, and keeps the zNear and zFar clipping planes at an appropriate range. An application that displays molecules in micron scale, for example, would probably not want to place the viewer at a distance of 10 feet with a 60 degree field of view. | ||

+ | |||

+ | ===== How are coordinates transformed? What are the different coordinate spaces? ===== | ||

+ | |||

+ | Object Coordinates are transformed by the ModelView matrix to produce Eye Coordinates. | ||

+ | |||

+ | Eye Coordinates are transformed by the Projection matrix to produce Clip Coordinates. | ||

+ | |||

+ | Clip Coordinate X, Y, and Z are divided by Clip Coordinate W to produce Normalized Device Coordinates. | ||

+ | |||

+ | Normalized Device Coordinates are scaled and translated by the viewport parameters to produce Window Coordinates. | ||

+ | |||

+ | Object coordinates are the raw coordinates you submit to OpenGL with a call to glVertex*() or glVertexPointer(). They represent the coordinates of your object or other geometry you want to render. | ||

+ | |||

+ | Many programmers use a World Coordinate system. Objects are often modeled in one coordinate system, then scaled, translated, and rotated into the world you're constructing. World Coordinates result from transforming Object Coordinates by the modelling transforms stored in the ModelView matrix. However, OpenGL has no concept of World Coordinates. World Coordinates are purely an application construct. | ||

+ | |||

+ | Eye Coordinates result from transforming Object Coordinates by the ModelView matrix. The ModelView matrix contains both modelling and viewing transformations that place the viewer at the origin with the view direction aligned with the negative Z axis. | ||

+ | |||

+ | Clip Coordinates result from transforming Eye Coordinates by the Projection matrix. Clip Coordinate space ranges from -Wc to Wc in all three axes, where Wc is the Clip Coordinate W value. OpenGL clips all coordinates outside this range. | ||

+ | |||

+ | Perspective division performed on the Clip Coordinates produces Normalized Device Coordinates, ranging from -1 to 1 in all three axes. | ||

+ | |||

+ | Window Coordinates result from scaling and translating Normalized Device Coordinates by the viewport. The parameters to glViewport() and glDepthRange() control this transformation. With the viewport, you can map the Normalized Device Coordinate cube to any location in your window and depth buffer. | ||

+ | |||

+ | For more information, see the [http://www.opengl.org/resources/faq/technical/gettingstarted.htm#gett0002 OpenGL Specification], Figure 2.6. | ||

+ | |||

+ | ===== How do I transform only one object in my scene or give each object its own transform? ===== | ||

+ | |||

+ | OpenGL provides matrix stacks specifically for this purpose. In this case, use the ModelView matrix stack. | ||

+ | |||

+ | A typical OpenGL application first sets the matrix mode with a call to glMatrixMode(GL_MODELVIEW) and loads a viewing transform, perhaps with a call to gluLookAt(). More information is available on [http://www.opengl.org/resources/faq/technical/viewing.htm gluLookAt()]. | ||

+ | |||

+ | Then the code renders each object in the scene with its own transformation by wrapping the rendering with calls to glPushMatrix() and glPopMatrix(). For example: | ||

+ | |||

+ | <source lang="c"> | ||

+ | glPushMatrix(); | ||

+ | glRotatef(90., 1., 0., 0.); | ||

+ | gluCylinder(quad, 1, 1, 2, 36, 12); | ||

+ | glPopMatrix(); | ||

+ | </source> | ||

+ | |||

+ | The above code renders a cylinder rotated 90 degrees around the X-axis. The ModelView matrix is restored to its previous value after the glPopMatrix() call. Similar call sequences can render subsequent objects in the scene. | ||

+ | |||

+ | ===== How do I draw 2D controls over my 3D rendering? ===== | ||

+ | |||

+ | The basic strategy is to set up a 2D projection for drawing controls. You can do this either on top of your 3D rendering or in overlay planes. If you do so on top of a 3D rendering, you'll need to redraw the controls at the end of every frame (immediately before swapping buffers). If you draw into the overlay planes, you only need to redraw the controls if you're updating them. | ||

+ | |||

+ | To set up a 2D projection, you need to change the Projection matrix. Normally, it's convenient to set up the projection so one world coordinate unit is equal to one screen pixel, as follows: | ||

+ | |||

+ | <source lang="c"> | ||

+ | glMatrixMode(GL_PROJECTION); | ||

+ | glLoadIdentity(); | ||

+ | gluOrtho2D(0, windowWidth, 0, windowHeight); | ||

+ | </source> | ||

+ | |||

+ | gluOrtho2D() sets up a Z range of -1 to 1, so you need to use one of the glVertex2*() functions to ensure your geometry isn't clipped by the zNear or zFar clipping planes. | ||

+ | |||

+ | Normally, the ModelView matrix is set to the identity when drawing 2D controls, though you may find it convenient to do otherwise (for example, you can draw repeated controls with interleaved translation matrices). | ||

+ | |||

+ | If exact pixelization is required, you might want to put a small translation in the ModelView matrix, as shown below: | ||

+ | |||

+ | <source lang="c"> | ||

+ | glMatrixMode(GL_MODELVIEW); | ||

+ | glLoadIdentity(); | ||

+ | glTranslatef(0.375, 0.375, 0.); | ||

+ | </source> | ||

+ | |||

+ | If you're drawing on top of a 3D-depth buffered image, you'll need to somehow disable depth testing while drawing your 2D geometry. You can do this by calling glDisable(GL_DEPTH_TEST) or glDepthFunc (GL_ALWAYS). Depending on your application, you might also simply clear the depth buffer before starting the 2D rendering. Finally, drawing all 2D geometry with a minimum Z coordinate is also a solution. | ||

+ | |||

+ | After the 2D projection is established as above, you can render normal OpenGL primitives to the screen, specifying their coordinates with XY pixel addresses (using OpenGL-centric screen coordinates, with (0,0) in the lower left). | ||

+ | |||

+ | ===== How do I bypass OpenGL matrix transformations and send 2D coordinates directly for rasterization? ===== | ||

+ | |||

+ | There isn't a mode switch to disable OpenGL matrix transformations. However, if you set either or both matrices to the identity with a glLoadIdentity() call, typical OpenGL implementations are intelligent enough to know that an identity transformation is a no-op and will act accordingly. | ||

+ | |||

+ | More detailed information on using OpenGL as a rasterization-only API is in the [http://www.3dgamedev.com/resources/openglfaq.txt OpenGL Game Developer’s FAQ]. | ||

+ | |||

+ | ===== What are the pros and cons of using absolute versus relative coordinates? ===== | ||

+ | |||

+ | Some OpenGL applications may need to render the same object in multiple locations in a single scene. OpenGL lets you do this two ways: | ||

+ | |||

+ | # Use “absolute coordinates". Maintain multiple copies of each object, each with its own unique set of vertices. You don't need to change the ModelView matrix to render the object at the desired location. | ||

+ | # Use “relative coordinates". Keep only one copy of the object, and render it multiple times by pushing the ModelView matrix stack, setting the desired transform, sending the geometry, and popping the stack. Repeat these steps for each object. | ||

+ | |||

+ | In general, frequent changes to state, such as to the ModelView matrix, can negatively impact your application’s performance. OpenGL can process your geometry faster if you don't wrap each individual primitive in a lot of changes to the ModelView matrix. | ||

+ | |||

+ | However, sometimes you need to weigh this against the memory savings of replicating geometry. Let's say you define a doorknob with high approximation, such as 200 or 300 triangles, and you're modeling a house with 50 doors in it, all of which have the same doorknob. It's probably preferable to use a single doorknob display list, with multiple unique transform matrices, rather than use absolute coordinates with 10-15K triangles in memory. | ||

+ | |||

+ | As with many computing issues, it's a trade-off between processing time and memory that you'll need to make on a case-by-case basis. | ||

+ | |||

+ | ===== How can I draw more than one view of the same scene? ===== | ||

+ | |||

+ | You can draw two views into the same window by using the glViewport() call. Set glViewport() to the area that you want the first view, set your scene’s view, and render. Then set glViewport() to the area for the second view, again set your scene’s view, and render. | ||

+ | |||

+ | You need to be aware that some operations don't pay attention to the glViewport, such as SwapBuffers and glClear(). SwapBuffers always swaps the entire window. However, you can restrain glClear() to a rectangular window by using the scissor rectangle. | ||

+ | |||

+ | Your application might only allow different views in separate windows. If so, you need to perform a MakeCurrent operation between the two renderings. If the two windows share a context, you need to change the scene’s view as described above. This might not be necessary if your application uses separate contexts for each window. | ||

+ | |||

+ | ===== How do I transform my objects around a fixed coordinate system rather than the object's local coordinate system? ===== | ||

+ | |||

+ | If you rotate an object around its Y-axis, you'll find that the X- and Z-axes rotate with the object. A subsequent rotation around one of these axes rotates around the newly transformed axis and not the original axis. It's often desirable to perform transformations in a fixed coordinate system rather than the object’s local coordinate system. | ||

+ | |||

+ | The [http://www.3dgamedev.com/resources/openglfaq.txt OpenGL Game Developer’s FAQ] contains information on using quaternions to store rotations, which may be useful in solving this problem. | ||

+ | |||

+ | The root cause of the problem is that OpenGL matrix operations postmultiply onto the matrix stack, thus causing transformations to occur in object space. To affect screen space transformations, you need to premultiply. OpenGL doesn't provide a mode switch for the order of matrix multiplication, so you need to premultiply by hand. An application might implement this by retrieving the current matrix after each frame. The application multiplies new transformations for the next frame on top of an identity matrix and multiplies the accumulated current transformations (from the last frame) onto those transformations using glMultMatrix(). | ||

+ | |||

+ | You need to be aware that retrieving the ModelView matrix once per frame might have a detrimental impact on your application’s performance. However, you need to benchmark this operation, because the performance will vary from one implementation to the next. | ||

+ | |||

+ | ===== What are the pros and cons of using glFrustum() versus gluPerspective()? Why would I want to use one over the other? ===== | ||

+ | |||

+ | glFrustum() and gluPerspective() both produce perspective projection matrices that you can use to transform from eye coordinate space to clip coordinate space. The primary difference between the two is that glFrustum() is more general and allows off-axis projections, while gluPerspective() only produces symmetrical (on-axis) projections. Indeed, you can use glFrustum() to implement gluPerspective(). However, aside from the layering of function calls that is a natural part of the GLU interface, there is no performance advantage to using matrices generated by glFrustum() over gluPerspective(). | ||

+ | |||

+ | Since glFrustum() is more general than gluPerspective(), you can use it in cases when gluPerspective() can't be used. Some examples include [http://www.opengl.org/resources/faq/technical/lights.htm#ligh0130 projection shadows], tiled renderings, and stereo views. | ||

+ | |||

+ | Tiled rendering uses multiple off-axis projections to render different sections of a scene. The results are assembled into one large image array to produce the final image. This is often necessary when the desired dimensions of the final rendering exceed the OpenGL implementation's maximum viewport size. | ||

+ | |||

+ | In a stereo view, two renderings of the same scene are done with the view location slightly shifted. Since the view axis is right between the “eyes”, each view must use a slightly off-axis projection to either side to achieve correct visual results. | ||

+ | |||

+ | ===== How can I make a call to glFrustum() that matches my call to gluPerspective()? ===== | ||

+ | |||

+ | The field of view (fov) of your glFrustum() call is: | ||

+ | |||

+ | fov*0.5 = arctan ((top-bottom)*0.5 / near) | ||

+ | |||

+ | Since bottom == -top for the symmetrical projection that gluPerspective() produces, then: | ||

+ | |||

+ | top = tan(fov*0.5) * near | ||

+ | bottom = -top | ||

+ | |||

+ | Note: fov must be in radians for the above formula to work with the C math library. If you have computer your fov in degrees (as in the call to gluPerspective()), then calculate top as follows: | ||

+ | |||

+ | top = tan(fov*3.14159/360.0) * near | ||

+ | |||

+ | The left and right parameters are simply functions of the top, bottom, and aspect: | ||

+ | |||

+ | top /= aspectYScale | ||

+ | bottom /= aspectYScale | ||

+ | left = aspect * bottom | ||

+ | right = aspect * top | ||

+ | |||

+ | The OpenGL Reference Manual ([http://www.opengl.org/resources/faq/technical/gettingstarted.htm#gett0004 where do I get this?]) shows the matrices produced by both functions. | ||

+ | |||

+ | ===== How do I draw a full-screen quad? ===== | ||

+ | |||

+ | This question usually means, "How do I draw a quad that fills the entire OpenGL viewport?" There are many ways to do this. | ||

+ | |||

+ | The most straightforward method is to set the desired color, set both the Projection and ModelView matrices to the identity, and call glRectf() or draw an equivalent GL_QUADS primitive. Your rectangle or quad's Z value should be in the range of –1.0 to 1.0, with –1.0 mapping to the zNear clipping plane, and 1.0 to the zFar clipping plane. | ||

+ | |||

+ | As an example, here's how to draw a full-screen quad at the zNear clipping plane: | ||

+ | |||

+ | <source lang="c"> | ||

+ | glMatrixMode(GL_MODELVIEW); | ||

+ | glPushMatrix(); | ||

+ | glLoadIdentity(); | ||

+ | glMatrixMode(GL_PROJECTION); | ||

+ | glPushMatrix(); | ||

+ | glLoadIdentity(); | ||

+ | glBegin(GL_QUADS); | ||

+ | glVertex3i(-1, -1, -1); | ||

+ | glVertex3i(1, -1, -1); | ||

+ | glVertex3i(1, 1, -1); | ||

+ | glVertex3i(-1, 1, -1); | ||

+ | glEnd(); | ||

+ | glPopMatrix(); | ||

+ | glMatrixMode(GL_MODELVIEW); | ||

+ | glPopMatrix(); | ||

+ | </source> | ||

+ | |||

+ | Your application might want the quad to have a maximum Z value, in which case 1 should be used for the Z value instead of -1. | ||

+ | |||

+ | When painting a full-screen quad, it might be useful to mask off some buffers so that only specified buffers are touched. For example, you might mask off the color buffer and set the depth function to GL_ALWAYS, so only the depth buffer is painted. Also, you can set masks to allow the stencil buffer to be set or any combination of buffers. | ||

+ | |||

+ | ===== How can I find the screen coordinates for a given object-space coordinate? ===== | ||

+ | |||

+ | You can use the GLU library gluProject() utility routine if you only need to find it for a few vertices. For a large number of coordinates, it can be more efficient to use the Feedback mechanism. | ||

+ | |||

+ | To use gluProject(), you'll need to provide the ModelView matrix, projection matrix, viewport, and input object space coordinates. Screen space coordinates are returned for X, Y, and Z, with Z being normalized (0 <= Z <= 1). | ||

+ | |||

+ | ===== How can I find the object-space coordinates for a pixel on the screen? ===== | ||

+ | |||

+ | The GLU library provides the gluUnProject() function for this purpose. | ||

+ | |||

+ | You'll need to read the depth buffer to obtain the input screen coordinate Z value at the X,Y location of interest. This can be coded as follows: | ||

+ | |||

+ | <pre> GLdouble z; | ||

+ | glReadPixels (x, y, 1, 1, GL_DEPTH_COMPONENT, GL_DOUBLE, &z);</pre> | ||

+ | |||

+ | Note that x and y are OpenGL-centric with (0,0) in the lower-left corner. | ||

+ | |||

+ | You'll need to provide the screen space X, Y, and Z values as input to gluUnProject() with the ModelView matrix, Projection matrix, and viewport that were current at the time the specific pixel of interest was rendered. | ||

+ | |||

+ | ===== How do I find the coordinates of a vertex transformed only by the ModelView matrix? ===== | ||

+ | |||

+ | It's often useful to obtain the eye coordinate space value of a vertex (i.e., the object space vertex transformed by the ModelView matrix). You can obtain this by retrieving the current ModelView matrix and performing simple vector / matrix multiplication. | ||

+ | |||

+ | ===== How do I get the active MODELVIEW or PROJECTION matrices? ===== | ||

+ | <source lang="c"> | ||

+ | GLfloat m[16]; | ||

+ | glGetFloatv(GL_MODELVIEW_MATRIX, m); | ||

+ | glGetFloatv(GL_PROJECTION_MATRIX, m); | ||

+ | </source> | ||

+ | ===== How do I calculate the object-space distance from the viewer to a given point? ===== | ||

+ | |||

+ | Transform the point into eye-coordinate space by multiplying it by the ModelView matrix. Then simply calculate its distance from the origin. (If this doesn't work, you may have incorrectly placed the view transform on the Projection matrix stack.) | ||

+ | |||

+ | To retrieve the current Modelview matrix: | ||

+ | <source lang="c"> | ||

+ | GLfloat m[16]; | ||

+ | glGetFloatv(GL_MODELVIEW_MATRIX, m); | ||

+ | </source> | ||

+ | As with any OpenGL call, you must have a context current with a window or drawable in order for glGet*() function calls to work. | ||

+ | |||

+ | ===== How do I keep my aspect ratio correct after a window resize? ===== | ||

+ | |||

+ | It depends on how you are setting your projection matrix. In any case, you'll need to know the new dimensions (width and height) of your window. How to obtain these depends on which platform you're using. In GLUT, for example, the dimensions are passed as parameters to the reshape function callback. | ||

+ | |||

+ | The following assumes you're maintaining a viewport that's the same size as your window. If you are not, substitute viewportWidth and viewportHeight for windowWidth and windowHeight. | ||

+ | |||

+ | If you're using gluPerspective() to set your Projection matrix, the second parameter controls the aspect ratio in which can be implemented into the first parameter using trigonometric math to re-calculate the FOV changing the aspect direction to extend vertically instead of horizontal as it follows: | ||

+ | |||

+ | gluPerspective(atan(tan(fov * 3.14159 / 360.0) / (float)windowWidth/(float)windowHeight) * 360.0 / 3.14159, (float)windowWidth/(float)windowHeight, zNear, zFar); | ||

+ | |||

+ | For best results, you might want to use conditional aspect to switch direction if it goes below a specified ratio: | ||

+ | |||

+ | float aspectYScale = 1.0; | ||

+ | if ( (float)windowWidth/(float)windowHeight < 1.7777777777777778 ) { | ||

+ | aspectYScale *= (float)windowWidth / (float)windowHeight / 1.7777777777777778; | ||

+ | } | ||

+ | gluPerspective(atan(tan(fov * 3.14159 / 360.0) / aspectYScale) * 360.0 / 3.14159, (float)windowWidth/(float)windowHeight, zNear, zFar); | ||

+ | |||

+ | When your program catches a window resize, you'll need to change your Projection matrix as follows: | ||

+ | |||

+ | <source lang="c"> | ||

+ | glMatrixMode(GL_PROJECTION); | ||

+ | glLoadIdentity(); | ||

+ | float aspectYScale = 1.0; | ||

+ | if ( aspect < conditionalaspect ) { | ||

+ | aspectYScale *= (float)windowWidth / (float)windowHeight / conditionalaspect; | ||

+ | } | ||

+ | gluPerspective(atan(tan(fov * 3.14159 / 360.0) / aspectYScale) * 360.0 / 3.14159, (float)windowWidth/(float)windowHeight, zNear, zFar); | ||

+ | </source> | ||

+ | |||

+ | If you're using glFrustum(), the aspect ratio varies with the width of the view volume to the height of the view volume. You might maintain a 1:1 aspect ratio with the following window resize code: | ||

+ | |||

+ | <source lang="c"> | ||

+ | float cx, halfWidth = windowWidth*0.5f; | ||

+ | float aspect = (float)windowWidth/(float)windowHeight; | ||

+ | float aspectYScale = 1.0; | ||

+ | if ( aspect < conditionalaspect ) { | ||

+ | aspectYScale *= aspect / conditionalaspect; | ||

+ | } | ||

+ | glMatrixMode(GL_PROJECTION); | ||

+ | glLoadIdentity(); | ||

+ | /* cx is the eye space center of the zNear plane in X */ | ||

+ | glFrustum(cx-halfWidth*aspect/aspectYScale, cx+halfWidth*aspect/aspectYScale, bottom/aspectYScale, top/aspectYScale, zNear, zFar); | ||

+ | </source> | ||

+ | |||

+ | glOrtho() and gluOrtho2D() are similar to glFrustum(). | ||

+ | |||

+ | ===== Can I make OpenGL use a left-handed coordinate space? ===== | ||

+ | |||

+ | OpenGL doesn't have a mode switch to change from right- to left-handed coordinates. However, you can easily obtain a left-handed coordinate system by multiplying a negative Z scale onto the ModelView matrix. For example: | ||

+ | |||

+ | <source lang="c"> | ||

+ | glMatrixMode(GL_MODELVIEW); | ||

+ | glLoadIdentity(); | ||

+ | glScalef(1., 1., -1.); | ||

+ | /* multiply view transforms as usual... */ | ||

+ | /* multiply model transforms as usual... */ | ||

+ | </source> | ||

+ | |||

+ | ===== How can I transform an object so that it points at or follows another object or point in my scene? ===== | ||

+ | |||

+ | You need to construct a matrix that transforms from your object's local coordinate system into a coordinate system that faces in the desired direction. See this [http://www.opengl.org/resources/faq/technical/lookat.cpp example code] to see how this type of matrix is created. | ||

+ | |||

+ | If you merely want to render an object so that it always faces the viewer, you might consider simply rendering it in eye-coordinate space with the ModelView matrix set to the identity. | ||

+ | |||

+ | ===== How can I transform an object with a given yaw, pitch, and roll? ===== | ||

+ | |||

+ | The upper left 3x3 portion of a transformation matrix is composed of the new X, Y, and Z axes of the post-transformation coordinate space. | ||

+ | |||

+ | If the new transform is a roll, compute new local Y and X axes by rotating them "roll" degrees around the local Z axis. Do similar calculations if the transform is a pitch or yaw. Then simply construct your transformation matrix by inserting the new local X, Y, and Z axes into the upper left 3x3 portion of an identity matrix. This matrix can be passed as a parameter to glMultMatrix(). | ||

+ | |||

+ | Further rotations should be computed around the new local axes. This will inevitably require rotation about an arbitrary axis, which can be confusing to inexperienced 3D programmers. This is a [http://www.opengl.org/resources/faq/technical/transformations.htm#tran0001 basic concept in linear algebra]. | ||

+ | |||

+ | Many programmers apply all three transformations -- yaw, pitch, and roll -- at once as successive glRotate() calls about the X, Y, and Z axes. This has the disadvantage of creating gimbal lock, in which the result depends on the order of glRotate() calls. | ||

+ | |||

+ | ===== How do I render a mirror? ===== | ||

+ | |||

+ | Render your scene twice, once as it is reflected in the mirror, then once from the normal (non-reflected) view. [http://www.opengl.org/resources/faq/technical/mirror.c Example code] demonstrates this technique. | ||

+ | |||

+ | For axis-aligned mirrors, such as a mirror on the YZ plane, the reflected scene can be rendered with a simple scale and translate. Scale by -1.0 in the axis corresponding to the mirror's normal, and translate by twice the mirror's distance from the origin. Rendering the scene with these transforms in place will yield the scene reflected in the mirror. Use the matrix stack to restore the view transform to its previous value. | ||

+ | |||

+ | Next, clear the depth buffer with a call to glClear(GL_DEPTH_BUFFER_BIT). Then render the mirror. For a perfectly reflecting mirror, render into the depth buffer only. Real mirrors are not perfect reflectors, as they absorb some light. To create this effect, use blending to render a black mirror with an alpha of 0.05. glBlendFunc(GL_SRC_ALPHA,GL_ONE_MINUS_SRC_ALPHA) is a good blending function for this purpose. | ||

+ | |||

+ | Finally, render the non-reflected scene. Since the entire reflected scene exists in the color buffer, and not just the portion of the reflected scene in the mirror, you will need to touch all pixels to overwrite areas of the reflected scene that should not be visible. | ||

+ | |||

+ | ===== How can I do my own perspective scaling? ===== | ||

+ | |||

+ | OpenGL multiplies your coordinates by the ModelView matrix, then by the Projection matrix to get clip coordinates. It then performs the perspective divide to obtain normalized device coordinates. It's the perspective division step that creates a perspective rendering, with geometry in the distance appearing smaller than the geometry in the foreground. The perspective division stage is accomplished by dividing your XYZ clipping coordinate values by the clipping coordinate W value, such as: | ||

+ | |||

+ | Xndc = Xcc/Wcc | ||

+ | Yndc = Ycc/Wcc | ||

+ | Zndc = Zcc/Wcc | ||

+ | |||

+ | To do your own perspective correction, you need to obtain the clipping coordinate W value. The feedback buffer provides homogenous coordinates with XYZ in device coordinates and W in clip coordinates. You might also glGetFloatv(GL_CURRENT_RASTER_POSITION,…) and the W value will again be in clipping coordinates, while XYZ are in device coordinates. | ||

+ | |||

+ | [[Category:General OpenGL]] | ||

+ | [[Category:Deprecated]] |

## Latest revision as of 11:05, 6 August 2019

Warning: This article describes legacy OpenGL APIs that have been removed from core OpenGL 3.1 and above (they are only deprecated in OpenGL 3.0). It is recommended that you not use this functionality in your programs. |

## Contents

- 1 How does the camera work in OpenGL?
- 2 How can I move my eye, or camera, in my scene?
- 3 Where should my camera go, the ModelView or Projection matrix?
- 4 How do I implement a zoom operation?
- 5 Given the current ModelView matrix, how can I determine the object-space location of the camera?
- 6 How do I make the camera "orbit" around a point in my scene?
- 7 How can I automatically calculate a view that displays my entire model? (I know the bounding sphere and up vector.)
- 8 Why doesn't gluLookAt work?
- 9 How do I get a specified point (XYZ) to appear at the center of the scene?
- 10 I put my gluLookAt() call on my Projection matrix and now fog, lighting, and texture mapping don't work correctly. What happened?
- 11 How can I create a stereo view?
- 12 I can't get transformations to work. Where can I learn more about matrices?
- 13 Are OpenGL matrices column-major or row-major?
- 14 What are OpenGL coordinate units?
- 15 How are coordinates transformed? What are the different coordinate spaces?
- 16 How do I transform only one object in my scene or give each object its own transform?
- 17 How do I draw 2D controls over my 3D rendering?
- 18 How do I bypass OpenGL matrix transformations and send 2D coordinates directly for rasterization?
- 19 What are the pros and cons of using absolute versus relative coordinates?
- 20 How can I draw more than one view of the same scene?
- 21 How do I transform my objects around a fixed coordinate system rather than the object's local coordinate system?
- 22 What are the pros and cons of using glFrustum() versus gluPerspective()? Why would I want to use one over the other?
- 23 How can I make a call to glFrustum() that matches my call to gluPerspective()?
- 24 How do I draw a full-screen quad?
- 25 How can I find the screen coordinates for a given object-space coordinate?
- 26 How can I find the object-space coordinates for a pixel on the screen?
- 27 How do I find the coordinates of a vertex transformed only by the ModelView matrix?
- 28 How do I get the active MODELVIEW or PROJECTION matrices?
- 29 How do I calculate the object-space distance from the viewer to a given point?
- 30 How do I keep my aspect ratio correct after a window resize?
- 31 Can I make OpenGL use a left-handed coordinate space?
- 32 How can I transform an object so that it points at or follows another object or point in my scene?
- 33 How can I transform an object with a given yaw, pitch, and roll?
- 34 How do I render a mirror?
- 35 How can I do my own perspective scaling?

##### How does the camera work in OpenGL?

As far as OpenGL is concerned, there is no camera. More specifically, the camera is always located at the eye space coordinate (0.0, 0.0, 0.0). To give the appearance of moving the camera, your OpenGL application must move the scene with the inverse of the camera transformation by placing it on the MODELVIEW matrix. This is commonly referred to as the viewing transformation.

In practice this is mathematically equivalent to a camera transformation but more efficient because model transformations and camera transformations are concatenated to a single matrix. As a result though, certain operations must be performed when the camera and only the camera is on the MODELVIEW matrix. For example to position a light source in world space it most be positioned while the viewing transformation and only the viewing transformation is applied to the MODELVIEW matrix.

##### How can I move my eye, or camera, in my scene?

OpenGL doesn't provide an interface to do this using a camera model. However, the GLU library provides the gluLookAt() function, which takes an eye position, a position to look at, and an up vector, all in object space coordinates. This function computes the inverse camera transform according to its parameters and multiplies it onto the current matrix stack.

##### Where should my camera go, the ModelView or Projection matrix?

The GL_PROJECTION matrix should contain only the projection transformation calls it needs to transform eye space coordinates into clip coordinates.

The GL_MODELVIEW matrix, as its name implies, should contain modeling and viewing transformations, which transform object space coordinates into eye space coordinates. Remember to place the camera transformations on the GL_MODELVIEW matrix and never on the GL_PROJECTION matrix.

Think of the projection matrix as describing the attributes of your camera, such as field of view, focal length, fish eye lens, etc. Think of the ModelView matrix as where you stand with the camera and the direction you point it.

The game dev FAQ has good information on these two matrices.

Read Steve Baker's article on projection abuse. This article is highly recommended and well-written. It's helped several new OpenGL programmers.

##### How do I implement a zoom operation?

A simple method for zooming is to use a uniform scale on the ModelView matrix. However, this often results in clipping by the zNear and zFar clipping planes if the model is scaled too large.

A better method is to restrict the width and height of the view volume in the Projection matrix.

For example, your program might maintain a zoom factor based on user input, which is a floating-point number. When set to a value of 1.0, no zooming takes place. Larger values result in greater zooming or a more restricted field of view, while smaller values cause the opposite to occur. Code to create this effect might look like:

```
static float zoomFactor; /* Global, if you want. Modified by user input. Initially 1.0 */
/* A routine for setting the projection matrix. May be called from a resize
event handler in a typical application. Takes integer width and height
dimensions of the drawing area. Creates a projection matrix with correct
aspect ratio and zoom factor. */
void setProjectionMatrix (int width, int height, float conditionalaspect)
{
glMatrixMode(GL_PROJECTION);
glLoadIdentity();
if ( (float)width / (float)height < conditionalaspect ) { // Adjust zoom factor to extend vertical aspect ratio if below the aspect ratio constraint otherwise extend horizontal. By default, the aspect constraint is 1.0.
zoomfactor *= ((float)width / (float)height) / conditionalaspect;
}
gluPerspective(atan(tan(50.0 * 3.14159 / 360.0) / zoomFactor) * 360.0 / 3.14159, (float)width/(float)height, zNear, zFar);
/* ...Where 'zNear' and 'zFar' are up to you to fill in. */
}
```

Instead of gluPerspective(), your application might use glFrustum(). This gets tricky, because the left, right, bottom, and top parameters, along with the zNear plane distance, also affect the field of view. Assuming you desire to keep a constant zNear plane distance (a reasonable assumption), glFrustum() code might look like this:

```
glFrustum(left/zoomFactor, right/zoomFactor, bottom/zoomFactor, top/zoomFactor, zNear, zFar);
```

glOrtho() is similar.

##### Given the current ModelView matrix, how can I determine the object-space location of the camera?

The "camera" or viewpoint is at (0., 0., 0.) in eye space. When you turn this into a vector [0 0 0 1] and multiply it by the inverse of the ModelView matrix, the resulting vector is the object-space location of the camera.

OpenGL doesn't let you inquire (through a glGet* routine) the inverse of the ModelView matrix. You'll need to compute the inverse with your own code.

##### How do I make the camera "orbit" around a point in my scene?

You can simulate an orbit by translating/rotating the scene/object and leaving your camera in the same place. For example, to orbit an object placed somewhere on the Y axis, while continuously looking at the origin, you might do this:

```
gluLookAt(camera[0], camera[1], camera[2], /* look from camera XYZ */
0, 0, 0, /* look at the origin */
0, 1, 0); /* positive Y up vector */
glRotatef(orbitDegrees, 0.f, 1.f, 0.f);/* orbit the Y axis */
/* ...where orbitDegrees is derived from mouse motion */
glCallList(SCENE); /* draw the scene */
```

If you insist on physically orbiting the camera position, you'll need to transform the current camera position vector before using it in your viewing transformations.

In either event, I recommend you investigate gluLookAt() (if you aren't using this routine already).

##### How can I automatically calculate a view that displays my entire model? (I know the bounding sphere and up vector.)

The following is from a posting by Dave Shreiner on setting up a basic viewing system:

First, compute a bounding sphere for all objects in your scene. This should provide you with two bits of information: the center of the sphere (let ( c.x, c.y, c.z ) be that point) and its diameter (call it "diam").

Next, choose a value for the zNear clipping plane. General guidelines are to choose something larger than, but close to 1.0. So, let's say you set

```
zNear = 1.0;
zFar = zNear + diam;
```

Structure your matrix calls in this order (for an Orthographic projection):

```
GLdouble left = c.x - diam;
GLdouble right = c.x + diam;
GLdouble bottom c.y - diam;
GLdouble top = c.y + diam;
glMatrixMode(GL_PROJECTION);
glLoadIdentity();
glOrtho(left, right, bottom, top, zNear, zFar);
glMatrixMode(GL_MODELVIEW);
glLoadIdentity();
```

This approach should center your objects in the middle of the window and stretch them to fit (i.e., its assuming that you're using a window with aspect ratio = 1.0). If your window isn't square, compute left, right, bottom, and top, as above, and put in the following logic before the call to glOrtho():

```
GLdouble aspect = (GLdouble) windowWidth / windowHeight;
if ( aspect < 1.0 ) { // window taller than wide
bottom /= aspect;
top /= aspect;
} else {
left *= aspect;
right *= aspect;
}
```

The above code should position the objects in your scene appropriately. If you intend to manipulate (i.e. rotate, etc.), you need to add a viewing transform to it.

A typical viewing transform will go on the ModelView matrix and might look like this:

`gluLookAt(0., 0., 2.*diam, c.x, c.y, c.z, 0.0, 1.0, 0.0);`

##### Why doesn't gluLookAt work?

This is usually caused by incorrect transformations.

Assuming you are using gluPerspective() on the Projection matrix stack with zNear and zFar as the third and fourth parameters, you need to set gluLookAt on the ModelView matrix stack, and pass parameters so your geometry falls between zNear and zFar.

It's usually best to experiment with a simple piece of code when you're trying to understand viewing transformations. Let's say you are trying to look at a unit sphere centered on the origin. You'll want to set up your transformations as follows:

```
glMatrixMode(GL_PROJECTION);
glLoadIdentity();
gluPerspective(atan(tan(50.0 * 3.14159 / 360.0) / 1.0) * 360.0 / 3.141593, 1.0, 3.0, 7.0);
glMatrixMode(GL_MODELVIEW);
glLoadIdentity();
gluLookAt(0.0, 0.0, 5.0,
0.0, 0.0, 0.0,
0.0, 1.0, 0.0);
```

It's important to note how the Projection and ModelView transforms work together.

In this example, the Projection transform sets up a 50.0-degree field of view with trigonometric functions to add a zoom factor sub-parameter, with an aspect ratio and zoom factor of 1.0. The zNear clipping plane is 3.0 units in front of the eye, and the zFar clipping plane is 7.0 units in front of the eye. This leaves a Z volume distance of 4.0 units, ample room for a unit sphere.

The ModelView transform sets the eye position at (0.0, 0.0, 5.0), and the look-at point is the origin in the center of our unit sphere. Note that the eye position is 5.0 units away from the look at point. This is important, because a distance of 5.0 units in front of the eye is in the middle of the Z volume that the Projection transform defines. If the gluLookAt() call had placed the eye at (0.0, 0.0, 1.0), it would produce a distance of 1.0 to the origin. This isn't long enough to include the sphere in the view volume, and it would be clipped by the zNear clipping plane.

Similarly, if you place the eye at (0.0, 0.0, 10.0), the distance of 10.0 to the look at point will result in the unit sphere being 10.0 units away from the eye and far behind the zFar clipping plane placed at 7.0 units.

If this has confused you, read up on transformations in the OpenGL red book or OpenGL Specification. After you understand object coordinate space, eye coordinate space, and clip coordinate space, the above should become clear. Also, experiment with small test programs. If you're having trouble getting the correct transforms in your main application project, it can be educational to write a small piece of code that tries to reproduce the problem with simpler geometry.

##### How do I get a specified point (XYZ) to appear at the center of the scene?

gluLookAt() is the easiest way to do this. Simply set the X, Y, and Z values of your point as the fourth, fifth, and sixth parameters to gluLookAt().

##### I put my gluLookAt() call on my Projection matrix and now fog, lighting, and texture mapping don't work correctly. What happened?

Often this is caused by placing the transformation on the wrong matrix, look at question 3 for an explanation of this problem. However occasionally, and in particular for lighting, this can be caused because the lights were positioned when the wrong matrix is on the MODELVIEW matrix stack. When a light is positioned in eye space, i.e. relative to the eye, it should be positioned when an identity matrix is on the MODELVIEW stack. When a light is positioned in the world it should be positioned when the viewing matrix is on the MODELVIEW stack. When the light is positioned relative to an object under transformation it should be positioned when that object's model matrix has been multiplied with the viewing matrix on the MODELVIEW stack, remembering that it will have to be positioned before anything lit by it is rendered. If any light moves relative to the eye between frames it must be repositioned each frame using the appropriate matrix.

##### How can I create a stereo view?

Stereo viewing is accomplished by presenting a different image to the left and right eyes of the viewer. These images must be appropriate for the viewers relationship to the display they are looking at, much moreso than a mono 3D image. In addition the method used is tied closely to the display technology being used. Some graphics systems and display devices support stereo viewing in hardware and support features like left and right framebuffers in addition to the front and back buffers of conventional double buffered systems. Other systems support stereo correctly when two viewports are created in specific screen regions and specific video mode is used to send these to the screen. In conjunction with these modes a viewer often wears glasses either shuttered or polarized to select the displayed image appropriate to each eye. However even without these graphics features a developer can generate stereo views using features like color filtering where colored filters select an image based on red or blue filters and draw left and right eye images to red and blue framebuffer components for example, or even more simply just have multiple systems or graphics cards (or even a single card) generate two entirely separate video signals, for which a separate left and right eye image is drawn. The video is then sent to the appropriate eye either using a display employing polarizing filters or a head mounted display or some other custom display operating on similar principals.

From an OpenGL perspective, the requirements of stereo rendering are to use the appropriate setup to render to left and right eyes (be it color masks, separate contexts or different viewports) and then match the geometry of the OpenGL projection to the relationship of the viewer's left and right eyes with the display. The final OpenGL requirement is that the position of the eyes in the 'virtual' world must be given a pupil separation on the modelview stack, this separation would of course be a translation in eye space, but could be calculated in other equivalent ways.

Paul Bourke has assembled information on stereo OpenGL viewing.

##### I can't get transformations to work. Where can I learn more about matrices?

A thorough explanation of basic matrix math and linear algebra is beyond the scope of this FAQ. These concepts are taught in high school math classes in the United States.

If you understand the basics, but just get confused (a common problem even for the experienced!), read through Steve Baker's review of matrix concepts and his article on Euler angles.

Delphi code for performing basic vector, matrix, and quaternion operations can be found here.

##### 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.

##### What are OpenGL coordinate units?

The short answer: Anything you want them to be.

Depending on the contents of your geometry database, it may be convenient for your application to treat one OpenGL coordinate unit as being equal to one millimeter or one parsec or anything in between (or larger or smaller).

OpenGL also lets you specify your geometry with coordinates of differing values. For example, you may find it convenient to model an airplane's controls in centimeters, its fuselage in meters, and a world to fly around in kilometers. OpenGL's ModelView matrix can then scale these different coordinate systems into the same eye coordinate space.

It's the application's responsibility to ensure that the Projection and ModelView matrices are constructed to provide an image that keeps the viewer at an appropriate distance, with an appropriate field of view, and keeps the zNear and zFar clipping planes at an appropriate range. An application that displays molecules in micron scale, for example, would probably not want to place the viewer at a distance of 10 feet with a 60 degree field of view.

##### How are coordinates transformed? What are the different coordinate spaces?

Object Coordinates are transformed by the ModelView matrix to produce Eye Coordinates.

Eye Coordinates are transformed by the Projection matrix to produce Clip Coordinates.

Clip Coordinate X, Y, and Z are divided by Clip Coordinate W to produce Normalized Device Coordinates.

Normalized Device Coordinates are scaled and translated by the viewport parameters to produce Window Coordinates.

Object coordinates are the raw coordinates you submit to OpenGL with a call to glVertex*() or glVertexPointer(). They represent the coordinates of your object or other geometry you want to render.

Many programmers use a World Coordinate system. Objects are often modeled in one coordinate system, then scaled, translated, and rotated into the world you're constructing. World Coordinates result from transforming Object Coordinates by the modelling transforms stored in the ModelView matrix. However, OpenGL has no concept of World Coordinates. World Coordinates are purely an application construct.

Eye Coordinates result from transforming Object Coordinates by the ModelView matrix. The ModelView matrix contains both modelling and viewing transformations that place the viewer at the origin with the view direction aligned with the negative Z axis.

Clip Coordinates result from transforming Eye Coordinates by the Projection matrix. Clip Coordinate space ranges from -Wc to Wc in all three axes, where Wc is the Clip Coordinate W value. OpenGL clips all coordinates outside this range.

Perspective division performed on the Clip Coordinates produces Normalized Device Coordinates, ranging from -1 to 1 in all three axes.

Window Coordinates result from scaling and translating Normalized Device Coordinates by the viewport. The parameters to glViewport() and glDepthRange() control this transformation. With the viewport, you can map the Normalized Device Coordinate cube to any location in your window and depth buffer.

For more information, see the OpenGL Specification, Figure 2.6.

##### How do I transform only one object in my scene or give each object its own transform?

OpenGL provides matrix stacks specifically for this purpose. In this case, use the ModelView matrix stack.

A typical OpenGL application first sets the matrix mode with a call to glMatrixMode(GL_MODELVIEW) and loads a viewing transform, perhaps with a call to gluLookAt(). More information is available on gluLookAt().

Then the code renders each object in the scene with its own transformation by wrapping the rendering with calls to glPushMatrix() and glPopMatrix(). For example:

```
glPushMatrix();
glRotatef(90., 1., 0., 0.);
gluCylinder(quad, 1, 1, 2, 36, 12);
glPopMatrix();
```

The above code renders a cylinder rotated 90 degrees around the X-axis. The ModelView matrix is restored to its previous value after the glPopMatrix() call. Similar call sequences can render subsequent objects in the scene.

##### How do I draw 2D controls over my 3D rendering?

The basic strategy is to set up a 2D projection for drawing controls. You can do this either on top of your 3D rendering or in overlay planes. If you do so on top of a 3D rendering, you'll need to redraw the controls at the end of every frame (immediately before swapping buffers). If you draw into the overlay planes, you only need to redraw the controls if you're updating them.

To set up a 2D projection, you need to change the Projection matrix. Normally, it's convenient to set up the projection so one world coordinate unit is equal to one screen pixel, as follows:

```
glMatrixMode(GL_PROJECTION);
glLoadIdentity();
gluOrtho2D(0, windowWidth, 0, windowHeight);
```

gluOrtho2D() sets up a Z range of -1 to 1, so you need to use one of the glVertex2*() functions to ensure your geometry isn't clipped by the zNear or zFar clipping planes.

Normally, the ModelView matrix is set to the identity when drawing 2D controls, though you may find it convenient to do otherwise (for example, you can draw repeated controls with interleaved translation matrices).

If exact pixelization is required, you might want to put a small translation in the ModelView matrix, as shown below:

```
glMatrixMode(GL_MODELVIEW);
glLoadIdentity();
glTranslatef(0.375, 0.375, 0.);
```

If you're drawing on top of a 3D-depth buffered image, you'll need to somehow disable depth testing while drawing your 2D geometry. You can do this by calling glDisable(GL_DEPTH_TEST) or glDepthFunc (GL_ALWAYS). Depending on your application, you might also simply clear the depth buffer before starting the 2D rendering. Finally, drawing all 2D geometry with a minimum Z coordinate is also a solution.

After the 2D projection is established as above, you can render normal OpenGL primitives to the screen, specifying their coordinates with XY pixel addresses (using OpenGL-centric screen coordinates, with (0,0) in the lower left).

##### How do I bypass OpenGL matrix transformations and send 2D coordinates directly for rasterization?

There isn't a mode switch to disable OpenGL matrix transformations. However, if you set either or both matrices to the identity with a glLoadIdentity() call, typical OpenGL implementations are intelligent enough to know that an identity transformation is a no-op and will act accordingly.

More detailed information on using OpenGL as a rasterization-only API is in the OpenGL Game Developer’s FAQ.

##### What are the pros and cons of using absolute versus relative coordinates?

Some OpenGL applications may need to render the same object in multiple locations in a single scene. OpenGL lets you do this two ways:

- Use “absolute coordinates". Maintain multiple copies of each object, each with its own unique set of vertices. You don't need to change the ModelView matrix to render the object at the desired location.
- Use “relative coordinates". Keep only one copy of the object, and render it multiple times by pushing the ModelView matrix stack, setting the desired transform, sending the geometry, and popping the stack. Repeat these steps for each object.

In general, frequent changes to state, such as to the ModelView matrix, can negatively impact your application’s performance. OpenGL can process your geometry faster if you don't wrap each individual primitive in a lot of changes to the ModelView matrix.

However, sometimes you need to weigh this against the memory savings of replicating geometry. Let's say you define a doorknob with high approximation, such as 200 or 300 triangles, and you're modeling a house with 50 doors in it, all of which have the same doorknob. It's probably preferable to use a single doorknob display list, with multiple unique transform matrices, rather than use absolute coordinates with 10-15K triangles in memory.

As with many computing issues, it's a trade-off between processing time and memory that you'll need to make on a case-by-case basis.

##### How can I draw more than one view of the same scene?

You can draw two views into the same window by using the glViewport() call. Set glViewport() to the area that you want the first view, set your scene’s view, and render. Then set glViewport() to the area for the second view, again set your scene’s view, and render.

You need to be aware that some operations don't pay attention to the glViewport, such as SwapBuffers and glClear(). SwapBuffers always swaps the entire window. However, you can restrain glClear() to a rectangular window by using the scissor rectangle.

Your application might only allow different views in separate windows. If so, you need to perform a MakeCurrent operation between the two renderings. If the two windows share a context, you need to change the scene’s view as described above. This might not be necessary if your application uses separate contexts for each window.

##### How do I transform my objects around a fixed coordinate system rather than the object's local coordinate system?

If you rotate an object around its Y-axis, you'll find that the X- and Z-axes rotate with the object. A subsequent rotation around one of these axes rotates around the newly transformed axis and not the original axis. It's often desirable to perform transformations in a fixed coordinate system rather than the object’s local coordinate system.

The OpenGL Game Developer’s FAQ contains information on using quaternions to store rotations, which may be useful in solving this problem.

The root cause of the problem is that OpenGL matrix operations postmultiply onto the matrix stack, thus causing transformations to occur in object space. To affect screen space transformations, you need to premultiply. OpenGL doesn't provide a mode switch for the order of matrix multiplication, so you need to premultiply by hand. An application might implement this by retrieving the current matrix after each frame. The application multiplies new transformations for the next frame on top of an identity matrix and multiplies the accumulated current transformations (from the last frame) onto those transformations using glMultMatrix().

You need to be aware that retrieving the ModelView matrix once per frame might have a detrimental impact on your application’s performance. However, you need to benchmark this operation, because the performance will vary from one implementation to the next.

##### What are the pros and cons of using glFrustum() versus gluPerspective()? Why would I want to use one over the other?

glFrustum() and gluPerspective() both produce perspective projection matrices that you can use to transform from eye coordinate space to clip coordinate space. The primary difference between the two is that glFrustum() is more general and allows off-axis projections, while gluPerspective() only produces symmetrical (on-axis) projections. Indeed, you can use glFrustum() to implement gluPerspective(). However, aside from the layering of function calls that is a natural part of the GLU interface, there is no performance advantage to using matrices generated by glFrustum() over gluPerspective().

Since glFrustum() is more general than gluPerspective(), you can use it in cases when gluPerspective() can't be used. Some examples include projection shadows, tiled renderings, and stereo views.

Tiled rendering uses multiple off-axis projections to render different sections of a scene. The results are assembled into one large image array to produce the final image. This is often necessary when the desired dimensions of the final rendering exceed the OpenGL implementation's maximum viewport size.

In a stereo view, two renderings of the same scene are done with the view location slightly shifted. Since the view axis is right between the “eyes”, each view must use a slightly off-axis projection to either side to achieve correct visual results.

##### How can I make a call to glFrustum() that matches my call to gluPerspective()?

The field of view (fov) of your glFrustum() call is:

fov*0.5 = arctan ((top-bottom)*0.5 / near)

Since bottom == -top for the symmetrical projection that gluPerspective() produces, then:

top = tan(fov*0.5) * near bottom = -top

Note: fov must be in radians for the above formula to work with the C math library. If you have computer your fov in degrees (as in the call to gluPerspective()), then calculate top as follows:

top = tan(fov*3.14159/360.0) * near

The left and right parameters are simply functions of the top, bottom, and aspect:

top /= aspectYScale bottom /= aspectYScale left = aspect * bottom right = aspect * top

The OpenGL Reference Manual (where do I get this?) shows the matrices produced by both functions.

##### How do I draw a full-screen quad?

This question usually means, "How do I draw a quad that fills the entire OpenGL viewport?" There are many ways to do this.

The most straightforward method is to set the desired color, set both the Projection and ModelView matrices to the identity, and call glRectf() or draw an equivalent GL_QUADS primitive. Your rectangle or quad's Z value should be in the range of –1.0 to 1.0, with –1.0 mapping to the zNear clipping plane, and 1.0 to the zFar clipping plane.

As an example, here's how to draw a full-screen quad at the zNear clipping plane:

```
glMatrixMode(GL_MODELVIEW);
glPushMatrix();
glLoadIdentity();
glMatrixMode(GL_PROJECTION);
glPushMatrix();
glLoadIdentity();
glBegin(GL_QUADS);
glVertex3i(-1, -1, -1);
glVertex3i(1, -1, -1);
glVertex3i(1, 1, -1);
glVertex3i(-1, 1, -1);
glEnd();
glPopMatrix();
glMatrixMode(GL_MODELVIEW);
glPopMatrix();
```

Your application might want the quad to have a maximum Z value, in which case 1 should be used for the Z value instead of -1.

When painting a full-screen quad, it might be useful to mask off some buffers so that only specified buffers are touched. For example, you might mask off the color buffer and set the depth function to GL_ALWAYS, so only the depth buffer is painted. Also, you can set masks to allow the stencil buffer to be set or any combination of buffers.

##### How can I find the screen coordinates for a given object-space coordinate?

You can use the GLU library gluProject() utility routine if you only need to find it for a few vertices. For a large number of coordinates, it can be more efficient to use the Feedback mechanism.

To use gluProject(), you'll need to provide the ModelView matrix, projection matrix, viewport, and input object space coordinates. Screen space coordinates are returned for X, Y, and Z, with Z being normalized (0 <= Z <= 1).

##### How can I find the object-space coordinates for a pixel on the screen?

The GLU library provides the gluUnProject() function for this purpose.

You'll need to read the depth buffer to obtain the input screen coordinate Z value at the X,Y location of interest. This can be coded as follows:

GLdouble z; glReadPixels (x, y, 1, 1, GL_DEPTH_COMPONENT, GL_DOUBLE, &z);

Note that x and y are OpenGL-centric with (0,0) in the lower-left corner.

You'll need to provide the screen space X, Y, and Z values as input to gluUnProject() with the ModelView matrix, Projection matrix, and viewport that were current at the time the specific pixel of interest was rendered.

##### How do I find the coordinates of a vertex transformed only by the ModelView matrix?

It's often useful to obtain the eye coordinate space value of a vertex (i.e., the object space vertex transformed by the ModelView matrix). You can obtain this by retrieving the current ModelView matrix and performing simple vector / matrix multiplication.

##### How do I get the active MODELVIEW or PROJECTION matrices?

```
GLfloat m[16];
glGetFloatv(GL_MODELVIEW_MATRIX, m);
glGetFloatv(GL_PROJECTION_MATRIX, m);
```

##### How do I calculate the object-space distance from the viewer to a given point?

Transform the point into eye-coordinate space by multiplying it by the ModelView matrix. Then simply calculate its distance from the origin. (If this doesn't work, you may have incorrectly placed the view transform on the Projection matrix stack.)

To retrieve the current Modelview matrix:

```
GLfloat m[16];
glGetFloatv(GL_MODELVIEW_MATRIX, m);
```

As with any OpenGL call, you must have a context current with a window or drawable in order for glGet*() function calls to work.

##### How do I keep my aspect ratio correct after a window resize?

It depends on how you are setting your projection matrix. In any case, you'll need to know the new dimensions (width and height) of your window. How to obtain these depends on which platform you're using. In GLUT, for example, the dimensions are passed as parameters to the reshape function callback.

The following assumes you're maintaining a viewport that's the same size as your window. If you are not, substitute viewportWidth and viewportHeight for windowWidth and windowHeight.

If you're using gluPerspective() to set your Projection matrix, the second parameter controls the aspect ratio in which can be implemented into the first parameter using trigonometric math to re-calculate the FOV changing the aspect direction to extend vertically instead of horizontal as it follows:

gluPerspective(atan(tan(fov * 3.14159 / 360.0) / (float)windowWidth/(float)windowHeight) * 360.0 / 3.14159, (float)windowWidth/(float)windowHeight, zNear, zFar);

For best results, you might want to use conditional aspect to switch direction if it goes below a specified ratio:

float aspectYScale = 1.0; if ( (float)windowWidth/(float)windowHeight < 1.7777777777777778 ) { aspectYScale *= (float)windowWidth / (float)windowHeight / 1.7777777777777778; } gluPerspective(atan(tan(fov * 3.14159 / 360.0) / aspectYScale) * 360.0 / 3.14159, (float)windowWidth/(float)windowHeight, zNear, zFar);

When your program catches a window resize, you'll need to change your Projection matrix as follows:

```
glMatrixMode(GL_PROJECTION);
glLoadIdentity();
float aspectYScale = 1.0;
if ( aspect < conditionalaspect ) {
aspectYScale *= (float)windowWidth / (float)windowHeight / conditionalaspect;
}
gluPerspective(atan(tan(fov * 3.14159 / 360.0) / aspectYScale) * 360.0 / 3.14159, (float)windowWidth/(float)windowHeight, zNear, zFar);
```

If you're using glFrustum(), the aspect ratio varies with the width of the view volume to the height of the view volume. You might maintain a 1:1 aspect ratio with the following window resize code:

```
float cx, halfWidth = windowWidth*0.5f;
float aspect = (float)windowWidth/(float)windowHeight;
float aspectYScale = 1.0;
if ( aspect < conditionalaspect ) {
aspectYScale *= aspect / conditionalaspect;
}
glMatrixMode(GL_PROJECTION);
glLoadIdentity();
/* cx is the eye space center of the zNear plane in X */
glFrustum(cx-halfWidth*aspect/aspectYScale, cx+halfWidth*aspect/aspectYScale, bottom/aspectYScale, top/aspectYScale, zNear, zFar);
```

glOrtho() and gluOrtho2D() are similar to glFrustum().

##### Can I make OpenGL use a left-handed coordinate space?

OpenGL doesn't have a mode switch to change from right- to left-handed coordinates. However, you can easily obtain a left-handed coordinate system by multiplying a negative Z scale onto the ModelView matrix. For example:

```
glMatrixMode(GL_MODELVIEW);
glLoadIdentity();
glScalef(1., 1., -1.);
/* multiply view transforms as usual... */
/* multiply model transforms as usual... */
```

##### How can I transform an object so that it points at or follows another object or point in my scene?

You need to construct a matrix that transforms from your object's local coordinate system into a coordinate system that faces in the desired direction. See this example code to see how this type of matrix is created.

If you merely want to render an object so that it always faces the viewer, you might consider simply rendering it in eye-coordinate space with the ModelView matrix set to the identity.

##### How can I transform an object with a given yaw, pitch, and roll?

The upper left 3x3 portion of a transformation matrix is composed of the new X, Y, and Z axes of the post-transformation coordinate space.

If the new transform is a roll, compute new local Y and X axes by rotating them "roll" degrees around the local Z axis. Do similar calculations if the transform is a pitch or yaw. Then simply construct your transformation matrix by inserting the new local X, Y, and Z axes into the upper left 3x3 portion of an identity matrix. This matrix can be passed as a parameter to glMultMatrix().

Further rotations should be computed around the new local axes. This will inevitably require rotation about an arbitrary axis, which can be confusing to inexperienced 3D programmers. This is a basic concept in linear algebra.

Many programmers apply all three transformations -- yaw, pitch, and roll -- at once as successive glRotate() calls about the X, Y, and Z axes. This has the disadvantage of creating gimbal lock, in which the result depends on the order of glRotate() calls.

##### How do I render a mirror?

Render your scene twice, once as it is reflected in the mirror, then once from the normal (non-reflected) view. Example code demonstrates this technique.

For axis-aligned mirrors, such as a mirror on the YZ plane, the reflected scene can be rendered with a simple scale and translate. Scale by -1.0 in the axis corresponding to the mirror's normal, and translate by twice the mirror's distance from the origin. Rendering the scene with these transforms in place will yield the scene reflected in the mirror. Use the matrix stack to restore the view transform to its previous value.

Next, clear the depth buffer with a call to glClear(GL_DEPTH_BUFFER_BIT). Then render the mirror. For a perfectly reflecting mirror, render into the depth buffer only. Real mirrors are not perfect reflectors, as they absorb some light. To create this effect, use blending to render a black mirror with an alpha of 0.05. glBlendFunc(GL_SRC_ALPHA,GL_ONE_MINUS_SRC_ALPHA) is a good blending function for this purpose.

Finally, render the non-reflected scene. Since the entire reflected scene exists in the color buffer, and not just the portion of the reflected scene in the mirror, you will need to touch all pixels to overwrite areas of the reflected scene that should not be visible.

##### How can I do my own perspective scaling?

OpenGL multiplies your coordinates by the ModelView matrix, then by the Projection matrix to get clip coordinates. It then performs the perspective divide to obtain normalized device coordinates. It's the perspective division step that creates a perspective rendering, with geometry in the distance appearing smaller than the geometry in the foreground. The perspective division stage is accomplished by dividing your XYZ clipping coordinate values by the clipping coordinate W value, such as:

Xndc = Xcc/Wcc Yndc = Ycc/Wcc Zndc = Zcc/Wcc

To do your own perspective correction, you need to obtain the clipping coordinate W value. The feedback buffer provides homogenous coordinates with XYZ in device coordinates and W in clip coordinates. You might also glGetFloatv(GL_CURRENT_RASTER_POSITION,…) and the W value will again be in clipping coordinates, while XYZ are in device coordinates.