CS 488/688: Introduction to Computer Graphics
Fall 2016 Assignment 2: Pipeline
Your goal of this assignment is to write a program to draw a wireframe cube. You can apply modelling transformations to the cube, and viewing transformations to the camera. That might sound easy, especially in light of all the cubes in Assignment 1, but there's a catch: all you're allowed to do is draw lines directly in normalized device coordinates. You will be responsible for implementing the geometric pipeline, including perspective projection and clipping. This assignment provides a good way to see all the parts of the pipeline in a single place.
You should construct your cube using the eight vertices (±1, ±1, ±1). You must also draw two coordinate frames (sometimes called gnomons in this context). The first will represent the cube's local modelling coordinates; its origin is the cube's centre, and it will be subjected to every modelling, viewing and projection transformation applied to the cube, except for scaling. The second will represent world coordinates. These will be the same size as the modelling axes, but they will remain fixed at (0,0,0)—they will be subjected only to the viewing and projection transformations. Draw each gnomon so that its x, y, and z axes are visually distinct; the most obvious means of doing so is to draw them with different colours. (Though these coordinate frames are conceptually of unit length, you'll probably want to scale them when drawing them in order to ensure they're visible on screen.)
You will apply modelling transformations to the box (rotations, translations, and scales) and viewing transformations to the eyepoint (rotations and translations). The user interface will allow you to select which class of transformation to apply. In each mode, dragging with a combination of mouse buttons pressed will use the x position of the mouse to control the axes on which a transformation will act.
You will need to maintain four distinct coordinate systems in this assignment. Three of these coordinate systems are 3D and one is 2D: the box ("model") coordinates (3D), the eyepoint ("view") coordinates (3D), the universal ("world") coordinates (3D), and the display ("screen") 2D normalized device coordinates (which arise from the perspective projection of the eye's view onto the eye's xy plane).
The modelling transformations apply with respect to model coordinates (i.e., a model mode rotation about the x axis will rotate the box about its current x axis, not the world's x axis). The viewing transformations apply with respect to view coordinates (i.e., a view mode rotation about the x axis will appear to swing the objects in view up or down on the screen, since the eye's x axis appears parallel to the screen's horizontal axis). None of the modelling transformations will change world coordinates (i.e., the world gnomon never changes its location, though, of course, it may drift out of our view as a result of viewing transformations).
You are to form all matrices yourself and accumulate all matrix products in software. You will also do the perspective projection yourself, including the division to convert from 3D homogeneous coordinates to 2D Cartesian coordinates. This means that you will have to do a 3D near-plane line/plane clip in the viewing coordinate system to avoid dividing by zero or having line segments "wrap around".
Your GUI panel must contain at least the following widgets:
- A Reset button (keyboard shortcut A), which restores the original state of all transforms and perspective parameters, and sets the viewport to its initial state.
- A Quit button (keyboard shortcut Q), which terminates the program.
- A set of radio buttons that control the current interaction modes. The interaction modes are listed in detail below.
- A status line indicating (at least) the locations of the near and far planes (i.e., their distances from the camera).
The main means of interaction with the environment is by dragging the mouse with one or more buttons held down. When a mouse button is pressed, relative horizontal motion of the cursor is tracked and the transformations are continuously updated until a button up event is received. If multiple mouse buttons are held down simultaneously, all relevant parameters should be updated in parallel. This can be a bit tricky when rotating with multiple mouse buttons simultaneously, since rotations around the different axes don't commute. In this case, you may apply the rotations in a fixed order of your choosing. In general, you will want to be able to compose an arbitrary sequence of transformations.
Here are the interaction modes you must support:
- Rotate View (keyboard shortcut O):
- Dragging with the left mouse button rotates the view vector about the eye's x (horizontal) axis.
- Dragging with the middle mouse button rotates the view about the eye's y (vertical) axis.
- Dragging with the right mouse button rotates the view about the eye's z axis.
- Translate View (keyboard shortcut N):
- Dragging with the left mouse button translates the eye position along the eye's x (horizontal) axis.
- Dragging with the middle mouse button translates the eye position along the eye's y axis.
- Dragging with the right mouse button translates the eye position along the eye's z axis.
- Perspective (keyboard shortcut P):
- Dragging with the left mouse button changes the field of view (FOV) of the projection over a range from 5 to 160 degrees.
- Dragging with the middle mouse button translates projection's near plane along the view direction.
- Dragging with the right mouse button translates projection's far plane along the view direction.
- Rotate Model (keyboard shortcut R):
- Dragging with the left mouse button rotates the cube about its local x axis.
- Dragging with the middle mouse button rotates the cube about its local y axis.
- Dragging with the right mouse button rotates the cube about its local z axis.
- Translate Model (keyboard shortcut T):
- Dragging with the left mouse button translates the cube about its local x axis.
- Dragging with the middle mouse button translates the cube about its local y axis.
- Dragging with the right mouse button translates the cube about its local z axis.
- Scale Model (keyboard shortcut S):
- Dragging with the left mouse button scales the cube in its local x direction.
- Dragging with the middle mouse button scales the cube in its local y direction.
- Dragging with the right mouse button scales the cube in its local z direction.
- Viewport (keyboard shortcut V): use the mouse to draw an axis-aligned rectangle on screen, which defines the viewport in normalized device coordinates into which the scene will be drawn. More information about Viewport mode below.
The initial interaction mode should be "Rotate Model", and this mode should be restored on a reset. The amount of translation, rotation, or scaling will be determined from the relative change in the cursor's x value referenced to the value read at the time the mouse button was last moved. Make sure your program doesn’t get confused if more than one button is pressed at the same time; all the motion events should be processed simultaneously, as specified above, although individual “incremental” transformations can be composed in a fixed order (for example, when rotating around multiple axes simultaneously, you can decide on a fixed order in which the axis rotations will be applied).
You should use appropriate scaling factors to map the relative mouse motion to reasonable changes in the model and viewing transformations. For example, you might map the width of the application window to a rotation of 180 or 360 degrees. On the other hand, do not limit the total accumulation of rotations and translations; i.e., there should be no restriction on the cumulative amount of rotation or translation applied to an object, or to the number of sequential transformations.
Viewport mode allows the user to change the viewport. Assume that you have a square window into the world, and that this window is mapped to the (possibly non-square) viewport. The window-to-viewport mapping should be as described in the lecture notes and the course text: if the aspect ratio of the viewport doesn’t match the aspect ratio of the window (i.e., the viewport is not square), then the objects appearing in the viewport will be stretched. Further, when you change the viewport, you will see the same objects in the new viewport (possibly scaled and stretched) that you saw in the old viewport.
You must draw the outline of the viewport so that we can tell where it is.
In Viewport mode, the left mouse button is used to draw a new viewport. Pressing the left mouse button sets one corner. While the mouse is moving with the button held down, you should dynamically update the viewport, and when the button is released, that viewport should remain in effect. You should be able to draw a viewport by specifying the corners in any order. If the mouse position is outside the window when dragging or releasing the button, clamp the edges of the viewport to the visible part of the window.
The initial viewport should fill 90% of the full window size, with a 5% margin around the top, bottom, left and right edges. This is important so that we can verify that your viewport clipping works correctly—if you do not do this, you may lose marks in two places. The user should be able to set the viewport to any portion of the application window, including sizes larger than the original size. Note also that the viewport is to be reset to the initial size when the reset option is selected from the file menu.
You must implement a perspective projection. This will
make the cube look three dimensional, with perspective foreshortening
distinguishing front and back. You may use a projective transformation
matrix, if you wish. However, note that for this assignment there
is no need to transform the z-coordinate. Thus you could use
the mappings x→x/z and y→y/z directly,
although note that some additional scaling will be
necessary to account for the field of view. If you do wish to
construct a perspective projection matrix, you must do so
manually—you may not simply use a library function that
creates perspective matrices. (That is, you may use a type like
mat4 to hold the perspective matrix, but you must construct
the matrix with explicit values.)
If you cannot get perspective projection working, you may implement an orthographic view (no perspective) instead. You will not get a mark for Objective 7, but you may still complete most of the other objectives in the assignment. It may actually be useful to implement an orthographic view first in order to get model and view transformations working, and return to add perspective projection last.
You will need to clip your lines to the viewing volume. There are several ways to clip, any of which will suffice for this assignment. Note, however, that you must clip to the near plane before performing perspective projection, or you will get odd behaviour and crashes. You may find it easiest to clip to the remaining sides of the viewing volume after projection (since you will be clipping to a cube), but you may clip at any point in your program. Note that we will be testing clipping against all sides of the view volume.
You should already have the necessary starter code in the
cs488/A2/, which came with the ZIP file you
downloaded for A0 and A1.
You will make changes to
A2.cpp. This assignment is somewhat unusual, because
you will not use any OpenGL API calls directly; instead, you must
rely on the provided methods for drawing coloured lines. With that
in mind, you should focus on the following additions/changes to the
A2.hpp, add whatever member fields you want to track the current state of the modelling, viewing and projection transformations, as well as the viewport.
A2::appLogic(), remove the sample code that draws a few simple lines, and replace it with your code for drawing the cube, gnomons, and viewport. Use the provided methods
A2::guiLogic(), add code to draw the UI widgets listed above.
- Add interaction callbacks to track the mouse and perform transformations appropriate for the current interaction mode.
Again, the code you add should contain no OpenGL calls—all
drawing is hidden behind
drawLine(). In addition, while
you are permitted to use most of the vector and matrix manipulation
code in the GLM library, please do not use the function
glm::perspective(). If you use a matrix to implement
perspective projection, you must construct that matrix explicitly
yourself (you can still use a
mat4 to hold it, though).
If you're unsure about what functions you are or are not allowed to use,
or where you can add code, please ask on Piazza.
As always, prepare a ZIP file of the
A2/ directory, omitting
unnecessary files (executables, build files, etc.). Upload the ZIP file to
LEARN. In that directory, include a
README file and a screenshot.
If you omit either file, you will receive a deduction.
Every assignment includes a list of objectives. Your mark in the assignment will be based primarily on the achievement of these objectives, with possible deductions outside the list if necessary.
Assignment 2 objectives
- ▢ All model transformations are carried out with respect to the cube's local origin. (This means, for example, that an x translation will not necessarily be parallel to the world's x axis, if the box has been rotated about its y or z axis.)
- ▢ Viewing transformations work as expected according to the eye's location. This is indicated by the displayed location of the world gnomon.
- ▢ Model transformations are applied to the cube's gnomon, except that the gnomon is carried along unscaled.
- ▢ The transformations in all modes act smoothly while the mouse is being moved. Pressing two buttons at the same time results in transformations in multiple axes being performed together.
- ▢ Rotations, translations, and scales can be invoked in any order. Interaction modes may be entered and left as often as desired. There are no restrictions that prevent model transformations from being applied after the view has changed, or view transformations after the cube has been transformed. No matter what sequence of transformations is entered, the box never distorts so that its edges fail to meet at right angles (in 3D).
- ▢ The user interface works as described, with (at least) two buttons, the radio buttons to select interaction modes, and a status line indicating the numerical values of the near and far planes.
- ▢ The perspective transformation has been correctly implemented, and the field of view can be changed as specified in the assignment description.
- ▢ The viewport user interface and the viewport mapping works as specified in the assignment description. The initial viewport is centered and occupies 90% of the application window.
- ▢ Lines are clipped to the near and far planes. The near and far planes can be changed as specified in the assignment description.
- ▢ Lines are clipped to the sides of the viewing volume.