1 / 9

Building a flexible [Game Engine]

Abstraction, Indirection, and Orthogonality Aaron Moore. Building a flexible [Game Engine]. Definitions. Abstraction – Going away from the specific, dealing with things on a higher level Indirection – Loose coupling Orthogonality – Meshing systems without special cases.

phong
Download Presentation

Building a flexible [Game Engine]

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. Abstraction, Indirection, and Orthogonality Aaron Moore Building a flexible [Game Engine]

  2. Definitions • Abstraction – Going away from the specific, dealing with things on a higher level • Indirection – Loose coupling • Orthogonality – Meshing systems without special cases

  3. Strengths and Advantages • Eliminates some bottlenecks (Game Development) • Consistency • Exposes properties to designers • Component systems and Metadata

  4. Example: Unreal 3 Engine • What is Unreal 3? • Top-down engine framework • Content pipeline w/realtime preview • Framework • Object Management • Gameplay w/auto memory management • Engine systems • Content

  5. Object Management • Loose coupling of all objects creates a vastly customizable amount of content which can be placed into the code without disruption of other factors. • Inheritance • Gives distinct properties to different objects and still allows them to interact with the other objects

  6. Engine System • Stores explicit metadata for classes • Exposes properties to the designers so everything can be data-driven • Key elements can be changed without having things hard-coded

  7. Gameplay • Actors • Collision • Specialized per instance • Classes • NPCs • Inventory Items

  8. Content • Keeps things consistent yet provides distinct properties • Prevents things such as the combinatorial explosion of light and shadow options • Kismet – Visual Scripting • sequence objects • attach events

  9. Summary • Keeps things specialized per instance • Adding/Changing does not disrupt other teams • Component systems keep things flexible • Keeps things consistent

More Related