ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Mobile & games · #pixijs
Learn how to optimize GPU memory in PixiJS by decoupling BaseTextures from Textures to prevent redundant VRAM uploads and memory leaks.
PixiJS already runs one requestAnimationFrame loop. Register your update logic on its Ticker, drive motion from elapsed time, and know where delta-time stops being enough.
Learn how to use PixiJS TilingSprite to create high-performance, seamless scrolling backgrounds by leveraging UV mapping instead of duplicating sprite objects.
Background PixiJS 7 dropped the automatic canvas size adjustment that matched the browser viewport. Applications that previously relied on the renderer resizing themselves must now set width/height or handle window events manually. Current Constraints Legacy code written for PixiJS 6 will break if the canvas is not explicitly resized. There is no built‑in fl
When initializing PixiJS in a browser that lacks WebGL support, the library throws the error pixi.js: WebGL not supported and logs it to the console immediately. In production builds this message is useful, but in development environments it can flood the console, making it hard to spot genuine runtime problems such as missing assets or internal API misuse.
Ticker Timing and Tab Visibility The PixiJS Ticker utilizes requestAnimationFrame to manage the update loop, calculating a delta value to ensure frame-rate independent movement. This mechanism relies on the browser's high-resolution timestamp to maintain synchronization between logic updates and rendering. A specific challenge arises when the browser tab is