pixijs-core-concepts

PixiJS v8 uses autoDetectRenderer to evaluate environment capabilities and select the optimal backend, defaulting to WebGL or WebGPU when available and falling back to Canvas. This selection process ensures compatibility across various browser contexts.

The PixiJS render loop integrates with the ticker to execute a per-frame pipeline that handles transform traversal and renders frames. This loop continuously processes scene graph updates and issues draw commands to the selected backend renderer.

PixiJS v8 adapts to different contexts like web workers and SSR using environment adapters. These adapters abstract environment-specific logic, allowing the renderer system to function correctly outside standard browser windows.

Renderer systems in PixiJS v8 manage high-level renderer state and lifecycle, while pipes handle specific stages of the rendering pipeline. This architecture modularizes the per-frame work into distinct processing steps.

Creating a PixiJS Application automatically initializes the renderer via autoDetectRenderer and starts the ticker-driven render loop. You can observe and configure backend selection and per-frame pipeline behavior through the application's renderer instance.

PixiJS v8 falls back to Canvas or WebGL when WebGPU is unavailable in the current environment. The autoDetectRenderer logic checks for specific backend support and environment capabilities before making its selection.