Quick answer: Share a single material across combined meshes, mark objects static for static batching, and respect vertex and material limits so batching actually reduces calls.
Batching not reducing draw calls is usually multiple materials or unmarked objects. Here is how to fix it.
How to fix it
1. Share one material
Batching combines objects that share a material into one draw call. Combined geometry with multiple materials still issues a call per material. Use a shared material (and atlas textures) so it batches into one.
2. Mark objects static
Static batching only applies to objects marked static. If they are not flagged, they are not batched. Mark non-moving objects static so the system can combine them at build or load time.
3. Respect batch limits
Static batching has vertex limits per batch, and dynamic batching only works for small meshes. Exceeding the limits silently falls back to separate calls. Keep within them, or use GPU instancing for large counts.
Catching the ones you can't reproduce
The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.
Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.
This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.
Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.