This document is about: QUANTUM 2
SWITCH TO

Execution Order

Most framework scripts rely on a standardized set of custom initialization, deinitialization and ticking methods:

  • Initialize()
  • Deinitialize()
  • Tick()

These are used to provided a consistent and replicable execution order accross devices and simulations. In addition these can be called at will and do not rely on the Unity execution order or the MonoBehaviour lifecycle and lifetime. It is recommended to use these when inheriting or extending framework classes; otherwise, it is the developer's responsibility to ensure the execution order is respected.

Tick Order

Tick() will be run for all objects before any MonoBehaviour Update() is executed. All common MonoBehaviour methods (Awake()/Start()/Update()) can still be implemented if needed.

The following graph presents the the tick order of the most important Unity and framework parts. Note: The priority order is visualized as follows:

  • Left => Right
  • Top => Bottom
fps template tick order
FPS Template Tick Order.

Lifetime / Persistency

The scripts of the core framework have varying lifespans. In the following graph Following graph shows the scripts persistency from most (top) to least (bottom) persistent; if the box is aligned with the previous one, the lifetime is identical.

fps template scripts persistency
Scripts Persistency.
Back to top