pixijs-ticker

Guidance for running per-frame logic and controlling the PixiJS v8 render loop through the Ticker. In v8, app.ticker registers callbacks that fire every frame and drives app.render() at UPDATE_PRIORITY.LOW. Each callback receives the Ticker instance itself, which exposes three distinct timing values: deltaTime, a dimensionless multiplier roughly equal to 1.0 at 60fps that is speed-scaled and minFPS-capped; deltaMS, real milliseconds for time-based calculations such as pixels per second; and elapsedMS, raw frame time with no scaling or cap, useful for profiling.

The skill covers the full registration API, including Ticker.add and addOnce, removal that must match both function and bound context, and priority ordering across INTERACTION (50), HIGH (25), NORMAL (0), LOW (-25), and UTILITY (-50). It explains frame-rate capping with maxFPS (which skips updates to enforce a ceiling) and minFPS (which caps the delta so large frame drops do not produce enormous values), plus speed scaling that affects deltaTime and deltaMS but not elapsedMS. It also distinguishes Ticker.shared (an autostarted, destroy-protected singleton), Ticker.system (used for engine background tasks), and a new Ticker() instance whose lifecycle you manage yourself.

Use it when building animation, physics, or game loops, when ordering systems by priority, or when you need manual control over rendering via app.start()/app.stop(), the autoStart: false option, and a custom frame driver calling ticker.update() and app.render(). The per-object onRender hook is presented as an alternative to a global callback for logic tied to a single display object. A prominent common-mistakes section warns that v8 passes the Ticker instance (not a delta number) to callbacks, so the v7 pattern of doing arithmetic on the argument yields NaN, and advises onRender over overriding updateTransform for per-frame work.