From CDOT Wiki
(Redirected from DPS901)
Jump to: navigation, search

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!

Introduction To Game Programming/3D Game Programming

  • This course introduces three-dimensional, real-time, event-driven, multi-media, game programming. It 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 accompanying web pages. The framework is introduced in stages throughout the course. The web pages describe the upgrades at each stage.
  • Students refactor select parts of the framework to produce a game of their own.

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 as the starting point. Each team consists of up to 5 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 game design and identifies which member will work on which aspect of the game. Each member is responsible for their own aspect. Each team meets with the instructor to review the proposal and obtain approval. The second stage releases a draft of the game. Each team meets again with the instructor to review progress and redefine goals. The third and final stage presents the completed game to the class. Details are on the Project Requirements page.


  • Assignment 50%
    • Individual Work - 50% to 75% inclusive
    • Group Work - 25% to 50% inclusive
    • Total (Individual + Group) - 100%
  • Test 20%
  • Exam 30%

Final Submission Requirements

When ready to submit your project:

  1. Finalize your modifications in trunk.
  2. Create a directory in trunk called: "SubmissionLogs"
  3. For each member of the team create a text file named as "YourSenecaEmailId.txt" in the "SubmissionLogs" directory. In this text file, in a point form, specify in detail, all the tasks you have done for the group project.
  4. Branch (copy) the whole project including the SubmissionLogs directory and its text files into tags directory under "prj1.0".
  5. If final adjustments are needed after these steps, repeat everything from step one but branch the trunk into a new directory in tags as prj1.1, prj1.2, etc.
    (for marking purposes, your instructor will consider your last revision as your submission)


Examples and In-Class Notes