|September 2129

|September 28October 11|-|Member branches with updated 15-Controller sample ready|October 11

|No later than the week of October 1011-14

|Draft game submission and project reviewProject Review meeting with instructor|November 1615-18

|December 76 and 8

Your game involves a real-time audio-visual experience in some sort of 3-D world. The user must be able to control at least some aspects of the game with a controller, and there must be some use of sound, both in the background and in response to some action in your game. The user should have control over which display devices, resolution and input devices are used at any time during the game. Your game may however offer only a subset of the available resolutions and input devices. Finally, your design code must differ significantly from the samples presented in class and you must identify the unique elements of your code in your submissionssubmission logs. Each game is a team effort and . The structure of each team is up to the team members. Each member must contribute their own work in a selected area or areas of their choosing. All members should contribute to the design part of the assignment.

The first phase is a 200-300 word informal, written proposal of what you intend to implement in your game: what you imagine your game doing. Your description should identify the objects in your game and include one or more illustrations of your design. The illustrations may be hand-drawn and scanned. Included Include in your illustrations should be a map of what you'd like envisage the 3D world of your game to will look like, with 3-dimensional coordinates of all of the major points in the world. Your map should include includes all of the "actors" (moving objects) in the world. You should attempt to make Identify the coordinates as realistic realistically as possible, being aware that you may need to scale them up or down as you implement your design in code. Accompanying  Submit the written proposal on your proposal should be wiki team-page under '''Proposal''' and '''Map of the World of the Game'''. Before continuing phase 1, please do the Sprite Animation Sample from following# Read [[Hints for Using SVN to collaborate on school projects]]# Update your team's wiki page with your team's repository path information under '''Repo Path'''# Create a directory with your seneca id under the class notesbranch sub-directory of your team's repository. This will be your home directory for development; for details see: [http://zenit.senecac.on.ca/wiki/index. Your instructor php/Hints_for_Using_SVN_to_collaborate_on_school_projects#Directory_Structure Directory Structure]# One of your team members should be able export svn://zenit.senecac.on.ca/dpsgam/trunk/Framework into the trunk of your team's repository#: For detailed steps see [[Hints for Using SVN to run this collaborate on school projects#Start_the_project_by_continuing_an_existing_work | Start the project by continuing an existing work]] Each team member should have their own successfully compiled version of the Framework sample directly in their own workspace in the branch sub-directory of their team's repository.Branch submission path: svn://zenit.senecac.on.ca/gam666dps901_113??/branches/SenecaID/Framework  : ''Start doing the above by opening branching the executable directlyFramework into svn://zenit.senecac.on.ca/gam666dps901_113??/branches/SenecaID/Framework. See here for help: [http://zenit.senecac.on.ca/wiki/index.php/Hints_for_Using_SVN_to_collaborate_on_school_projects#Preparing_Branches.2Fworkspace_for_development Preparing Branches/workspace for development]''  The source code for the upgraded Framework sample should include the following updates:* your own name in the caption for the dialog box* your team name in the window title

Merge all of the team members' Framework workspaces back to trunk so that the caption of the dialog box shows all of the names of the team members. See [http://zenit.senecac.on.ca/wiki/index.php/Hints_for_Using_SVN_to_collaborate_on_school_projects#Merging_your_work_back_to_trunk Merging your work back to trunk] for details  The purpose of this first phase of the project is twofold:* to define your game in both scope and detail and thereby to give your instructor some idea of your design, so that your instructor can give you some feedback whether what you intend is too simple, too complex, or about right* to show your instructor that you are ready to work with your own branch of your team's repository and ready to start modifying the framework to suit your team's design. Your team should decide its own group to individual ratio for grading purposes and post the agreed ratio on its project page. Your team must should arrange a time and date to meet with your instructor to discuss review your proposal and to commit identify the different responsibilities of the team members. This meeting should take place no later than during week 6 of the semester.

The second phase releases a draft of your game design without sound or input control.

This is your last opportunity to revise amend your original proposal, modify your design , and obtain your instructor's approval. You will complete feedback on your implementation in the third and final phaseprogress.

The third phase presents your completed game with sound and input control to the class. Your presentation includes a demonstration of how the game plays along with an explanation of the innovative aspects that your team members have implemented. Each team has 20 no more than 30 minutes to showcase its game.

Each team will introduce upgrades to The Framework that you download from the Framework presented in classcourse repository consists of around 12,000 source lines of code. The nature This version of the upgrades will vary from team Framework is only a starting point and provides a set of fallback/default positions for your course project. There are many opportunities to teamrefactor different parts depending upon what your game design requires and what your personal interests are. Each team member will be responsible for one specific upgrade Decisions to focus on certain parts reflect the areas with which you wish to become familiar. Parts of the framework Listed below are some areas that might be upgraded are listed belowyou should consider in deciding where to devote your energy. The If you wish to add items to this list is not exclusive, consult your instructor.

Each team will introduce its own upgrades to the Framework. The nature of these upgrades will vary from team to team. Each team member is responsible for a thorough understanding of at least one particular upgrade. Two upgrades are mandatory, while some are challenging:* required mandatory upgrades are in <strong>'''bold</strong>'''* challenging upgrades marked are followed by an *

== Modeling (Design Component) Class ==# <strong> '''game play logic</strong> (all members)# import a model script''' == Design Units (Scene Component) Object Class Hierarchy ==# <strong>'''design new objects for the scene</strong>'''# import a model script from GAM667# create billboards – clouds, smoke, vapor trails# add stock objects (requires changes to GraphicsCard Component also)# detect collisions between objects in a scene reference frames * == Viewpoints (Viewing Component) Camera Class ==

== 3D Graphics (GraphicsCard Component) Display Class ==# introduce fog# change render state == Light Class ==# introduce emissive light == Graphic Class ==

# introduce fog, emissive light# create new graphics graphic representation for new objects in the scene# implement an OpenGL 3.0 option *# Direct2D for fonts *

== Sound (SoundCard Component) Class ==

# replace DirectMusic with DirectSound only# replace DirectMusic and DirectSound with Xaudio2 *# create an Open Audio option * == User Interface (Input and UserDialog Components) Window API Branch ==

# action mapping *# replace DirectInput with Xinput XInput *

== Direct API Branch ==# implement an OpenGL 3.0 version *# create an Open Audio version *# use Direct2D for fonts *# replace Direct3D9 with Direct3D10 *# replace Direct3D9 with Direct3D11 *# COLLADA == Framework (Cross-Component) ==# context – implement a database*