1Computer Graphics Practical Assessment – 3D pacman Due: Wednesday January 12 th 12-noon John Shearer Culture Lab – space 2

2Computer Graphics 3D Pacman! You are required to write a game similar to “pacman” - but with a 3D view (the game is still 2D) Normal rules of pacman apply (see –Eating dots –Control pacman with keys –Ghosts move around –Normally ghosts eat pacman –Pacman can eat a powerup to eat ghosts –Level is complete when all the dots are eaten The view of the maze must be in 3D –The walls should be walls around the corridors The maze should tip in response to user controls – influencing pacman's direction

3Computer Graphics Submission – to NESS a zip file named as your student number –e.g. a zip containing all files organised as you choose (and all libraries if you use them) an executable or batch/shell file in the root directory named as your student number that is/runs your program –e.g. a exe, a bat, a sh, a all (fully documented) source code for your program, including build files (.sln files, make files, etc.) so your examiner can build the executable if required a text, html, or word file named as your student number that provides your submission document (see later slide) –e.g. a doc, a html

4Computer Graphics Testing You must test your zip file on a campus build of the appropriate OS Preferably also test on a friend’s login to make sure it’ll run for your examiner also REALLY!

5Computer Graphics Code documentation Your code should be documented appropriately –not with just what each function does, but also why it does it in that way, design decisions, other ways it could work. –BUT, I'm not marking code comments specifically, but I need to be able to understand how/why you've made decisions in awarding marks for functionality Overall, your code should be understandable with reasons why it is structured/written the way it is

6Computer Graphics Separate documentation You should provide a text, html, or word file providing overall documentation for your coursework This should be 1 side of A4 This document should overview your coursework giving your overall approach, any specific forms of innovation you have introduced, why you decided to make your coursework the way it is, etc. Brief instructions of how to use the program

7Computer Graphics Marking The coursework is (PRESENTLY) worth 20% of your module mark –DISCUSS 80% of that is the program performance, 20% for documentation –of the 20% 5% for code comments 15% for separate documentation –of the 80% 40% for achieving the “base” requirements (see later slides) –5% for it running plus 5% for each requirement 40% for achieving the “extra” requirements (see later slides) –7% each extra requirement

8Computer Graphics Mark Scheme Basic (5% for it running plus 5% for each requirement) –Basic 3D Geometry (cuboids, squares, spheres) – Maze (walls), Ghosts, Pacman Maze same/similar to original pacman Pacman CANNOT be just a sphere –Basic Lighting –Movement Controls, dot eating, level complete –Tipping Maze –Ghosts move, ghost eat pacman (animation no required) –Powerup for Ghost-eating and ghosts eatable (and visual effects to reflect state), ghosts run away (at least a little) from pacman when eatable –Counter / Score / Lives / Start game count-down Note: implementing the game in just 2D will lose significant marks. Extras 7% each (max 40%) –Advanced / Dynamic Lighting –Advanced Geometry –Advanced / Dynamic Camera Zooms and follows pacman? –Character animation (pacman, ghosts, eating, powerups) –Ghosts return to home when eaten, to become alive again –Texturing –Environment Geometry e.g. Stadium, Lunar Surface –Pacman/ghost speed effected by angle of maze (more advanced controls needed) –Maze loading from a text file (format of your choice, but explained so I can edit/test the file) –First person view (either as alternative on key press, or as an additional viewport) –Other 'advanced' effects – after consultation