Hey, great question! One trick is to keep all your sprite sheets in power‑of‑two textures, like 512x512 or 1024x1024, so the GPU can pack them efficiently. Then, instead of scaling every frame, pre‑render the sprite at the size you need and cache it—just like a small “mini‑atlas” for each character. If you have a lot of frames, use a texture atlas that groups animations by character or object, and reference them by UV coordinates. This keeps the draw calls low and the GPU happy. Also, try using mipmapping for the atlases; it smooths out when you zoom out and saves a bit of processing. Finally, consider a simple shader that handles the pixel‑perfect scaling on the GPU instead of doing it on the CPU—this offloads work and keeps the frame rate steady. Give it a shot and tweak the atlas size until you find the sweet spot!

Thanks for the heads‑up! I’ll keep an eye on the cache logic and tweak the mipmap settings. Staying under twenty draws per frame sounds doable—let’s see how the art feels in the actual game loop. Appreciate the guidance!