CMSC 23800/53800
Course Project

Overview

The course project is to design an implement a racing game. You will work in groups of around five students and will be expected to make frequent, but informal, presentations about your project in class. This page will include links to various documentation, code, and game assets that you may find helpful for your projects.

Milestones

It is important that you work steadily on your project throughout the term. The help you gage your progress, here is a list of project milestones with target dates.

Milestone 0: group formation (April 6)

By Tuesday of the second week, you should have formed your groups and picked a group name. You should also start thinking about breaking up the project into parts and assigning responsibilities.

Milestone 1: design document (April 13)

An important part of any large software project is a document that lays out the architecture of the application. For the first project milestone, each group should produce a design document that covers (at least) the following issues:

You should view this document as a living document that will be refined as the term progresses

Milestone 2: basic physics engine (April 20)

The physics engine is the heart of game, since it manages the state of the player and AI vehicles. Getting a basic engine up and running early will provide a useful tool for developing the other parts of the project.

Milestone 3: basic AI (May 4)

At this point, you should have enough physics and AI infrastructure implemented that your AI agents can navigate around the track without crashing into the walls, or each other.

Milestone 4: playability (May 11)

Milestone 5: networking (May 18)

Final project demos (June 1)

The final project demos will be on Tuesday June 1st in class.

Specifications

Assets

Here are some assets that you can use in your game.
oval.trk
A simple, hand-generated, oval track.
barbell.trk
A medium sized track generated using a script.
wide-barbell.trk
A wider version of barbell.trk (20 units vs. 12) with four lanes (instead of 3). It was generated using a script.

Last revised: May 26, 2010.