Difference between revisions of "GAM670/DPS905"

From CDOT Wiki
Jump to: navigation, search
(Evaluation)
(GAM670/DPS905 -- Game Programming Techniques/3D Game Programming Techniques)
Line 14: Line 14:
 
* [https://cs.senecac.on.ca/~gam670/pages/content/index.html Course Web Site – Lecture Notes]
 
* [https://cs.senecac.on.ca/~gam670/pages/content/index.html Course Web Site – Lecture Notes]
 
* [https://cs.senecac.on.ca/~gam670/pages/timeline.html Course Web Site – Timeline]
 
* [https://cs.senecac.on.ca/~gam670/pages/timeline.html Course Web Site – Timeline]
 +
* [https://open.senecac.on.ca/cms/course/view.php?id=238 Course Grades and Discussion Forums]
 
<!--* [https://cs.senecac.on.ca/~gam670/Code%20Samples Framework – Class Samples]-->
 
<!--* [https://cs.senecac.on.ca/~gam670/Code%20Samples Framework – Class Samples]-->
 
* [http://msdn.microsoft.com/en-us/library MSDN]
 
* [http://msdn.microsoft.com/en-us/library MSDN]

Revision as of 16:58, 14 January 2011


GAM670/DPS905 | Weekly Schedule | Student List | Project Requirements | Teams and their Projects | Student Resources



Please help make this page resourceful for all GAM670/DPS905 students to use!

GAM670/DPS905 -- Game Programming Techniques/3D Game Programming Techniques

  • This course continues the study of game programming techniques begun in the introductory course. Topics covered include modeling, texturing and lighting techniques, force feedback, and shader programming
  • The course is supported by the open instructional software framework introduced in GAM666/DPS901. Students refactor select components of the framework to augment the base code for all members of the class.

Subject Description and Course Outcomes

External Links

The Project

The course project is a three-stage, team assignment to build a game using the framework from the introductory course. Each team consists of up to 3 members. Membership is subject to instructor approval and is open to modification until the end of the week of the drop date for the course. The first stage of the assignment proposes the features that your team will add to the framework and identifies which member will work on which feature. Each member is responsible for a distinct feature. Each team meets with the instructor to review the proposal and obtain approval. The second stage is a release of the framework that includes the feature. The third and final stage presents your own team's completed game to the class, which includes your features along with several features incorporated by other teams. Details are on the Project Requirements page.

Evaluation

  • Option A
    • Feature - Individual Assignment 30%
    • Game - Group Assignment 20%
    • Test 20%
    • Exam 30%
  • Option B (no exam - feature work is significantly more in depth)
    • Feature in Depth - Individual Assignment 60%
    • Game - Group Assignment 20%
    • Test 20%

Each student must commit to Option A or B by March 16

Final Submission Requirements

Resources

Examples and In-Class Notes

Archives