Changes

= Game Presentation Schedule Due Dates =

|Team Name|Date Proposed game and Time|-|-|Team Zombieteam members selected|Tuesday April January 12 8:20AM

|Proposal completed and projects selected|Tuesday April 12 8:50AMJanuary 21

|Team GuardianProject progress reports|Tuesday April 12 9:20AMFebruary 15

|Team GG|Thursday April 14 8:20AM|Project completed -Class Presentation|Team HSD|Thursday April 14 8:50AM|-|Team Slap Your Grandma|Thursday April 14 9:20AMMarch 21

|Team Name

|Team Guardian - Hasan, JPJesse Santos|Tuesday March 22 9January 15 12:00AM|-|Team Zombie - Damian, Qing|Thursday March 24 8:00AM|-|Hic Sunt Dracones - David|Thursday March 24 9:15AM|-|Team GG - Brad|Tuesday March 29 8:00AM|-|Team GG - Randl|Tuesday March 29 8:30AM

|Slap Your Grandma - Dan, Andrei, Sashasezar gantous|Tuesday March 29 9Friday January 18 11:00AM40AM

|Hic Sunt Dracones - Daniel, Jon, KaitlynDylan Segna|Thursday March 31 8Friday January 18 12:00AM

|Team Name

|ZombieSezar Gantous|Tuesday January 18 10Monday March 11 12:00AM00 AM

|Team GGJesse Santos|Tuesday January 18 10Friday March 15 11:15AM30 AM

|Team GuardianClinton Bale|Tuesday January 18 10Friday March 15 12:30AM|-|Andrew Condinho|Tuesday January 18 10:45AM00 AM

|Zombie|Tuesday February 1 10Wednesday March 22 8:15AM|-|Andrei Kopytov|Tuesday February 1 10:30AM00AM

|Tuesday February 1 10Wednesday March 21 8:45AM25AM

|Tuesday February 1 11Wednesday March 21 8:00AM50AM

|Tuesday February 1 11:15AM|-|Slap Your Grandma|Tuesday February 1 1:30PM|-|}Project Review{| border="1"|-|Team Name|Date and Time|-|Team GG|Tuesday February 22 10:00AM|-|Zombie|Tuesday February 22 10Wednesday March 21 9:15AM

|Tuesday February 22 10Friday March 23 8:30AM00AM

|Tuesday February 22 10Friday March 23 8:45AM25AM

|Tuesday February 22 11Friday March 23 8:00AM50AM

|Tuesday February 22 11Friday March 23 9:15AM|-|Slap Your Grandma|Tuesday February 22 1:30PM|-|}<br /> = Due Dates ={| border="1"

|Proposed game and team members selectedC Minor|January 18Wednesday March 28 8:00AM

|Proposal completed and members' roles selected|February 1|-|Phase 2 draft and review|February 22|WIN -Randl(Terrain Generation)/Jeremy(Networked Gameplay)|Phase 2 completed - Presentation|Friday March 22|-|Phase 3 completed - Presentation30 8:00AM|April 12-14

Your game involves a real-time audio-visual-haptic experience in a 3-D world using advanced game programming techniques == Features that you could add to improve the performance and the appeal of your game. The user should experience force feedback through some form of controller in response to certain common actions in your game.Updated Base Code ==

Each member must contribute their own feature to the game development in a selected area of specialization. Each member should also contribute to the integration of a separate, unrelated feature developed by another team. == Phase 1 == The first phase is an informal, written proposal of the features that your team wishes to implement in its final game. Your description should identify the basic aspects of these features as well as the refinements to those features that are needed to implement your game design. Identifying the features and the required refinements will demand some research on your part. In the case of DPS905 students, the research should be deep and the description should identify the theory behind the required refinements.  Your proposal should be documented on the team project page of the course wiki under '''Proposal'''. Your proposal should identify the parts of the framework that you expect to modify extensively in your implementation. A draft of your proposal should be on the wiki before your meeting with the instructor and you should update your proposal after consultation with your instructor. In developing your game, you may start with the code that you used in the previous course or you may start with the base code for this course. The base code for this course is an update version of the base code for the previous course. In any event, each member should use the updated base code to develop the feature that they have selected and present the results of their work using the updated base code. In other words, the update base code with the new features installed will serve as the source for other teams' access.  Each team member should have their own successfully compiled version of the updated base code in their own workspace in the branch sub-directory of their team's repository. The source code for each team member's copy of the base code should include the following updates:* add your own name to the caption for the dialog box* change the window title to include the name of the team Merge all of the team members' 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 identify the features that your final game will include* to identify the features that each member of your team will incorporate* to identify the features that your team is expecting to incorporate from the work of other teams. Your team should decide its own group to individual ratio for grading purposes and post the agreed ratio on its project page. == Phase 2 == The second phase releases a version of the updated base code that includes the new features that your team members have incorporated.  This phase includes a presentation that shows* how your new features work within** the updated base code** your own game* how to incorporate the new features in external code Your team will have one hour to make its presentation and each team member will have fifteen minutes to describe the feature that they implemented themselves == Phase 3 == The third phase presents your completed game with your team's new features and two new features that members of other teams developed.  Your presentation includes* a demonstration of how the game plays* an explanation of the innovative aspects that your team members have implemented* an evaluation of the features that your team incorporated, including criticisms and suggested enhancements Each team has 30 minutes to showcase its game.<br /><br /><br /> = Features that you could add to the Updated Base Code = The base code serves as the common thread for sharing feature development amongst all members of the class. Our objective is to add as many of the features that students wish to see implemented in their own games as possible. We review this list at the start of the semester and you are welcome to expand detail or to add other features.

** view viewing frustum

* camera techniques** third-person camera techniques