About reduce-draw-calls
A graphics optimization skill that guides developers through measuring and reducing draw calls, using batching or hardware instancing where appropriate. It also recommends pixel verification to check that the rendered image remains unchanged.
Key features
- 01Measure draw-call counts
- 02Disable hidden elements
- 03Group geometry with BatchManager
- 04Use hardware instancing
- 05Check rendering with pixel verification
Use cases
- 01Diagnosing draw-call bottlenecks
- 02Batching static or dynamic geometry
- 03Rendering many copies of one mesh
- 04Validating visual output after optimization
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ playcanvas/ skills --skill reduce-draw-callsAfter installing, type/reduce-draw-callsin Claude Code to confirm it loaded.
Details
From the project READMECut draw calls
Measure first with app.stats.drawCallCount or MiniStats; the per-pass app.stats.drawCalls
breakdown fills only in profiler builds. Also halve the pixel ratio and call app.resizeCanvas():
if frame time drops, the cost is fill rate, not draw calls. Stop at the first rung that meets the
budget and report before-and-after counts.
1. Stop drawing hidden things
An element at opacity 0 still draws. Set enabled = false.
2. BatchManager
Call app.batcher.addGroup(name, dynamic, maxAabbSize), then set batchGroupId on render, sprite,
or element components. Use dynamic: false for geometry that never moves. Members join when
enabled in the live tree, in any order, and groups regenerate automatically when membership
changes. Call markGroupDirty(id) only after moving members of a static group. Manual AppOptions
bootstraps must set batchManager.
3. Hardware instancing
Use this for many copies of one mesh and material with per-frame transforms. Build a buffer with
VertexFormat.getDefaultInstancingFormat(device), one mat4 per instance, and call
meshInstance.setInstancing(vb); instancingCount follows the buffer.
There is no per-instance culling. By default the group always draws; setInstancing(vb, true)
culls it as one unit against a RenderComponent#customAabb covering every instance. Split large
instance sets into spatial chunks. Custom vertex chunks need the INSTANCING path
(override-shader-chunks). Start from the graphics/instancing-basic and
graphics/instancing-custom examples.
Confirm the image is unchanged with verify-pixels.