next up previous
Next: About this document ...

Department of Computer Science, Clemson University
CpSc 481/681, 3D Game Development
Policies and Information
Brian Malloy, PhD
January 17, 2007



Office: 313 McAdams Hall Phone: 656-0808
Office Hours: TBA e-mail: malloy@cs.clemson.edu
No office hours on Mon or Fri TA: me



  1. There is no official textbook for this iteration of this course. I will be taking material from anyplace I can get it!

  2. Tentative Grading Policy ($\pm$ 10%):

    Exams 50% Date: Feb 7th, Mar 7th
    Final Exam 10% Date: Apr 25th
    Presentation 10% Date: before Apr 25th
    Assignments 20% Probably 4 or 5 assignments
    Final Project 10% May 2nd, Wed 6:30 - 9:30 PM
    Martin Luther King jr   Jan 15, Mon
    Spring Break   Mar 19-23, Mon-Fri
    Final Exam Week   Apr 28-May 5, Sat-Sat

  3. Course objective: to master techniques in game engine construction using: the Simple DirectMedia Layer (SDL); OpenSceneGraph (OSG); and the C++ programming language.

  4. Assignments: The first assignment will be done on an individual basis; assignments after the first can be accomplished in groups of size 1 to 3 students.

  5. Exams: All exams will be taken on an individual basis. Exams will be in class and written. There will be two kinds of exams: (1) consisting of reading and writing C++ code, and (2) consisting of reading C++ code and answering questions about reading assignments including the tutorial that Rob and I are developing.

  6. Presentation: A presentation of a technique that would facilitate 3D Game Development. Your presentation should include a small code-based example demonstrating the technique. Also, you must construct either a powerpoint slide presentation or web page(s) presentation providing detailed explanation of how the technique works, as well as the advantages and disadvantages of using the technique. Your presentation may be in groups of size 1, 2 or 3. If you are unable to make a presentation, then you must submit a survey paper consisting of a code example and a complete description of what the code does and how the code works.

  7. Exemption: If you receive an A for your Presentation, have perfect attendance for all presentations and are carrying an A in the course, you may exempt the final. You may not exempt the final if you do not make a presentation.

  8. Attendence: Attendence at classes is expected. Many studies have found that the single factor that contributes the most to success in a course is class attendance. Failure to attend not only hurts you, but places an extra burden on the instructor and detracts from the overall quality of the course. If you have exceeded 3 unexcused absenses before the drop date you may be dropped from the course. If you are not or cannot be dropped, or if the last day to drop has already passed, you will receive an F for the course. You are responsible for keeping track of your situation in the course. If you know that you have exceeded the maximum number of absences before the last day to drop you should go ahead and drop the course yourself to avoid an F.

  9. Policy and Syllabus: This policy & the syllabus can be found on my web page.
    www.brianmalloy.com
    

  10. Venue: The course meets in Daniel 408 on Monday and Wednesday from 4:00 until 5:15. If the instructor has not arrived by 4:15, you may assume that he isn't coming.

  11. 481: This course will be incorporated into the regular curriculum with a normal course number.

  12. Grades: The grading scale is: 90 or better is an A, 80 or better is a B.

  13. Behavior: Please do not engage in side conversations during class. Try to direct your comments to all of us. I believe that we're all interested in learning more about game construction.




next up previous
Next: About this document ...
Brian Malloy 2007-01-17