Animation scenes draw every part separately, costing hundreds of draw calls a frame

Open
#814 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@JamesVanBoxtel is already working on this.

Since Nov 14, 2026.

Assessment

This issue has not been assessed yet.

Description

Client-side enhancement graphics

Animation scenes, such as stage backgrounds like Esme's Terrace (#812) and the title screen, draw each part from its own image, so LÖVE can't batch them into one draw call. Esme's Terrace makes 943 draw calls a frame from 98 images, and the title screen makes 55. Most parts never move, yet each one is still transformed, coloured and blended every frame. This costs the most on phones and tablets, and it grows with every part a scene adds.

Proposed fix, done when animation data loads:

  • Pack the loader's images onto shared texture atlas pages, so draws from different images batch together.
  • Bake each run of still parts into one image drawn in the run's place, so the draw order stays the same.

It touches AnimationLoader.lua and graphics_util.lua, which the #199 UI rework also changes, so the two need to land in a coordinated order.

Dominant language
Lua
Stars
30
Forks
20
Avg merge
3d 15h
Merged PRs (30d)
17

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from panel-attack/panel-game

All issues in panel-attack/panel-game

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.