- name
- blender-game-optimization
- description
- Optimize Blender assets for real-time engines - triangle/material/texture/bone budgets per platform (mobile, Roblox, web, VR, console, PC), LOD chains, decimation modes, mesh cleanup, draw-call reduction (material merging, atlases, trim sheets), instancing, vertex-split costs, collision proxies, texture memory. Use when an asset is too heavy, before export, or when targeting a platform budget.
- license
- MIT
- metadata
- author: blender-agent-skills version: "1.2.0"
Game Optimization
The execution model is in blender-core. Always re-run blender-asset-qa after optimizing.
Procedure
- Measure:
scripts/mesh_stats.py -- --objects ... --budget mobile|roblox|web|vr|console|pc. It returns tris, estimated draw calls, materials, texture VRAM, bones, and the over-budget items. - Clean:
make_lods.py --cleanup(merge by distance 0.1 mm, dissolve degenerate, delete loose). Remove hidden faces: back-to-back faces and faces under other parts (qa_check→back_to_back, plus manual xray). - Reduce in this order (cheapest visual loss first): hidden/interior geometry → unnecessary edge loops on flat areas (Limited Dissolve 1–5°) → over-segmented cylinders → Decimate → bake detail to normals (
blender-texture-baking). - Materials: merge to 1–2 per asset (atlas / trim sheet / shared tiling material). Each material slot per mesh is roughly one draw call.
- LODs:
scripts/make_lods.py -- --objects SM_X --renamecreates_LOD1.._LOD3at 50/25/12.5%. Check every LOD silhouette withlook/review_shots. - Re-measure, then QA, then export (
blender-export-pipelines).