Next-Generation Game Development Rafael Chandler KRI April 6 ...

Next-Generation Game Development 

Rafael Chandler 

KRI 

April 6, 2007

About Media Sunshine 

Game Industry Consultants 

• Heather Chandler, Executive Producer 

• Rafael Chandler, Creative Director 

• Experience at Activision, EA, & Ubisoft 

• Combined total of over 50 shipped titles 

• Production, writing, localization, & design 

• www.mediasunshine.com

About Media Sunshine 

Shipped Titles Include: 

• Ghost Recon: Advanced Warfighter (X360) 

• Two Worlds (X360) 

• Monster Madness (X360) 

• Rainbow Six: Lockdown (Xbox, PS2) 

• Ghost Recon 2 (Xbox, PS2) 

• Rainbow Six 3: Raven Shield (PC) 

• Civilization: Call to Power (PC) 

• Heavy Gear II (PC)

Publications

1. Localization 

2. Design 

3. Production 

4. Narrative 

Overview

Next-Generation Game Localization

Next-Generation Game Localization 

Overview 

• Creating international content 

• Localization-friendly code 

• Localization plan 

• Simultaneous release 

• Organizing assets for translation 

• Integrating assets 

• Quality assurance testing 

• Console submission

International Content 

Checklist 

• Avoid culturally specific references 

• Be aware of age ratings per country 

• Sex and violence restrictions 

• Consider region-specific content

Localization-Friendly Code 

Language assets 

• All text, art, audio assets in one location 

• Words in text format, not code or graphics 

• Text in graphics should be layered 

• Follow established naming convention 

• Audio files: voice tracks separate


International characters 

• Support Unicode: international characters 

• Double-byte support for Asian, Cyrillic 

• Fonts support international characters 

• Font easy to read on standard and HD TVs


User interface 

• Text increase of 25-30% 

• Dynamically size boxes and UI elements 

• Use icons instead of text 

• Don't crowd UI elements onto screen 

• Support international currency, time, date


Keyboard input 

• International keyboards 

• Keys in different places 

• Keys mapped by location: third down 

• Or mapped by symbol: letter K


Technical considerations 

• Plan for subtitle support 

• How will localized VO handle lip-synch 

• Compatibility between languages (online)

Level of Localization 

Overview 

• Publisher decides level of localization 

• Based on region, sales expectation 

• Box-and-docs (no game localization) 

• Partial (only text localized) 

• Full (text and audio localized)

Localization Plan 

Developing plan 

• Cost estimates for translations, VO 

• Dev team schedule for integration, testing 

• How long will it take? 

• Are localizations released simultaneously? 

• Translation and testing usually outsourced 

• Dev team responsible for asset integration 

• Dev can create loc kit after game complete 

• Allows external dev to fully localize game

Localization Plan 

Asset overview 

• Number of words to be translated 

• File formats 

• Art, audio, text files need to be integrated 

• Translation vendor can then estimate costs 

• Allows team full picture of scope 

• Publisher uses this to estimate cost

Simultaneous release 

Overview 

• Challenge: start before code finalized 

• Difficult if not planned for in advance 

• If game loc-friendly, simship easier 

• Only alter language assets, not code

Simultaneous release 

Overview 

• Asset lockdown 4-8 wks before code release 

• Depends on amount of content in the game 

• Translators can handle 2000 words per day 

• 100,000 word game takes 50 days 

• Multiple translators can add inconsistencies

Organizing Assets 

Documentation 

• For translators prior to beginning work 

• Build of game 

• Design documents 

• Cheats/walkthroughs 

• Voice actor casting notes 

• Glossary 

• Technical overview


Text assets 

• Pulled out and formatted into spreadsheet 

• Send translators the TXT files (risk) 

• If multiple files, track with checklist


Voice assets 

• Master spreadsheet with content 

• Character, dialogue, context, filename 

• Casting notes, voice guide 

• Audio files in primary language 

• Indicate timed dialogue and duration


Other assets 

• Manual and box text 

• Keyboard reference card 

• Customer support info 

• Licenses and legal text

Integrating Localized Assets 

Overview 

• Time-consuming if copy/pasted into game 

• Automation of asset integration process 

• If dev, easier to control budget, schedule 

• If third-party, may get behind schedule (risk) 

• Assets checked into source control dbase 

• Usual process for language updates

Integrating Localized Assets 

Overview 

• Each language increases assets to track 

• Plan for file size increase after integration 

• If tight on memory limitations, this is risk 

• Number of languages on the disc 

• Which language displayed to the user 

• User selects, or automatically selected

Testing Content 

Functionality testing 

• Check for functionality bugs in loc versions 

• Font not displaying correctly 

• Wrong set of assets appearing in game 

• Not necessary to have language experts


Linguistic testing 

• Tracked like other bugs 

• Text truncations 

• Text overlap 

• Incorrect context 

• Wrong languages 

• Grammatical errors

Console Submission 

Process 

• Submission to Sony, Microsoft, Nintendo 

• If space on disc, all languages at once 

• Or separate discs, submitted separately 

• Glossaries for gaming platform terms 

• Incorrect terms can fail game

Next-Generation Game Design

Next-Generation Game Design 

Overview 

• Mainstream approach 

• Market realities 

• Concept development 

• Goal definition 

• Polish and presentation 

• Next-gen opportunities 

• Resources

Mainstream Approach 

Mass-market audience 

• Transition from hardcore audience 

• Impulse buys, buzz, word-of-mouth 

• Retail outlets, department stores 

• Anonymous customer, not forum fan 

• Difficulty level not as intense 

• Hollywood tie-in, brand awareness

Market Realities 

GameFly rentals, March 24-30, 2007 

• 8 sequels (GRAW 2) 

• 4 tie-ins (TMNT) 

• 2 sports games (MLB 2007) 

• 1 original game (Motorstorm) 

• Implications: risk-averse publishers 

• Millions of dollars, hundreds of developers 

• System and process become critical

Concept development 

Holistic design 

• What is user experience? 

• Immersion in the fantasy, culling of features 

• Necessary content becomes focus 

• D&D vs. Dread 

• Process of creating experience 

• Detachment from developer knowledge 

• Testing and verification of intent 

• Demonstrable goal achievement

Goal definition 

Developer vision 

• Specific emotions, moments 

• Key scenarios or opportunities 

• What is it that player does? 

• Why is it fun? 

• Does it command the player's attention? 

• How is goal realized via mechanics? 

• How do our tools help us create fantasy?

Polish and Presentation 

Top-ranked games on GameRankings.com 

• PS3 -- Resistance: Fall of Man 

• Xbox 360 -- The Elder Scrolls IV: Oblivion 

• Wii -- Zelda: Twilight Princess 

• PS2 -- Resident Evil 4 

• Xbox -- Halo: Combat Evolved 

• Gamecube -- Metroid Prime

Polish and Presentation 

Ramifications 

• Consideration of user experience 

• Absence of awkward fumbling 

• Small steps towards innovation

Next-Gen Opportunities 

Sony 

• PlayStation Home 

• Focus on community, online presence 

• User creates avatar on PS3 

• Home decorated through achievement


Microsoft 

• Xbox Live Arcade 

• Online game distribution service 

• Inexpensive casual games 

• Over fifty titles on 360 

• 25 million games downloaded


Microsoft 

• Games for Windows 

• Web site, brand management 

• Easy install option 

• Compatibility with 360 controller 

• Launches from Media Center


Microsoft 

• Cross-platform gaming 

• Shadowrun: Vista and Xbox 360 

• Several games predicted for fall 2007


Nintendo 

• Wii Channel 

• Customizable menu interface 

• Mii avatar 

• WiiConnect24 

• Constantly online 

• Community interaction 

• Promotions

Resources 

Books 

• The Game Production Handbook 

• Heather Chandler, Charles River, 2006. 

• Indie Game Development Survival Guide 

• David Michael, Charles River, 2003. 

• Game Development and Production 

• Erik Bethke, Wordware, 2003. 

• The Game Producer’s Handbook 

• Dan Irish, Thomson, 2005.

Resources 

Organizations 

• IGDA – www.igda.org 

• International Game Developers Association 

• Dedicated to the game dev community 

• Sponsors of the annual GDC 

• AIAS – www.interactive.org 

• Academy of Interactive Arts and Sciences 

• Academy that promotes common interests

Resources 

News sites 

• Blues News – www.bluesnews.com. 

Presents latest industry news, game 

reviews, and other info. 

• Develop – www.developmag.com. 

European game development magazine. 

• The Escapist – escapistmagazine.com. 

Weekly online magazine that covers 

gamers and gaming culture.

Resources 

News sites 

• Gamasutra – www.gamasutra.com. 

Features game development resources such 

as job postings, industry news, and articles 

about game development. 

• Gamespot- www.gamespot.com. A gaming 

news site with information about all genres 

and platforms.

Resources 

News sites 

• GameDev.net – www.gamedev.net. 

Features technical articles about game 

development and other useful information. 

• Game Developer Magazine – 

www.gdmag.com. This is a magazine 

published in the States that features articles 

on game development. It also includes job 

postings.

Resources 

News sites 

• Game Rankings – gamerankings.com. A 

useful website that posts all the reviews of 

a given game and determines an overall 

average based on these reviews. 

• IGN – www.ign.com. A gaming news site 

with previews, reviews, interviews, etc. for 

all game genres and platforms.

Resources 

News sites 

• Metacritic – www.metacritic.com. Posts 

and averages all the reviews of a game. 

• Moby Games – www.mobygames.com. 

Collects collects and posts information on 

game credits and other news about the 

game industry. 

• Next-generation – www.next-gen.biz. 

Features news and articles.

Next-Generation Game Production

Next-Generation Game Production 

Overview 

• Challenges 

• Project management 

• Agile & Scrum 

• Production techniques 

• Team management 

• Team building

Production 

Challenges 

• Next-gen more complex, more assets 

• Multiplatform development 

• PS3, X360, Wii, PSP, DS, PC versions 

• Outsourcing large part of production 

• Some studios have tracking departments 

• Management of production process

Formal Project Management 

Overview 

• More control over game dev cycle 

• Tangible process motivates team 

• Easier to determine project status 

• Bringing new team members up to speed 

• Generation of project metrics

Formal Project Management 

Disadvantages 

• People don’t like change 

• Devs may be reluctant to try new system 

• Can be costly to develop/implement 

• Team Software Process takes 2 weeks 

• Everyone in team must participate

Agile Game Development 

Overview 

• Much attention in recent years 

• Set of methods focused on product value 

• Attained through iteration and feedback 

• Focus is on functional version of game 

• Instead of assembling parts, build basics 

• Always a working version of the game 

• Functionality built upon iterations


Scrum 

• One type of Agile, focused on management 

• Flexible; used in a variety of situations 

• No formal training required; inexpensive


Characteristics of Scrum 

• Create subsets of self-directed teams 

• Teams are small and cross-functional 

• Each subset headed by “scrum master” 

• Responsible for removing team’s obstacles 

• Work to create tangible deliverable on time 

• Deliverables every 2 or 4 weeks


Benefits of Scrum 

• Iterative nature allows progress tracking 

• Always something functional 

• Easier to remove features against deadline 

• Successfully used by numerous studios 

• High Moon Studios (Darkwatch)


More information: 

www. agile game development .com

Production Techniques 

Balance 

• Between time, resources, features, quality 

• Increase time in schedule 

• Increase number of people on project 

• Cut features from game 

• Reduce quality/scope of features


Risk analysis 

• Risks are things that can go wrong 

• Constantly assess potential risks 

• Better to over-prepare for what might be 

• Saves time and stress when things go wrong


Risk analysis 

• Steve McConnell, Rapid Development: 

• Identify risks that could happen 

• Analyze probability and impact 

• Prioritize risks based on impact 

• Create plan to neutralize most critical 

• Implement plan, monitor progress


Project reviews 

• Useful for monitoring game progress 

• Teams getting larger, games more complex 

• Once per month, if not more often 

• Identify and neutralize problems 

• Key decision-makers must attend 

• Focuses developers on overall progress


Conducting project reviews 

• Compare plan with current status of project 

• Note accomplishments since last review 

• If no progress made, project in trouble 

• Identify risks, propose solutions 

• Identify and remove roadblocks 

• Update schedule, deliverables, milestones 

• Identify necessary resources (people, tools) 

• www. project review .net


Critical stage analysis 

• Technique developed by Wolfgang Hamann 

• Getting regular feedback from team 

• Measure what each individual thinks at time 

• Allow team to provide feedback 

• Show that thoughts are taken seriously 

• Pointless to wait until postmortem 

• CSA done on monthly basis, or milestone



• Survey provided to all team members 

• What 5 things went right? 

• What 5 things went wrong? 

• What 5 things could be improved?



• Producer collates results of survey 

• Publish action plan 2 days later 

• Plan deals with top 5 concerns 

• People assigned specific tasks, deadlines 

http://www.gamasutra.com/resource_guide/ 

20030714/hamann_01.html


Feature creep 

• New features added without adjustment 

• Features impact time, resources, quality 

• From management, leads, team, fans 

• Adding features can improve final game 

• Some feature requests damage project 

• Research impact of feature addition


Feature creep 

• Presentation of options: 

• Add feature, but others removed, reduced 

• Add feature, but need time, team, or money 

• Add feature without impact 

• Communicate impact to the team 

• Change Request Forms to document adds 

• Prioritize new features, critical first


Task force 

• Cross-discipline group of developers 

• Troubleshooting, developing solutions 

• One member from each discipline 

• Design, art, programming, testing 

• Group develops several solutions 

• One is selected – the decision is final 

• Gives team ownership of their work 

• Personal investment in process


Prototyping 

• Helps determine strength/weakness of idea 

• Before time, money spent on assets, code 

• Tweak feature cheaply during prototyping 

• More defined feature can be implemented


Managing teams 

• People are most important asset 

• Keep team happy to get best work 

• Few unhappy employees infect team 

• Building team is critical for good game 

• Constantly seek better communication 

• Communication from top down 

• Management, producer, lead, team 

• Face-to-face is important


Motivating teams 

• Roles must be defined 

• Team view of role must match member 

• Provide role-fulfillment resources 

• Provide information about role 

• Also note impact and significance to team



• Cross-training can help build teams 

• Engineer spends a day watching an artist 

• Artist spends day testing bugs in QA 

• Leads to process-improvement suggestions 

• Team understands itself better 

• Integration of new team members



• Team meeting 

• Useful way to communicate in person 

• Public discussion of concerns 

• Answered questions, information 

• Social opportunity for team 

• Updated deadlines and schedules

Next-Generation Game Narrative

Next-Generation Game Narrative 

Overview 

• Context 

• Story design 

• Narrative structure 

• Documentation 

• Cinematics 

• Voice acting 

• Story integration 

• Testing content

Context 

Evolution of narrative justification 

• What’s happening and why 

• Once communicated through packaging

Context

Context

Types 

• Brick-and-mortar 

• Story-driven 

• Open World 

Story Design

Story Design 

Developer collaboration 

• Design: context, scripting 

• Audio: sound, voice 

• Art: characters, cinematics 

• Programmers: AI, engine

Story Design 

Parameters 

• Gameplay: what happens in-game 

• Brand: association with fans 

• Marketing: advertisement, features 

• Competition: other games, other brands

Narrative Structure 

Logocentric vs. Mythocentric


Logocentric structure 

• Authority: developer 

• Experience: scripted 

• Design: control 

• Ramifications


Mythocentric structure 

• Authority: player 

• Experience: open 

• Design: opportunity 

• Ramifications

Documentation 

Audience 

• Designers: scripting, gameplay, integration 

• Scripters: placement, action, dialogue 

• Audio team: effects, filenames 

• Programmers: AI patterns, scripting tools 

• Voice actors: dialogue, character, context 

• QA testers: integration, execution

Documentation 

Screen/Play 

• Process: each game different 

• Programs: Excel, Open Office Spreadsheet 

• Structure: spreadsheet with visible grid 

• Format: columns, headings, sorting 

• Interaction: members of dev team 

www. open office .org

Cinematics 

Development 

• Concept: vision for events, lines 

• Material: documentation, screenplay 

• Storyboards: 2D representation 

• Animatics: flipbook, roughs 

• Audio: voice acting, sound effects 

• Iteration: evaluation, critique

Voice Acting 

Planning 

• Characters definition 

• Voice notes: description, comparison 

• Pitch, accent, vocabulary 

• Role, status, story arc 

• Key moments, memorable lines 

• Team relationships, integration

Voice Acting 

Planning 

• Casting: audio palette, adaptation 

• Participation: team members attending 

• Schedule: timetable based on lines 

• Accuracy: voice acting on or off 

• Variation: multiple takes, identical 

• Role: specific idea of character

Voice Acting 

Recording 

• Process: role definition, structure 

• Documented specificity of situation 

• Researched pronunciation 

• Direction: warm-up, character 

• Context, momentum, feedback 

• Assets: delivery, format, integration

Story Integration 

Process 

• Scripters require documentation 

• Events, actors, sequence, dialogue 

• Filename conventions 

• Level organization 

• Consistent citations and names 

• Version control and access

Dialogue 

• Interruptions 

• Player movement 

• Dead speaker 

• Retriggered cues 

• False awareness 

• Dependent cues 

Story Integration


Quality Assurance 

• Schedule: production, post-production 

• Sooner the better, identify problems 

• Prototype VO with placeholder 

• Revise while cheaper and easier 

• Personnel: QA testers 

• Dedicated story tester 

• Writer, designers, scripters, audio


Materials 

• Story documents: dialogue, summary 

• Screenplays, spreadsheets, testplans 

• Cinematic lists: number, structure 

• Character voice notes, bios


Defects 

• Classification, severity: low on list 

• Dialogue: specific cues 

• Cinematics: prerendered or scripted 

• Missing cue, wrong cue, interruption 

• Inappropriate VO for situation 

• Incorrect animation, missing context 

• Alternate cue needed

Postpartum 

Checklist followed by role-focused plan 

• What went wrong or right? 

• What was unexpected? 

• How did story turn out? 

• What was status of story elements? 

• Cinematics, dialogue, scripted events 

• What resources would have helped?

Thank you for your time! 

heather@mediasunshine.com

Next-Generation Game Development Rafael Chandler KRI April 6 ...

Create successful ePaper yourself

Delete template?

Save as template?