Group Size: 1-3 people
Deliverables: Working “tech demo” (shown live, but submitted as video), short presentation and a 3-4 page report
Judged on: Technical quality, originality/creativity, amount of effort, delivery of demo and presentation, clarity and completeness of report

This project has to be a Tech Demo of a game engine feature that you have designed and implemented. A tech demo does not have to e a fully working game, but it should demonstrate your technology in a game-like context.

One way to think about this is that in your first project you used a number of features that an existing game engine and its tools provided. This time around you can pick a couple of features, go under the hood, and implement them yourself. Working with the game engine should have given you a pretty good idea of what kinds of technologies are being offered.

This technology you work on can be something you build absolutely from scratch (e.g. your own resource management system or visual effects) or something that is put together from several existing components, combined in an interesting way (e.g. physics and animation).

You can propose pretty much anything, as long as the following is true about the project:

• It is challenging for you
• It is fun for you
• It is educational for you

There are a few more implementational requirements:

• Use C/C++ (this is a fundamental skill you need to develop)
• Use the Ogre 3D framework (it is flexible, well designed and at the right level of abstraction)
• You should make sure everyone on the team gets to program (divide project into units)

It is possible to negotiate the C/C++ and Ogre requirements, but you need very good arguments. For example, it is not enough to suggest using a different engine because then you can make a cooler game. This course is about the design of the engine itself, not game creation.

This is a short but informative, report about the final project that should include:

1. Title / Authors
2. Screen shot (at least one at the very top of the paper - see formatting instructions below)
3. Short abstract (at least one paragraph summarizing what your project is about)
4. Motivation (what is your technology addressing? who would want to use it?)
5. Related work (examples of similar things other have done. what existing work do you build on?)
6. Approach (explain your technical design and implementation)
7. Results (mention what worked and didn't work)
8. Future work (what would you do next if you had more time?)
9. References (a list of cited references in the correct format - see below, even if you only have one or two)

Think of this as a poster submission to a conference.

The paper should be written in a 9 or 10 point justified serif (Times or Times Roman) font in two columns per page, with a single line space. It should be 2-4 pages long.

Other than that, follow the guidelines for a technical paper submission to the SIGGRAPH conference as much as you can (don't worry too much about the details, just get a feeling for the overall structure and look):

• SIGGRAPH Instructions for Authors
• SIGGRAPH Submission Template