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.
Goal: Verify that assigning the crossorigin option to PIXI.Loader for an image hosted on a different origin results in a texture that can be safely used in a WebGL context without being marked as origin‑tainted. Constraints: The Loader forwards the option to the underlying HTMLImageElement , but browser implementations of CORS vary, and some servers may not
PixiJS ResourceLoader fallback handling after a failed upgrade When upgrading a PixiJS‑based project from 6.x to 7.x, the ResourceLoader may emit an error event for assets that fail to load. The library offers no built‑in retry or optional‑asset flag, so developers must decide how to treat these failures during the upgrade process. Additionally, the Applicat
Goal Gracefully cancel or timeout an ongoing resource load in PixiJS when the application needs to abort a request or the request takes too long. Current State PixiJS Loader uses fetch or XMLHttpRequest internally. The Loader does not expose a timeout or abort interface; its destroy method only frees GPU memory and does not terminate the network request. Whe
I'm designing a save/restore flow for a PixiJS application where the current scene graph is serialized to JSON, the app is torn down, and the scene is later reconstructed. The goal is a restoration that is visually and behaviorally identical to the saved state, including z-order of children and animation progress. The constraints I'm working under: assets ar
Goal: Gracefully Cancel Asset Loads PixiJS Loader is used to fetch textures and other assets in a web application. The current public API does not expose an abort method; developers must manually cancel the underlying XHR or Fetch request. When an asset load is aborted, the Loader’s onError callback is not invoked, leading to silent failures that are hard to
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