ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Mobile & games · #pixijs
PixiJS v8 offers WebGPU and WebGL backends. Here's how to choose a preference, what the real trade-offs are, and a concrete auto-detection setup with runtime validation.
PixiJS batches sprites sharing a base texture into single draw calls. Texture atlases and v8 RenderGroups let you structure scenes so the GPU draws instead of switches. A reproducible 2,000-sprite starfield shows the difference.
In PixiJS, texture switches per frame predict performance far better than sprite count. Here's how the batch renderer works, what breaks it, and a v8 atlas example that draws 500 sprites in one batch.
A practical decision guide for PixiJS renderer selection: when WebGL batching justifies the GPU dependency, when the canvas fallback is acceptable, and how to validate both with a concrete benchmark.
PixiJS performance problems are usually draw-call problems. Here's how the automatic batcher works, why texture atlases and sibling ordering matter, and how to measure the difference yourself.
Batch rendering with PixiJS ParticleContainer lets you display thousands of sprites—like snowflakes or fireflies—on mobile without dropping frame rates. Learn how to set it up, when it works best, and its trade‑offs.
Learn how PixiJS Ticker drives requestAnimationFrame, shares a global loop, and why mixing variable deltaTime with fixed timesteps can keep your game logic deterministic.
Learn how PixiJS ParticleContainer batches thousands of sprites sharing a texture into a single draw call, cutting CPU overhead for effects like rain or snow.
Learn how PixiJS’ shared Ticker supplies a delta time for frame‑rate independent updates, with a code example, limits, and common pitfalls.
webgpu
javascript