{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

ln004 - Game Engine Architecture Game-State the game-state...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon
Game Engine Architecture Game-State Simulator Controller Controller Controller Renderer Actions Updates Queries Queries Queries Game-State – the game-state represents the current state of the world. It knows about all the objects in the world and provides access to them so that they can be queried by all the other components for information about their current state. Simulator – the simulator encodes the rules of how the game-state changes based on the “game physics.” Together with a set of animations the simulator is responsible for generating a character’s moves in response to the actions chosen by the associated controller. Renderer – together with the game’s geometry and texture maps, the renderer is responsible for rendering a depiction of the game-state; usually with images and sound. Controller – each character in the game has at least one controller (“brain”) associated with it. The controller is responsible for selecting actions. For
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 2
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}