GROUP FINAL PROJECT
BENCHMARK 2
In this benchmark you will develop simple game prototype that will provide the look and feel of your ultimate game.
Benchmark 2 Requirements:
- World Rendering - Implement a the design, layout and rendering of a single level. This means background tiles, both tiled and sparse. Remember, your team will need one level for each team member, the assumption is that each teammate should be a level designer for one level. In this benchmark, you only need to provide the first level.
- An animated, interactive main character - Define your main character and the main character's movements and interactions such that it is fully animated and may move about the game world under the player's control as gameplay requires.
- The beginnings of a Collision Detection System - Start building your collision detection necessary in your game. You don't need to have it fully functional just yet, but it will be required for the next benchmarker moves around the game level as it will in the final demo. Sprite-to-sprite collision detection as well as sprite-to-tile collision detection should both be implemented if both are needed. Note that in the next benchmark.
- A Render Thread - All rendering, for both the GUI and the game levels should be done using a separate render thread as we discussed in lecture. This is an important part of improving your game's performance.
- NO MEMORY LEAKS - Employ the same memory management scheme we used in the individual project, and make sure your project has no memory leaks.
The point of this prototype is that you can work on the gameplay as you implement your coding. Poor gameplay will overshadow any brilliantly efficient algorithms, so I'd like for you to game test continually. From the start, consider what works in your game, what doesn't, what needs to be improved, tweaked, revamped, etc.
SUBMITTING YOUR HW: This should be done in two stages:
- Hand-in your full Visual Studio project with all source code and other components necessary to build and run your game by zipping it up into a single ZIP file and posting it to the class' Digital Dropbox on Blackboard. Call your submission "X's Benchmark 1", where "X" is your team's name. Only one student from each team needs to submit the project files. You'll use a similar style for future Benchmarks.
A LOOK AHEAD
For the next benchmark groups will further develop their prototypes adding additional rudimentary levels and some AI. In addition, sound & music will be added.
Web page created and maintained
by Richard McKenna