1
edit
Changes
→Appointment Schedules
{{GAM670/DPS905 Index | 20121}}
= Game Presentation Schedule Due Dates =
{| border="1"
|-
|Team NameProposed game and team members selected|Date and TimeJanuary 12
|-
|Proposal completed and projects selected
|January 21
|-
|Project progress reports|Wednesday April 11 8:20AMFebruary 15
|-
||Wednesday April 11 8:50AM|-||Wednesday April 11 9:20AM|Project completed -Class Presentation||Friday April 13 8:20AM|-||Friday April 13 8:50AM|-||Friday April 13 9:20AMMarch 21
|-
|Game completed - Class Presentation
|April 11-13
|}
<br />
<br />
= Research Project =
Your research project involves the investigation and implementation of a specific feature in the update base code. Identifying the features and the required refinements will demand some initial research on your part. The project is in two phases.
== Phase 1 ==
The first phase is an informal, written proposal of the features that your team has decided 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 in your own game by the end of the semester.
Your proposal should be presented 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. Your proposal should be on the wiki before your first meeting with your instructor. You should update your proposal after this meeting. Your instructor will use your updated proposal as the reference for marking this assignment.
The base code for this course is an updated version of the base code for the previous course. You should use the updated base code to develop the feature that you have selected and present the results of your work using the updated base code. The updated 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 research projects of other teams.
== Phase 2 ==
The second phase releases the updated base code with your new features to the class.
This phase concludes with a presentation that shows
* how your new features work within the updated base code
* how to incorporate the new features in external code
You will have one hour to make your presentation and to describe the feature that you have implemented.
== Appointment Schedules ==
Research Project
{| border="1"
|-
|Team Name
|Date and Time
|-
|Clinton Bale
|Tuesday January 15 11:40AM
|-
|Team Guardian - Hasan, JPJesse Santos|Tuesday March 22 9January 15 12:00AM
|-
|Team Zombie - Damian, Qingsezar gantous|Thursday March 24 8Friday January 18 11:00AM40AM
|-
|Hic Sunt Dracones - DavidDylan Segna|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, Sasha|Tuesday March 29 9:00AM|-|Hic Sunt Dracones - Daniel, Jon, Kaitlyn|Thursday March 31 8Friday January 18 12:00AM
|-
|}
{| border="1"
|-
|Team Name
|Date and Time
|-
|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
|-
|
|
|-
|}
{| border="1"
|-
|Date and Time
|-
|-
|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 selected|January 18
|-
|Proposal completed and members' roles selectedC Minor|February 1Wednesday March 28 8:00AM
|-
|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
|}
<br />
* visibility determination
** view viewing frustum
** bounding volume construction
*** principal component analysis
* audio techniques
* comprehensive collada imports
* camera techniques** third-person camera techniques
* quaternions
* networked gameplay
** provide external access to all objects in the scene coordinator
* enable Streaming SIMD Extension 2 in Configuration Properties with optimized math calculations
<br />
= Game =
== Requirements ==
Your game involves a real-time audio-visual-haptic experience in a 3-D world using advanced game programming techniques 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.
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.
In developing your game, you may start with the code that you used in the previous course or you may start with the updated base code for this course.
You present 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 />
== Game Presentation Schedule ==
{| border="1"
|-
|Team Name
|Date and Time
|-
|-
|
|Wednesday April 11 8:20AM
|-
|
|Wednesday April 11 8:50AM
|-
|
|Wednesday April 11 9:20AM
|-
|
|Friday April 13 8:20AM
|-
|
|Friday April 13 8:50AM
|-
|C Minor
|Friday April 13 9:20AM
|-
|}
<br />