154
edits
Changes
→Project Requirements
= Project Requirements =
Your game involves a real-time audio-visual -haptic experience in some sort of a 3-D worldusing advanced techniques to improve performance and appeal. The user must be able to control at least experiences force feedback through some aspects form 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 certain 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 in a selected area or areas of their choosing. All members Each member should also contribute to the design part integration of the assignmenta 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 intends 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 basic aspects of your design. The illustrations may be hand-drawn and scanned. Included in your illustrations should be a map of what you envisage the 3D world of your game will look like, with 3-dimensional coordinates of all of features as well as the major points in the worldrefinements needed to produce a comprehensive implementation. Your map proposal should include all be documented on the team project page of the "actors" (moving objects) in the worldcourse wiki under '''Proposal'''. You Your proposal should identify the coordinates as realistically as possible, being aware parts of the framework that you may need expect to scale them up or down as you implement modify in your design in codeimplementation.
Branch submission path: svn://zenit.senecac.on.ca/dps901_103rep??/branches/SenecaID/15C
* 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 detail
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: whether what you intend is too simple, too complex or about right* to ensure enable your instructor that you are ready to work with your own branch identify some of your team's repository and ready to start modifying the framework to suit your team's design.Your submission should enable your instructor to give details that you feedback and will need to discuss your proposal handle in some detail.implementing the selected features
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 arrange a time and date to meet with your instructor to discuss the proposal and to commit the different responsibilities of the team members. This meeting should take place no later than week 6 of the semester, preferably earlier.
== Phase 2 ==