FIT3145 Games engine programming - Semester 1, 2015

This unit exposes students to a variety of industry standard games engine environments and development techniques. Students will develop an appreciation and basic working knowledge of a number of different platforms used in contemporary games development. The unit aims to provide students with a practical insight into contemporary, industry standard, games development process and games engines.

Mode of Delivery

Workload Requirements

Minimum total expected workload equals 12 hours per week comprising:

(a.) Contact hours for on-campus students:

• Two hours of lectures
• One 2-hour tutorial

(b.) Additional requirements (all students):

• A minimum of 8 hours independent study per week for completing lab and project work, private study and revision.

See also Unit timetable information

Unit Relationships

Prerequisites

FIT2049 and FIT2073

Chief Examiner

Campus Lecturer

Tutors

Your feedback to Us

Previous Student Evaluations of this Unit

Based on student feedback this unit is well structured and no changes have been made for this semester.

Academic Overview

Learning Outcomes

• evaluate the appropriateness of a game engine to a specific game design brief;
• compare several game engines and rate multiple factors to judge relative value;
• analyse and research a game engine, then structure and present your findings to an audience;
• construct a basic game, using programming with a contemporary game engine.

Unit Schedule

*Unit Schedule details will be maintained and communicated to you via your learning system.

Teaching Approach

Assessment Summary

In-semester assessment: 100%

Assessment Requirements

Assessment Policy

Assessment Tasks

Participation

• Assessment task 1

  Title:

  Research and Presentation of Findings of a Specific Game Engine

  Description:

  Students will choose a game engine and present research findings related to the engine (see Moodle for game engines and times that each presentation will occur).
  
  Students will answer questions from peers and staff attending and in the following week on Moodle forums.
  
  Students are expected to provide a copy of their presentation and presentation notes as part of this assessment task.

  Weighting:

  20%

  Criteria for assessment:

  Students will be assessed based on clarity, completeness, presentation skills, research quality and answering questions posed by peers during the presentation and in the Moodle forums.

  Due date:

  Depending on schedule, due during one lecture, from Week 3 to Week 10

  Remarks:

  Please refer to Moodle for a detailed description of expectations for this assignment.

• Assessment task 2

  Title:

  Class Test (Case Study)

  Description:

  Students will be given a case study and will be required to decide which game engine (from the engines discussed during semester) is appropriate for the project.  Students will discuss the reasons behind their choice, benefits and negatives regarding the engine they are proposing and expected game design process and workflow based on the engine chosen.

  Weighting:

  20%

  Criteria for assessment:

  Clarity and reasoning behind choices, completeness and appropriateness of discussion.

  Due date:

  Week 12 during lecture

  Remarks:

  Please refer to Moodle for a detailed description of expectations for this assignment.

• Assessment task 3

  Title:

  Lecture and Forum Participation

  Description:

  In the lecture time, students will create written feedback related to each of the weekly presentations done by students and post the feedback on the Moodle forums.

  Weighting:

  15%

  Criteria for assessment:

  Clarity and appropriateness of feedback.

  Due date:

  Weekly, due before midnight each Wednesday, from Week 2 to Week 11

  Remarks:

  Please refer to Moodle for a detailed description of expectations for this assignment.

• Assessment task 4

  Title:

  Assignment (Game Creation)

  Description:

  Students will design and create a working game and a reflective document describing their thoughts on the game engine chosen for this task.  As part of this assignment, students will create a document describing their game (due week 5, worth 5%), meeting self-described milestones (due week 10, worth 5%), create a working prototype with completed key gameplay (due week 12, worth 5%) and submit a complete game (worth 30%) in week 15.

  Weighting:

  45% (5% for project plan, 5% for milestone completion, 5% for working prototype, 30% for game)

  Criteria for assessment:

  For the project plan, (worth 5%): Completeness, clarity and appropriateness of description and milestones

  For the milestones (worth 5%): Completeness of key gameplay elements of the game, as specified in milestones

  For the prototype (worth 5%):Functioning elements of the game, as specified in the design document

  For the game (worth 30%): Completeness, originality, technical (programming, design, art, etc.) skills shown

  Due date:

  Document describing game (due week 5, worth 5%), completion of milestones (due week 10, worth 5%), working prototype with completed key gameplay (due week 12, worth 5%), complete game (worth 30%) in week 15.

  Remarks:

  Please refer to Moodle for a detailed description of expectations for this assignment.

Learning resources

Feedback to you

• Informal feedback on progress in labs/tutes
• Graded assignments with comments
• Test results and feedback

Extensions and penalties

Returning assignments

Assignment submission

Online submission

If Electronic Submission has been approved for your unit, please submit your work via the learning system for this unit, which you can access via links in the my.monash portal.

Other Information

Policies

Graduate Attributes Policy

Student Charter

Student services

Monash University Library

Disability Liaison Unit