liveBook · Manning

Visual data

As explained in High Performance Unity Game Development

Visual data represents the scene objects and presentation state used to display a game's simulation.

Visual data holds the scene objects and presentation state used to display a game. Keep it separate from logic data: an enemy’s GameObject active state controls visibility, while a separate Alive array records whether the enemy is in use. section 3.3.4

Separating the two lets a game:

  • Save logic data and recreate visuals when loading. section 3.3.4
  • Run server-side checks or large-scale balance simulations without drawing anything. section 3.3.4

How High Performance Unity Game Development covers it

How deep it goes
Defines the separation and demonstrates it with an enemy pool, while deferring fuller treatment.
Examples
Uses pooled enemy GameObjects for visibility and a separate Alive array to track enemy use.
What you can do after
Apply via Unity GameObjects by toggling visibility separately from an Alive array that tracks enemy use.
How it connects
Connects visual data to game logic, object pooling, save-game reconstruction, and server-side simulation.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of High Performance Unity Game Development. The section links point to the parts of the book it draws on.