Skip to content
BLBlender

Drawcallanalyzer

by Skava·Workflow

Images © Skava. Used for product review; image policy.

Why we like it

DrawCallAnalyzer earns its place in the superhive library by moving draw-call and VRAM feedback to the start of the pipeline — you see the breakdown against a platform budget inside Blender, with the exact saving each suggestion produces, rather than after exporting to an engine.

What is Drawcallanalyzer?

DrawCallAnalyzer is a Blender addon from Skava that inspects a scene the way a game engine would and reports where the cost lands before you export. You pick a target platform — Desktop, Mobile, or Console — and each loads a realistic draw-call and VRAM budget, then clicking Analyze walks every mesh, material slot, texture, and mesh duplicate in the scene.

The breakdown appears in the sidebar: draw calls counted per material, texture memory sized with platform-specific compression formats, static and dynamic batching candidates, GPU instancing groups, and an overdraw heatmap — each compared against your budget and flagged when you go over. Every suggestion, from merging materials to instancing duplicates to downscaling a 4K texture, comes with the exact saving it produces.

A single button exports a full optimization report as CSV or JSON, and snapshot diffs let you save the scene's metrics, optimize, then compare the numbers. Documentation is available.

Who is Drawcallanalyzer best for?

Drawcallanalyzer is best for game and technical artists who need to hit performance budgets before handing off to engineering, indie developers who can't profile after every export, and environment artists on open-world or mobile projects where every draw call matters.

How much does Drawcallanalyzer cost?

Drawcallanalyzer is completely free to download and use.

Key features

  • Draw call estimation per material: every material slot counts as one draw call, totaled, broken down per material, and compared against your platform budget
  • Static and dynamic batching analysis: identifies static candidates (same material, combined vertex count under 64K) and dynamic candidates (same material, each object under 300 vertices), showing draw calls each would save
  • Mergeable materials detection: flags materials with the same shader type and matching texture counts as texture-atlas merge candidates
  • Texture memory per platform: sizes each image texture using platform compression formats with 33% mipmap overhead included, flagging 4K+ textures with downscale recommendations
  • GPU instancing detection: identifies objects sharing mesh data, calculates draw calls instancing would eliminate, and can tag each group with a custom property for export pipeline integration
  • Overdraw visualization: evaluates bounding box overlap from the active camera and color-codes objects green, yellow, or red in the viewport
  • Optimization report and snapshot diff: exports draw calls, texture memory, instancing groups, batching opportunities, and numbered suggestions as CSV or JSON, with metric snapshots to compare before and after

Tags

#Blender#game optimization#draw calls#performance#texture memory#batching#instancing

Frequently asked questions

Which platforms does DrawCallAnalyzer target?

DrawCallAnalyzer lets you pick Desktop, Mobile, or Console, and each option loads a realistic draw-call and VRAM budget. Texture memory is then sized using compression formats that match the target: DXT1, DXT5, and BC7 for Desktop; ASTC 4x4, ASTC 6x6, ETC2 RGB, and ETC2 RGBA for Mobile; and BC7, BC5, and BC1 for Console. Mipmap overhead of 33% is included automatically, and large textures at 4K and above are flagged with specific downscale recommendations so you can bring memory back under the platform budget.

How does DrawCallAnalyzer count draw calls?

DrawCallAnalyzer treats every material slot on every object as one draw call. When you click Analyze, it walks each mesh, material slot, texture, and mesh duplicate in the scene, totals the draw calls, breaks them down per material, and compares the result against your chosen platform budget. It then identifies static batching candidates that share a material with a combined vertex count under 64K, and dynamic batching candidates that share a material where each object stays under 300 vertices, showing how many draw calls each technique would save.

Can I export DrawCallAnalyzer's results?

DrawCallAnalyzer generates a report from a single button covering draw calls, texture memory, instancing groups, batching opportunities, and numbered optimization suggestions. You can export it as CSV or JSON to share with your team, paste into a task tracker, or diff against a later snapshot. It also supports snapshot diffs directly: save a snapshot of the scene's metrics, optimize, then compare to see how the numbers changed. For GPU instancing groups, it can tag each group with a custom property for export pipeline integration.

How does DrawCallAnalyzer show overdraw?

DrawCallAnalyzer evaluates bounding box overlap from the active camera, or in 3D if no camera exists. Objects are color-coded directly in the viewport — green for low, yellow for medium, and red for high — so you can spot problem areas at a glance. Alongside the overdraw heatmap, the sidebar shows draw calls, texture memory, and batching and instancing opportunities, each compared against your budget and flagged when you go over. Documentation is available for more detail.

Is DrawCallAnalyzer free?

DrawCallAnalyzer is listed as free in this catalog. Licensing terms can change, so check the developer's page from Skava for the current details before you rely on it for a project. The addon runs its analysis inside Blender, walking your scene's meshes, material slots, textures, and duplicates, so you can review draw calls, texture memory, batching, instancing, and overdraw without leaving Blender or round-tripping to a game engine.

Similar plugins