sandy23 Posted August 3 Share Posted August 3 I've been working with PixiJS for rendering animations and managing graphic elements on web canvases. Recently, I ran into a bit of a bottleneck while handling asset bundling and cache management for high-resolution graphics and media files. When users switch between different app states or mobile viewports, the asset loading causes a slight stutter before rendering smoothly on the stage. I'm currently looking into cleaner asset pre-loading strategies to keep the frame rate stable. For context, I was comparing how lightweight utility tools or mobile apps handle local asset rendering (like handling IPA packages or cached resources in setups), and I'm wondering if there's a similar optimized pipeline recommended in PixiJS for managing heavy texture caches. Quote Link to comment Share on other sites More sharing options...
CGTRocketX Posted October 22 Share Posted October 22 The state-switch stutter is usually textures arriving mid-frame, not the draw call itself. What helped us on a heavy browser canvas build: 1) Preload the next state's atlas before the transition starts, and only flip the state flag after the load promise settles. 2) Cap concurrent decode — one or two big textures at a time beats flooding the decoder. 3) Keep a small warm cache of the last state so Back does not re-fetch. On mobile viewports we also destroy off-screen textures instead of just hiding sprites; otherwise the GPU cache quietly grows across switches. Are you bundling with Pixi's Assets API, or a custom manifest? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.