1 / 23

CIS 300 Introduction to Computer Game Design cis.cornell/courses/cis300/2005sp

CIS 300 Introduction to Computer Game Design http://www.cis.cornell.edu/courses/cis300/2005sp http://www.cs.cornell.edu/projects/game Lecture 1: Introduction Spring 2005. Announcements. Room: Olin 255 this week! (MTWF) Reading assignments....

arista
Download Presentation

CIS 300 Introduction to Computer Game Design cis.cornell/courses/cis300/2005sp

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CIS 300 • Introduction to Computer Game Design • http://www.cis.cornell.edu/courses/cis300/2005sp • http://www.cs.cornell.edu/projects/game • Lecture 1: Introduction • Spring 2005

  2. Announcements • Room: Olin 255 this week! (MTWF) • Reading assignments.... • Chapter 1 of R&A for Tuesday, and Chapter 2 for Wednesday • Chapter 23 (pp313-327) of S&Z for Friday • yes, you must do reading

  3. Overview • Introduce staff • What is CIS300? • Priority: head count, survey • Syllabus • Coursework and expectations • Resources • Engineering technical writing credit • CIS300 or CS/CIS490?

  4. Instructors • Computer Science: • Mohan Rajagopalan, Instructor of CSmohan@cs.cornell.edu, 320 Upson Hall • David I. Schwartz, Lecturer of CSdis@cs.cornell.edu, 5137 Upson Hall • Music: • David Borden, Senior Lecturer of Musicdrb4@cornell.edu, 130 Lincoln Hall • Art: • guest lectures from faculty • Communication: • Jerry Gabriel, Lecturer of Engineering Comm.gg67@cornell.edu, 437 Hollister Hall • Rick Evans, Senior Lecturer of Engineering Comm.rae27@cornell.edu, 465 Hollister Hall • Tammy Shapiro, Assistant Professor of Org. Comm, Learning, and Designtshapiro@ithaca.edu, 359 Roy H Park Hall, Ithaca College • Our backgrounds...

  5. Teaching Assistants • Teaching Assistants: • Colin Campbell, cc374@cornell.edu • Piti Irawan, irawan@cs.cornell.edu • Justin Pease, jsp34@cornell.edu • Alec Rivers, arr33@cornell.edu • two more TAs (TBA) • Offices and contact: • usually by e-mail • newsgroups:http://www.cis.cornell.edu/courses/cis300/2005sp/usenet.html • cornell.class.cis300 • cornell.class.cs490.game • Well, that was us...so...

  6. Who are you? • We need to know more about you! • Survey being passed around: • name, Net-ID • your skills: art, programming, music, writing(helps us form design groups) • Prerequisites: • programming: CS211 and C++ • art: Experience with Photoshop and Illustrator, or similar software; ART 251 or equivalent • music: CS100 or equivalent; MUSIC 120 or equivalent • writers: CS100 or equivalent; ENGL 280/281 • Others? Mixed background/interests? • Who gets to do design? Need to explain CIS300...

  7. CIS 300 • CIS 300: Introduction to Computer Game Design • CIS vs CS: • Computing and Information Science/Computer Science • CIS course applies or explores aspects of CS in context of other field(s) of study • Computer game design and development involves... • art, music, writing, pogramming, ... , creativity! • we are interdisciplinary • Description: This course investigates the theory and practice of developing computer games from a blend of technical, aesthetic, and cultural perspectives. Technical aspects of game architecture will include software engineering, artificial intelligence, game physics, computer graphics, and networking. Aesthetic and cultural aspects of design will include art and modeling, sound and music, history of games, genre analysis, role of violence, gender issues in games, game balance, and careers in the industry.

  8. Interdisciplinary Groups • Artists and programmers and misconceptions • Respecting each other's contribution and ideas From "Pixel Pusher," Steve Theodore, Game Developer, January 2005, http://www.gdmag.com

  9. Objectives • "real world" training: • Provide motivating opportunity for students to experience teamwork with people in different fields • Apply skills to learn how to build a big project • Introduce game analysis, design, and development: • What degree do you get to work in game industry? • Provide a starting point for those on the path... • Motivate students to take later courses: • digital art, music • artificial intelligence, graphics • many more! • So, how will we do all of this...?

  10. CIS 300 Content • Lectures • Labs • Writing assignments • Group discussion • More detail....

  11. Lectures • mandatory attendence • sometimes traditional "chalk-and-talk" • often, group discussion based on textbook readings • discuss design & development process • explore aspects of games and develop analytical skills • occasional writing assignments • occasional group meeting time • occasional industry lectures! • will be meeting in Olin 218 • will be splitting class in half on Friday • ½ go to lecture on MF • ½ go to lecture on TW

  12. Game Laboratories • again, mandatory attendence • initially, develop skills based on roles • 2-3 skill-development labs • work on material depending on your field(s) • eventually, group meeting time • occasionally used for presentations and critique sessions: • groups will present their work a few times • opportunity to learn from other groups • Location: (CL)3 • Cornell Library Collaborative Learning Computer Laboratory • http://cl3.library.cornell.edu • Uris Library: enter across from Olin Library, turn left at security desk, go down a few stairs, STOP!, turn left • labs on W or M (based on lecture day)

  13. Writing/Communication Labs • mandatory attendence • CIS 300 fulfills Engineering College's technical writing requirement • But...everyone is already involved in writing and documentation and communication: • learn about writing for games and documentation • group interaction and evaluation • website development and other "advertising" • presentation • Meet in CL3 (T or F based on lecture day) • So, what are all the groups doing...?

  14. The Game • Main goal: create your game! • Groups: • generally, we form based on related interests • try to balance art and programming + others • everyone involved in design • How to get from ideas to game? • labs for getting skills up to speed (C++, photoshop, ...) • some homework to learn about nature of games • milestones (deadlines) to move you along

  15. Other Meetings • Occasional movie nights • Game sessions • More on these later....

  16. Another Class...GDIAC Showcase! • Showcase: • Wednesday, May 11, 2005, 3-6 PM • Mandatory • What is it? • we invite Cornell, locals, companies,... to see your games • kids, too!(something to consider when you start your design....)

  17. Grading • Grades based on attendance and participation, group self-evaluations, homework, and mostly your game • No exams. • Breakdown: • 40% - Game • 30% - Homework • 20% - Attendance, participation, and group evaluations • 10% - Showcase and final presentation

  18. Your Games • 2-D • Single or multiplayer on same keyboard and CPU • Exhibit artificial intelligence, collision detection, level design • Balance of art and technical aspects • Start small. Get big later. • Fun! • CIS300 Recommendations? • See GDIAC gallery • Note: some games are Part2, so will be more intense than CIS 300 games • Ask us for recommendations • Other things you need for course...

  19. Textbooks • Andrew Rollings and Ernest Adams on Game Design by Andrew Rollings and Ernest Adams, New Riders (and Pearson), 2003. • Rules of Play: Game Design Fundamentals by Katie Salen and Eric Zimmerman, The MIT Press, 2004. • Others books? Quite a few....

  20. Labs, Accounts, Software • Primary lab: • CLCLCLor just (CL)3 • http://cl3.library.cornell.edu • Secondary labs: • CSUG (Computer Science Undergraduate Lab): • http://www.csuglab.cornell.edu/ • We will process accounts once people confirmed • We will chase you down about activating accounts: • extra facilities where you can work • location of eventual showcase • activation: http://www.csuglab.cornell.edu/userinfo.html • Software: • photoshop • Vis Stuido .Net (free!) • Reason • What else should you be using...?

  21. Games! • We require you to play games! • usually, we will try to assign games to investigate • occasional movie nights • occasional group game sessions • Study focus: Asheron's Call 2 • everyone gets free copy + 90 days • we will have structured assignments • related activities: • possible "Cornell Army"? • competitions with other schools? • product evaluation

  22. CIS 300 vs CS/CIS 490 • CIS 300: • for past years, CIS300 was "Part 1" • effectively, an experimental intro course • CS 490: • the "second course" (also called "Part 2") • actually, all CS profs have a CS490: Supervised Undergradute Research • we conduct research projects, 3-D games, networked games, MEng projects, company projects • CIS 490: • also "Part 2" • reserved for people in Part 2 involved in non-CS aspects of design (art, music, writing) • How to get into CS/CIS 490?

  23. GDIAC • GDIAC: • The Game Design Initiative at Cornell • http://www.cs.cornell.edu/projects/game • Membership: • anyone who takes/teaches the courses • always looking for more contributors • alumni! please stay in contact after you graduate • Company info sessions: • internships, co-ops, entry-level jobs • EA, Vicarious Visions, Turbine, .... • Mission: • teaching, research, outreach • trying to help make games part of academia at Cornell

More Related