4
edits
Changes
no edit summary
{{GAM670/DPS905 Index | 20111}}
{| border="1"
|-
|-
|-
|TeamZombie|Tuesday January 18 April 12 8:00AM20AM
|-
|Slap Your Grandma|Tuesday December 7 April 12 8:15AM50AM
|-
|Team ZombieGuardian|Tuesday December 7 8April 12 9:30AM20AM
|-
|Team GG
|Tuesday December 7 Thursday April 14 8:20AM|-|Team HSD|Thursday April 14 8:45AM50AM|-|Team Slap Your Grandma|Thursday April 14 9:20AM|-|}<br /> = Presentation Schedule ={| border="1"
|-
|Cerebral ThoughtTeam Name|Tuesday December 7 9:00AMDate and Time
|-
|-
|Copy CatTeam Guardian - Hasan, JP|Thursday December Tuesday March 22 9 8:00AM
|-
|Team Zombie - Damian, Qing|Thursday December March 24 8:00AM|-|Hic Sunt Dracones - David|Thursday March 24 9 8:15AM
|-
|Double TapTeam GG - Brad|Thursday December 9 Tuesday March 29 8:30AM00AM
|-
| Hic Sunt DraconesTeam GG - Randl|Thursday December 9 Tuesday March 29 8:45AM30AM
|-
|SheetBrix RoboticsSlap Your Grandma - Dan, Andrei, Sasha|Thursday December 9 Tuesday March 29 9:00AM
|-
|The 10th FloorHic Sunt Dracones - Daniel, Jon, Kaitlyn|Thursday December 9 9March 31 8:15AM00AM
|-
|}
<br />--> = Appointment Schedules =Initial Proposal
{| border="1"
|-
|Date and Time
|-
|Zombie
|Tuesday January 18 10:00AM
|-
|Team GG
|Tuesday January 18 10:15AM
|-
|Team Guardian
|Tuesday January 18 10:30AM
|-
|Andrew Condinho
|Tuesday January 18 10:45AM
|-
|
|Tuesday January 18 11:15AM
|-
|Slap Your Grandma
|Tuesday January 18 1:30PM
|-
|}
Proposal Acceptance
{| border="1"
|-
|Team Name
|Date and Time
|-
|Team GG
|Tuesday February 1 10:00AM
|-
|Zombie
|Tuesday February 1 10:15AM
|-
|Andrei Kopytov
|Tuesday February 1 10:30AM
|-
|
|Tuesday February 1 10:45AM
|-
|
|Tuesday February 1 11:00AM
|-
|
|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 10:15AM
|-
|
|Tuesday February 22 10:30AM
|-
|
|Tuesday February 22 10:45AM
|-
|
|Tuesday February 22 11:00AM
|-
|
|Tuesday February 22 11:15AM
|-
|Slap Your Grandma
|Tuesday February 22 1:30PM
|-
|}
|-
|Proposal completed and members' roles selected
|January 31February 1
|-
|Phase 1 completed2 draft and review
|February 22
|-
|March 22
|-
|Approval meeting with instructor|March 29|Phase 3 completed -|Final game presentationPresentation
|April 12-14
|}
= Project Requirements =
Your game involves a real-time audio-visual -haptic experience in some sort of a 3-D world. The user must be able using advanced game programming techniques to control at least some aspects of improve the game with a controller, performance and there must be some use the appeal 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 experience force feedback through some form of the available resolutions and input devices. Finally, your design code must differ significantly from the samples presented controller in class and you must identify the unique elements of your code response to certain common actions in your submissions. Each game is a team effort. The structure of each team is up to the team members. Each member must contribute their own work feature to the game development in a selected area or areas of their choosingspecialization. All members Each member should also contribute to the design part integration of the assignmenta separate, unrelated feature developed by another team.
== Phase 1 ==
The first phase is a 200-300 word an informal, written proposal of what you intend the features that your team wishes to implement in your its final game: what you imagine your game doing. Your description should identify the objects in basic aspects of these features as well as the refinements to those features that are needed to implement your game and include one or more illustrations of your design. The illustrations may be hand-drawn Identifying the features and scannedthe required refinements will demand some research on your part. Included in your illustrations should be a map of what you envisage In the 3D world case of your game will look likeDPS905 students, with 3-dimensional coordinates of all of the major points in the world. Your map research should include all of be deep and the "actors" (moving objects) in the world. You description should identify the coordinates as realistically as possible, being aware that you may need to scale them up or down as you implement your design in code. Submit the written proposal on your wiki team-page under '''Proposal''' and '''Map of the World of theory behind the Game'''required refinements.
The source code for each team member's copy of the upgraded 15-Controller sample 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' 15C 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 detaildetails
The purpose of this first phase of the project is twofold:
* to define identify the features that your final game in both scope and detail and thereby to give your instructor some idea of your design: whether what you intend is too simple, too complex or about rightwill include* to ensure your instructor identify the features that you are ready to work with your own branch each member of your team's repository and ready will incorporate* to start modifying identify the framework to suit features that your team's design.Your submission should enable your instructor is expecting to give you feedback and to discuss your proposal in some detailincorporate 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 3 ==
The third phase presents your completed game with sound your team's new features and input control to the classtwo new features that members of other teams developed. Your presentation includes * a demonstration of how the game plays along with * 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 no more than 20 30 minutes to showcase its game.
<br />
<br />
<br />
= Some Suggested Upgrades Features that you could add to the Framework 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.