You already toggled static flags and still saw batches explode. That is where a frame-time cliff starts: draw calls stay high, CPU work keeps burning cycles, and optimization becomes firefighting instead of progress.
You get the low-level truth of static batching here, including why “it should batch” can still fail, how Awake/Start timing can break results, and what Unity is really doing with shared vertex and index buffers. You also inspect real captures in Frame Debugger and RenderDoc, plus a case study that weighs static batching against GPU instancing.
Concrete next step: profile one representative scene, check batched versus non-batched events, capture a frame, and compare CPU draw-call cost against memory overhead before you change your content pipeline.
CEO/Producer translation: this avoids shipping expensive rendering habits that quietly grow into a review tax and weeks of rework.
Unlock the full Static Batching module now and get the exact decision path for when to batch, when to instance, and what to test first.
In this module:
- 1. Intro to Static Batching & Why the Hell
- 2. Static Batching Like You Never Saw (Low Level!)
- 3. Case Study: Solasta
- 4. Exercises
Join to unlock the full module, audio, and resources.