From CDOT Wiki
Jump to: navigation, search


343 bytes removed, 08:48, 11 January 2012
Project Work
{{GAM670/DPS905 Index | 2011120121}}
Please help make this page resourceful for all GAM670/DPS905 students to use!
= GAM670/DPS905 -- Game Programming Techniques/3D Game Programming Techniques =*This course introduces three-dimensional, real-time, event-driven, multi-media, continues the study of game programmingtechniques begun in the introductory course. The course covers windows programming at the operating system levelTopics covered include modeling, texturing and lighting techniques, force feedback, low-level and shader 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 sequentially throughout the course. The components are independent of one another and the web pages describe the upgrades at each stage. *Students refactor select components aspects of the framework to produce a game augment the base code for all members of their ownthe class.
=== Subject Description and Course Outcomes ===
* [ Course Web Site – Lecture Notes]
* [ Course Web Site – Timeline]
* [ Course Grades and Discussion Forums - Moodle]<!--* [ Framework – Class Samples]-->
* [ MSDN]
== The Project Work ==The Project work for this course project is a three-stage, team assignment to build a game using the framework as the starting pointin in two parts. Each team consists of up student contributes some upgrade to 5 members. Membership is subject to instructor approval the framework and is open presents the upgrade to modification until the end rest of the week of the drop date for the courseclass. The first stage of the assignment proposes the Students working in teams incorporate their own upgrades into their own game design and identifies which member will work on which aspect of the incorporate another team's upgrade into their own game. Each member is responsible for a distinct aspect. Each team meets with student presents the instructor results of their research project to review the proposal and obtain approval. The second stage releases a draft of the game. The third class and each team presents their final stage presents the completed game to the class. Details are on the Project Requirements page.
== Evaluation ==
* Feature - Individual Assignment 5030%** Individual Work Game - 50% to 75% inclusive** Group Work - 25% to 50% inclusive** Total (Individual + Group) - 100Assignment 20%
* 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"'''
# 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 directory in tags as '''prj1.1, prj1.2''', etc.
#:(when marking, the last revision is considered as your submission)-->
== Resources ==
* [ Download Page of TortoiseSVN]
* [ TortoiseSVN Documentation]
* [ SVN book at] or download[ the PDF from here][ casino].
* [ IRC Basics]
== Archives ==
[[GAM670/DPS905_Weekly_Schedule_20111 | GAM670/DPS905 20111]]

Navigation menu