David Aldridge Programming (PDF)




File information


Title: Gameplay Networking of Halo: Reach
Author: pparsons;daldridge@bungie.com

This PDF 1.5 document has been generated by Microsoft® PowerPoint® 2010, and has been sent on pdf-archive.com on 31/07/2015 at 00:00, from IP address 75.162.x.x. The current document download page has been viewed 875 times.
File size: 5.86 MB (101 pages).
Privacy: public file
















File preview


I S h o t Yo u F i r s t !
Gameplay Networking in Halo: Reach

Who am I?
• David Aldridge, Lead Networking Engineer at Bungie
• Spent three years working on
Halo: Reach networking
• I’ve been making games for a
while

What is Halo: Reach?
• [video]

Talk Takeaways
• A proven architecture for scalable gameplay
networking
• How to design solid networking for your game
mechanics
• How to measure and optimize your networking

What is this talk NOT about?
• Halo’s Campaign or Firefight networking
• Sockets/low level networking
• High level networking
– Matchmaking
– Rating & ranking systems
– Creating and curating an online ecosystem

BUNGIE’S GAMEPLAY NETWORKING
ARCHITECTURE

What is gameplay networking?
• Communicating sufficient information to maintain a
perceptually shared reality, while minimizing both
bandwidth use and perceived violations of the
integrity of the simulation (artifacts)
• OR: Technology to help multiple players sustain the
belief that they are playing a fun game together

Common simplifying approaches
• 1. Lockstep (a.k.a. deterministic, input-passing)
– Common for games with a strict split between input and simulation
(e.g. RTS), so input latency issues can be bypassed
– Also common for ports of classic games (avoids game alterations)

• 2. Reliable transport protocols (TCP or homegrown)
– Requires high bandwidth or simple networked state
– TCP requires high latency tolerance

• 3. Send all networked state as a single blob (atomically)
– E.g. Quake 3 model
– Works very well as long as the total networked state is not too large

Halo has to solve the hard problem





Highly competitive multiplayer action game
16 players, vehicles, hundreds of replicated objects
No dedicated servers
Game is expected to work regardless of connection
quality
• For N players, O(N2) data needs to be networked






Download David Aldridge Programming



David_Aldridge_Programming.pdf (PDF, 5.86 MB)


Download PDF







Share this file on social networks



     





Link to this page



Permanent link

Use the permanent link to the download page to share your document on Facebook, Twitter, LinkedIn, or directly with a contact by e-Mail, Messenger, Whatsapp, Line..




Short link

Use the short link to share your document on Twitter or by text message (SMS)




HTML Code

Copy the following HTML code to share your document on a Website or Blog




QR Code to this page


QR Code link to PDF file David_Aldridge_Programming.pdf






This file has been shared publicly by a user of PDF Archive.
Document ID: 0000292788.
Report illicit content