Changes

Jump to: navigation, search

GAM666/DPS901

143 bytes added, 18:32, 29 August 2012
no edit summary
{{GAM666/DPS901 Index | 2010320123}}
Please help make this page resourceful for all GAM666/DPS901 students to use!
= GAM666/DPS901 -- Introduction To Game Programming/3D Game Programming =*This course introduces three-dimensional, real-time, event-driven, multi-media, game programming. The course 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 a set of accompanying web pages. The framework consists of components that are is introduced sequentially in stages throughout the course. The components are independent of one another and the web pages describe the upgrades at each stage.
*Students refactor select components parts of the framework to produce a game of their own.
=== Subject Description and Course Outcomes ===
* [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]
* [httpssvn://cszenit.senecac.on.ca/~gam666dpsgam/Code%20Samples Framework – trunk Class Samples]* [svn://zenit.senecac.on.ca/dpsgam/trunk/fwk4gps Framework ]* [svn://zenit.senecac.on.ca/dpsgam/trunk/resources Resources for the Framework]
* [http://msdn.microsoft.com/en-us/library MSDN]
== 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 a distinct 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.
== Evaluation ==
# Finalize your modifications in trunk.
# Create a directory in trunk called: '''"SubmissionLogs"'''
# 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 format, specify in detail, all the tasks you have done for the group project.
# Branch (copy) the whole project including the SubmissionLogs directory and its text files into tags directory under '''"prj1.0"'''.
# If final adjustments are needed after these steps, then repeat everything from step one but branch the trunk into a new tag directory in tags as '''prj1.1, prj1.2''', etc.#:(when for markingpurposes, the your instructor will consider your last revision is considered as your submission)
== Resources ==

Navigation menu