This third project of the semester is your chance to build and describe your own small virtual world. Unlike the prior two projects, thespecifics for this assignment are intentionally broad. At the end of this project, you must produce three things. First, a working OpenGL program that satisfies functional requirements set out below. A well documented, robust, system that meets these minimum requirements is worth 90% of the total points for the system. The remaining 10% is reserved for what can be best called "cool factor". Essentially, how interesting/fun/beautiful is your virtual world. In addition to the documented code, you are also being asked to build a webpage describing and illustrating the fruits of your efforts. To keep look and style consistent, as well as to provide some guidance, an html template with accumpanying style sheet will be distributed. The third thing you will be asked to produce is a sequence of images showing navigation through your scene. John Stevens, the GTA, is looking into the easiest way that these can be turned into a video that will work well as a part of your webpage. More will be said about this in the coming month. Note this image sequence is due on Wednesday, two days ahead of the code and webpage itself.

Your code must, at a minimum, do the following:

Contain at least three identifiable stationary objects.

You should strive to have a visually interesting 3D world, and at a minimum it should contain three distinct objects.

Contain at least two distinct objects which are in motion.

Recall that a recurring theme this semester has been how to put an object into motion. You scene must contain, at a minimum, objects which are in motion.

Permit Manual Navigation

You must implement mouse based navigation. Specifically, a user must be able to move forward, backward, up and down. In addition the user must be able to pan left and right. A modest ability to look up or down is also required.

Contain at least two light sources

At least two of the OpenGL light sources must be enabled and their influence over the appearance of the scene notable.

If history is any guide, there will be addendums to this assignment that clarify what is expected. These will be posted and dated here as well as announced in lecture as they arise.

Saving Images/Frames (11/30/2007)

Include the provided header file (saveFrame.h) in your main program. Whenever you want to save a frame, call the saveFrame function. This function takes two integer parameters: the width and height of the window. If you have a timer function that is called regularly to update the animations, that is a good place to call saveFrame. After the saveFrame function ahs been called 180 times, the saved frames will be written to disk. Further calls to saveFrame after this happens will have no effect. 180 frames is 6 seconds of video at 30 frames per second, which is sufficient for this assignment.

All of your code must be in one directory and include a single makefile that will successfully compile it on one of the CS Department Linux Machines. To submit your project code, you will upload a single tar file with the contents of this directly to RamCT. The project will appear on RamCT in the week it is due. Do not forget to include any and all auxillary files required by your program.

Your image sequence and finished web page will also be uploaded to RamCT through separate RamCT assignments.