# For each member of the team create a text file named as '''"YourSenecaEmailId.txt"''' in SubmissionLogs directory. In this text file, in a point form format, specify in detail, all the tasks you have done for the project.

# For each member of the team create a text file named as '''"YourSenecaEmailId.txt"''' in SubmissionLogs directory. In this text file, in a point form format, specify in detail, all the tasks you have done for the project.

# Branch (copy) the whole project including the SubmissionLogs directory and its text files into tags directory under '''"prj1.0"'''.

# 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.

# 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)

+

#:(when marking, the last revision is considered as your submission)-->

This course continues the study of game programming techniques begun in the introductory course. Topics covered include modeling, texturing and lighting techniques, force feedback, and shader programming

The course is supported by the open instructional software framework introduced in GAM666/DPS901. Students refactor select components of the framework to augment the base code for all members of the class.

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 from the introductory course. Each team consists of up to 3 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 features that your team will add to the framework and identifies which member will work on which feature. Each member is responsible for a distinct feature. Each team meets with the instructor to review the proposal and obtain approval. The second stage is a release of the framework that includes the feature. The third and final stage presents your own team's completed game to the class, which includes your features along with several features incorporated by other teams. Details are on the Project Requirements page.