CS248 Project 1: Breakout

The goal of this assignment is to get your feet wet by writing a simple interactive OpenGL program: an implementation of the arcade game Breakout.

Key Dates

• Tuesday, October 2: Project assigned.
• Tuesday, October 9, 11:59pm: Project source code due
• Wednesday, October 10: Project demos in Gates B08

Requirements

You must implement the game Breakout using OpenGL. This is a solo assignment, and all code should be written by you alone. You may discuss gameplay ideas and algorithms with your friends, but don't share any code. Similarly you may take gameplay ideas and algorithms from the web, but don't cut and paste any code.

Breakout consists of three types of objects:

• A paddle, at the bottom of the screen, which can move left and right, and is controlled by the mouse.
• An array of bricks of various colors at the top of the screen.
• A ball, which bounces around, colliding with the other objects. If the ball collides with the bottom of the screen, the player loses. If the ball collides with any other edges of the screen it bounces in a realistic manner. If the ball collides with a brick, the brick is destroyed and the ball bounces in a realistic manner. If the ball collides with the paddle, the ball bounces off at an angle proportional to where it hit the paddle. Eg if it hits the paddle on the extreme left side, it will bounce leftwards, and if it hits the paddle in the middle, it will bounce straight up. Note that this is not physically accurate. The ball's velocity should slowly increase as the game progresses, to increase the difficulty.

For a better sense of Breakout, try one of these online versions. Note that they don't necessarily meet the assignment requirements.
http://www.geocities.com/SiliconValley/Bay/6879/Breakout.html
http://www.geocities.com/ResearchTriangle/System/3517/breakout/breakout.html
http://www.aeonity.com/ab/games/arcade-classics/classic-breakout.php

You are encouraged to vary the rules, as long as it doesn't simplify the graphics or physics of the game.

You may write in any programming language that has an OpenGL library. We strongly recommend C or C++. You may write the project on any platform, using any development environment, as long as you can demo the game to us in Gates B08. We recommend either using the linux machines in B08, or bringing a laptop.

Extra Credit

We encourage you to implemented extra graphical or physical features. While grading is entirely up to the grader, the following things would be typically be considered as features worth extra credit:

• Complex physics on the ball, such as spin resulting from the ball bouncing off a moving paddle. Any extra physics should come with some kind of graphical effect to indicate their existence.
• A range of special bricks, which change the graphics and/or game rules when destroyed (e.g. a brick that when destroyed, spawns an extra ball)
• Particle Systems
• Antialiased text displaying a score, and a number of lives lefts.
• Anything else that requires some amount of graphical work and looks cool.

Extra credit points are not added to your project score, but instead tallied separately. At the end of the course, after fitting grades to a bell curve, extra credit points are converted into regular points and added to your grade.

You are also welcome to add sounds effects and music, but as this is a graphics course, they will not be worth any credit.

Grading

This project is worth 15% of your final grade. A game that meets all the requirements, runs smoothly, and has no glitches will get full marks. You may lose points for things like the game running very slowly, the game crashing, graphical flicker, or unintended unexpected behaviour of the game objects. A totally non-functional game will get no points.

If you submit your code late, you will be penalized with a cap on your maximum possible score, at a rate of 10% per day until you submit your final version. In this case, you should demo your program during TA office hours. Remember that the course outline affords you one day of grace for the course, which you may use for this assignment.

Submission

Submit a zip file of your submission here. If it's very large, or if you have problems with the submission script, contact the TAs. You may submit as many times as you like, so submit early and often.

Resources

Google is your friend. We suggest you use it heavily while getting OpenGL working. One useful set of tutorials is at http://nehe.gamedev.net/, though be warned that the code there can be quite messy. If you're a windows person, then a good site explaining how to get started in visual studio 2003 is here.

Your other main resource is the course TAs, Justin and Andrew, who can be reached at cs248-aut0708-staff@lists.stanford.edu, by attending their office hours, or after a lecture for quick questions.