1
edit
Changes
→Appointment Schedules
|-
|Proposed game and team members selected
|January 1812
|-
|Proposal completed and members' roles projects selected|January 2521
|-
|Project progress reportreports
|February 15
|-
|Project completed - Class Presentation
|March 21
|-
|Game completed - Class Presentation
|April 11-13
|}
<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"|-|Name|Date and Time|-|Clinton Bale|Tuesday January 15 11:40AM|-|Jesse Santos|Tuesday January 15 12:00AM|-|sezar gantous|Friday January 18 11:40AM|-|Dylan Segna|Friday January 18 12:00AM|-|} Feature Progress Meeting {| border="1"|-|Name|Date and Time|-|Sezar Gantous|Monday March 11 12:00 AM|-|Jesse Santos|Friday March 15 11:30 AM|-|Clinton Bale|Friday March 15 12:00 AM|-|||-|} == Project Presentation Schedule ==
{| border="1"
|-
|Friday March 23 9:15AM
|-
|C Minor
|Wednesday March 28 8:00AM
|-
|WIN - Randl(Terrain Generation)/Jeremy(Networked Gameplay)
|Friday March 30 8:00AM
|-
|}
<br />
* 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.
* a demonstration of how the game plays
* an explanation of the innovative aspects that your team members have implemented
<br />
== Game Presentation Schedule ==
{| border="1"
|-
|Friday April 13 8:50AM
|-
|C Minor
|Friday April 13 9:20AM
|-
|}
<br />
