pixijs-core-concepts

PixiJS v8 uses automatic backend selection during Application.init to choose WebGPU, WebGL, or Canvas. You can check app.renderer.name after async init to determine the active renderer and apply feature branching based on the selected backend.

Control the PixiJS render loop by using the Ticker priority model and ticker.deltaTime or deltaMS for frame-independent updates. You can debug render timing by understanding where app.render() fits into the per-frame execution order.

Yes, you can disable automatic rendering in PixiJS by setting autoStart to false and calling app.renderer.render() manually. This allows precise control over the render loop execution order and per-object onRender hooks.

PixiJS supports adapting behavior across DOMAdapter, WebWorker, and SSR contexts using environment adapters. These adapters modify rendering behavior to ensure compatibility across different execution environments outside the standard DOM.

Renderer systems run once per renderer lifecycle in PixiJS, while render pipes execute every frame to convert renderables into GPU work. This architecture separates initialization logic from the per-frame execution pipeline.