CS
5964/6964:
Interactive Machinima
CS
5964/6964:
Interactive Machinima
Spring 2009
Home | Syllabus | Schedule | Resources
This is a project-oriented class designed to teach you the skills to produce Machinima.
Successful completion of CS3500.
Communication in the class is via mailing lists:
The laboratory part of the class will be in our 130/124 EMCB Instructional Lab or on your own computers.
We will be using Windows in order to run the tools. You can get Microsoft Software from the MSDN Microsoft Academic Alliance. Simply email opers@eng.utah.edu with your eng.utah.edu login information and they will get you set up.
None
Much of the work during the semester will be in a team. Choosing a team wisely is important.
This is a project class, so the assignments will be few. Our current plan is for you to demonstrate knowledge of using the various tools and then work on a final Machinima.
As a project class, we do not anticipate any quizzes or exams. But things may change as we go along.
Points will be given for the various assignments and the final project.
Should you discover what you think is an error in grading, you have only TWO WEEKS after the grades are posted to request a regrade. The procedure you should use is to first go and see the TA who did the grading and see if you can get it resolved. If you are still unsatisfied, then you should go and see Professor Kessler.
Unless otherwise stated in the homework assignment, all homework solutions will be due by class time (that is noon) on the homework due date. The time that we use for the hand in of a homework is the creation time of the source file in the submit directories. Be careful not to overwrite a file and wipe out its creation time.
Assignments will not be accepted late—with the following exceptions:
Individual assignments - Each student will receive two late days for the entire course. Each late day allows you to extend the assignment deadline for one day (24 hours). To use a late day you simply submit the assignment late. We will assume that any assignments submitted late count against your late days.
Team assignments - Each team will receive two late days for the entire course. The same rules apply as above for individuals.
Any late assignment that is not accompanied by a valid late-day usage will not be accepted. There are no exceptions or excuses; the late days are intended to cover unforeseen circumstances.
No late days can be used for the final project.
The purpose of the homework is to improve your skills at solving problems and demonstrating that you have absorbed the class lecture material. Collaboration with other class members is acceptable when discussing the homework problems and how to go about solving them.
However, the code that you write must be your own. Sharing code or using someone else's code is considered plagiarism and will be dealt with using standard College and University procedures. This is a copy of the policy.
During the team phase of the course, collaboration and sharing of code with your team members is of course expected.
Note, here is the student code.
During the team phase, if a team member flakes out and doesn't do the work assigned to them, then we reserve the right to adjust the scores accordingly. This may mean adjusting the person not doing their job lower and possibly, in rare occurrences, adjusting the rest of the team higher (because they had to cover for the person "flaking out"). If this starts to happen at any point during the semester, please inform Professor Kessler IMMEDIATELY.
The information on these topics is college wide and provided here.