Difference between revisions of "GAM666/DPS901"

From CDOT Wiki
Jump to: navigation, search
Line 11: Line 11:
* [https://scs.senecac.on.ca/course/dps901 DPS901]
* [https://scs.senecac.on.ca/course/dps901 DPS901]
=== External Links ===
=== External Links ===
* [https://cs.senecac.on.ca/~gam666/content/index.html Course Web Site – Lecture Notes]
* [https://cs.senecac.on.ca/~gam666/pages/content/index.html Course Web Site – Lecture Notes]
* [https://cs.senecac.on.ca/~gam666/pages/timeline.html Course Web Site – Timeline]
* [https://cs.senecac.on.ca/~gam666/pages/timeline.html Course Web Site – Timeline]
* [https://cs.senecac.on.ca/~gam666/Code%20Samples Framework – Class Samples]
* [https://cs.senecac.on.ca/~gam666/Code%20Samples Framework – Class Samples]

Revision as of 22:31, 13 September 2010

GAM666/DPS901 | Weekly Schedule | Student List | Project Requirements | Teams and their Projects | Student Resources

Please help make this page resourceful for all GAM666/DPS901 students to use!

GAM666/DPS901 -- Introduction To Game Programming/3D

  • This course introduces three-dimensional, real-time, event-driven, multi-media, game programming. The course covers windows programming at the operating system level, low-level programming of hardware through the DirectX APIs and design implementation at the model-level.
  • The course is supported by an open instructional software framework with a set of accompanying web pages. The framework consists of components that are introduced in stages. The components are independent of one another and the web pages describe the upgrades at each stage.

Subject Description and Course Outcomes

External Links

The Project

The course assignment is a three-stage, team project to build a game using the in-class framework as its starting point. Each team consists of 4-5 members. Membership is subject to instructor approval and is open to modification until the week of the drop date for the course. The first stage of the assignment establishes the proposed design and identifies which member will work on which aspect of the game. Each member is responsible for a distinct aspect of the game. Team members submit their proposal on their project page and meet with the instructor to review the proposal and obtain approval. The second stage involves the release of a draft of the game. The team members meet with the instructor to review progress, discuss any changes, and obtain approval for the final plan to be implemented. The third and final stage involves presentation of the completed game to the class and its evaluation by the instructor.


  • Assignment 50%
    • Individual Work 50%
    • Group Work 50%
  • Test(s) 20%
  • Exam 30%


Examples and In-class Notes