For each project you develop for this course, you must submit your program electronically (directions are available here). Additionally, your code should be written in C++ and follow the spirit of the conventions detailed here. 

Finally, each program should include a README file that includes:

• your name and acpub ID
• time spent on the project
• list of data files needed to run your program and where to find them
• directions for compiling and running the program
• list of systems on which you tested your program

Warm-up

Warm-ups are simply to help get you acclimated to the course and to give me a little bit more information about you. It is important that you take as much time as you are need at the beginning to get used to the tools introduced.

• Introductions, due Tuesday, September 3

Homeworks

Homeworks are solo projects, on which you must work by yourself, designed to prepare everyone for the larger group projects.

• Animation, due Tuesday, September 10
• Hierarchy, due Tuesday, September 17
• Room, due Thursday, September 26 (for extra credit), but finally on Tuesday, October 1 
• Mouse, due Thursday, October 10

Group Projects

Group projects will be done by three to five students. You may choose your own partners for each project. Each project builds on the previous ones. For each group project, only one final program should be handed in.

• Terrain (teams)
  • Part 1: terrain from image and camera control, due Thursday, October 24
  • Part 2: smooth, colored terrain, due Tuesday, October 29

• Trains (teams)
  • Part 0: changes to group members, due Wednesday, October 30
  • Part 1: running train on track from image, due Thursday, November 7
  • Part 2: fully editable tracks and camera placement, due Thursday, November 14
     
• Scenery (teams)
  • Part 1: display inactive things in world from image, due Tuesday, November 26
  • Part 2: fully realized world with very interesting things, due Thursday, December 6
     

Apollo 13 (1995)	Titanic (1997)