154
edits
Changes
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 in stagesthroughout the course. The components are independent of one another and 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 ===
* [https://scs.senecac.on.ca/course/gam666 GAM666]
* [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 assignment project is a three-stage, team project assignment to build a game using the in-class framework as its the starting point. Each team consists of 4-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 establishes proposes the proposed game design and identifies which member will work on which aspect of the game. Each member is responsible for a distinct their own aspect of the game. Team members submit their proposal on their project page and meet Each team meets with the instructor to review the proposal and obtain approval. The second stage involves the release of releases a draft of the game. The Each team members meet meets again with the instructor to review progress, discuss any changes, and obtain approval for the final plan to be implementedredefine goals. The third and final stage involves presentation of presents the completed game to the class and its evaluation by . Details are on the instructorProject Requirements page.
== Evaluation ==
* 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:
# 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, 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, 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)
== Resources ==
