Project 2: Viewing 3D Models
This homework assignment consists of three parts, but only the first two are mandatory to get full credit (100 points). In the first part you will need to implement camera matrices and apply them to a simple scene. In the second part you will need to load 3D models files and display them with your viewer. The third, optional part requires building a very simple flight simulator.
This assignment is due on Friday, October 10. It will be introduced by TA Sid on Monday, October 8th at 2:30pm in lab 260.
1. The Camera Matrix (40 Points)
1a. Creating the Camera Matrix (20 Points)
As described in the lecture slides, create a camera class Camera with member variables for a 'center of projection' e, a 'look at point' d, and an 'up vector' up (10 points). The class should have an internal camera matrix C, derived from e, d and up (5 points).
Add a method getGLMatrix to your camera class to access the components of the camera matrix C as an array of 16 values of type GLdouble in the order OpenGL expects them (column-major). You will need this in part 1b. (5 points) If your camera matrix already stores the matrix components in OpenGL compatible format, you do not have to do this but can directly pass the pointer instead (and will also get the 5 points).
1b. Testing (20 Points)
As a basis you can use your source code from last week. We provide source code to generate a simple scene with a house to test your camera matrix implementation. Add this code to render the house (10 points).
Set OpenGL's projection matrix as it was in the Cube example from assignment 1 with the following code in GLUT's Reshape callback function:
glMatrixMode(GL_PROJECTION); glLoadIdentity(); glFrustum(-10.0, 10.0, -10.0, 10.0, 10, 1000.0); glTranslatef(0, 0, -20);
In your GLUT Display callback, set OpenGL's model-view matrix to your camera matrix C. Do not use the gluLookAt function in this homework assignment - but you are allowed to use it in future assignments.
Render two images of the scene using these two sets of parameters for your camera matrix:
- Image 1:
- Center of projection: 0, 10, 10
- Look at point: 0, 0, 0
- Up vector 0, 1, 0
- Image 2:
- Center of projection: -15, 5, 10
- Look at point: -5, 0, 0
- Up vector 0, 1, 0.5
Compare your implementation to the correct result images shown below. If you can accurately re-create the images you will receive 5 points for each image. Note that you need to set OpenGL's lighting to 'off' with glDisable(GL_LIGHTING).
|Image 1||Image 2|
2. Displaying 3D Models from Files (60 points)
The OBJ file format is a very simple ASCII text based file format for triangle meshes. In its basic form, an OBJ file contains a list of triangle vertices indicated by the letter v, followed by an array of indices to form triangles indicated by the letter f. We provide a C++ class that reads OBJ files. Add this code to your rendering engine. You have to write the necessary code to create OpenGL geometry out of the 3D data structure (20 points). Use a method of your choice to make the tessellation of the object visible, for instance by using different colors (random or following an algorithm) for different triangles, wire frames around the triangles (5 points).
Add support for keyboard commands to select and switch between one of five .obj files (5 points). You can parse key presses with the glutKeyboardFunc command, for which you can find a good tutorial here.
These five OBJ files are available for download. Map each of them to one of the keys '1' through '5'.
You will notice that without further measures, the objects in the OBJ files may be too small or too large for your rendering window. To render the objects as large as possible while still completely fitting in the window, use the following approach:
- Calculate the minimum and maximum vertex coordinates in all three dimensions (5 points) by writing three 'for' loops which traverse all vertices, one for each dimension, storing the smallest and largest values they come across.
- Your window origin is zero, so you are going to have to translate the model towards it if its origin is not already zero. Based on the amount of translation, you need to create a translation matrix to center the object (5 points).
- Find out approximately what size objects your rendering window allows, for instance by drawing the sphere model (which is one unit wide) and scaling it up or down until it fits in the window. Based on the amount of scaling necessary, you need to create a uniform scale matrix which, scales the object so that it renders as large as possible in the window. (5 points)
- Allow the user to trigger this automatic size adjustment by pressing the 'a' key (5 points).
The 's' key should toggle a rotation of the object around its y axis, similar to the cube in the base code. To toggle means that repeated key presses on 's' will start and stop the rotation (5 points).
Make the code robust enough that the user can change the 3D model, adjust its size and start/stop the rotation at any point by pressing the respective keys, without having to observe a specific order (5 points).
3. Optional Project: Height Map (10 points)
Generate and display a 3D mesh out of a 2D height map image. Wikipedia has a great description of this topic. Allow the user to interactively fly over the height map, similar to a simple flight simulator. You can use the height map image from the Wikipedia page, which you will also find below, or create your own with a paint program or another method of your choice.
To get full credit you need to implement the following features:
- Load the height map image and create a 3D mesh out of it (4 points). You can either read the Wikipedia PNG image file with your own reader, or read this PGM image file with this piece of C code. Note that this code returns a one dimensional array, which you have to interpret as a two-dimensional array based on the width of the image.
- Use a color gradient from blue (water) to yellow (sand), green (grass), grey (rock) and white (snow) to color the terrain polygons, depending on their height (2 points).
- Create a navigation mode, in which the user can rotate the camera left or right (with keys 'a' and 'd'), move up or down (with keys 'w' and 's'), and change the velocity of the flight ('m' for slower, 'k' for faster) (3 points). Scale the terrain to a size appropriate for a flight simulator scenario (1 point).
If you use the Wikipedia height map, the resulting terrain should look similar to this, except that it needs to be colored as described above: