blender-asset-validation

Blender Asset Validation

Read the shared execution guidance once per task for autonomous decisions, evidence cadence, and long-task continuity.

Validate the supplied asset and any requested exported deliverable. Do not create an export for an inspection-only or render-only task. A clean export or low triangle count is not proof of visual or functional quality.

Run deterministic inspection

Prefer the blender_inspect_asset MCP tool when available. Otherwise run:

$env:BLENDER_EXECUTABLE = "C:\path\to\Blender\blender.exe"
& $env:BLENDER_EXECUTABLE `
  --background --factory-startup `
  --python "<skill-root>\scripts\inspect_asset.py" -- `
  --input "<asset-path>" --output "<output-dir>\metrics.json"

Inspect:

• evaluated vertices, edges, polygons, and triangles;
• authored versus evaluated geometry density and refinement modifiers;
• smooth versus flat-shaded polygon ratios;
• UV-bearing meshes, node-based materials, image textures, and authored lights;
• mesh objects, materials, actions, frame ranges, and hierarchy;
• dimensions and world bounds;
• invalid coordinates, degenerate faces, loose elements, boundary and non-manifold edges;
• connected components per mesh;
• non-default transforms and missing material assignments.

Interpret metrics using references/quality-gates.md. Do not apply printing-only topology rules to every game asset.

When inspection finds degenerate faces or zero-length edges, call blender_diagnose_topology with assetPath, a new outputJson, and optionally objectName and limit. It reports full counts and bounded world-space locations. Indices belong to evaluated geometry: locate the region, repair durable source, and reinspect the export. Open boundaries alone are not defects.

Understand the scene before diagnosing a repair

When the Rust runtime is configured, use blender_describe_scene for evaluated world bounds, authored bas_role labels, parenting and paginated object summaries. Focus with an exact objectId and includeDescendants; follow next_offset for large selections. An assembly follows object parenting, not collection names.