Computer Games Laboratory (IN7106, IN710615)
hold by Prof. Dr. Westermann
|Time, Place||Wednesday, 16:00-18.00, 02.13.10 |
(only on days with milestone submissions, see detailed schedule below)
Oct. 17., 2018
Mandatory kick-off meeting: room: 02.13.010 . (No matching system needed. If you cannot make it to the kick off, contact us... it won't be possible to join later on!)
Main wiki: wiki.tum.de/display/gameslab1819/Home
This course is open only to master students in Informatik: Games Engineering. The module comprises lectures, programming exercises, and student presentations
|Final pres.:||The final presentation of results will take place during the demo day (exact date tba), and there will be a prize for the best game!|
|Prerequisites||Bachelor Informatik: Games Engineering|
Computer games development comprises the conception of the game world and the specification of the game flow and rules, artistic aspects, as well as the technical realization of the game via software, interaction- and display-devices. The goal of this course is to facilitate an in-depth understanding of the game development process. Students gradually design and develop a computer game in small groups and get acquainted with the art of game programming.
The Computer Games Laboratory addresses modern three-dimensional computer games technologies. In small teams, students will design and develop a computer game. The focus will be on the technical aspects of game development, such as rendering, interaction, physics, networking, distribution and parallelization, animation, and AI. In addition, we will cultivate creative thinking for advanced gameplay and visual effects.
This is a practical course which involves a hands-on approach with neither traditional lectures nor exercises. Instead, we will meet ca. once a week to discuss technical issues and to track progress. Students can utilize available game engines, yet we will make sure that a considerable own programming effort will be invested. While development will take place on PCs, students are free to choose the target platform of their final game.
At the end of the course, all results will be presented to the public. The best projects, choosen by the audience and a jury of experts from industrial partners, will be awarded hard- and software prices.
- Good programming skills (course projects are written in C++).
- Students should have passed successfully the Bachelor program Informatik: Games Engineering.
- We recommend higher level courses in the area of specialization related to the game technology making your game distinct.
Regardless the content of the game, the development process must adhere to the guidelines proposed below. Students are encouraged to design a game that has strong links to one of the areas of specialization in the curriculum of the Master program Informatik: Games Engineering.
Students chose their favorite area of specialization and contact the corresponding adminstrator (see list below) to propose and discuss the intended game. Teams from different areas can also join to create an even more complex game.
All students have to sign up for the Computer Games Laboratory and attend the mandatory lectures. It is not possible to join later on during the semester.
Note that sign-up for this practical course is happening only during the kick-off meeting at the end of the semester break (i.e., shortly before the summer or winter semester starts). The matching system (for seminars etc.) is not used, and thus you won't see this practical course within the matching system.
The following table gives an overview of all in class meetings during the semester. On all none mentioned weeks there is no class.
|lecture / milestone||date||team presentation||to publish on the wiki|
(due before presentation)
|Kick-off Lecture: softskills and prototyping||Oct. 17th||Form groups, email to email@example.com (also if you didn't find a group so far, but still want to participate!)|
|1. Milestone: Game idea pitch||Nov. 7th||Game idea||Report: Game idea proposal|
Slides: Game idea
|2. Milestone: Prototype||Nov. 21th||Prototype||Report: Prototype|
|3. Milestone: Interim Demo||Dec. 12th||First programming results||Report: Interim results|
Slides: Interim results
4. Milestone: Alpha release
|Jan. 16th||Alpha version||Report: Alpha release documentation|
Slides: Alpha release
|5. Playtesting||Jan. 30th||Playtesting results||Report: Playtesting results|
Slides: Playtesting results
|6. Final Release||Feb. 13th||no presentation|
Report: Final documentation
|Demo Day live presentation||Feb. 5th||pre-final |
Previous instances of this course