- name
SKILL.md
स्किल फ़ाइल पब्लिशर की रिपॉज़िटरी में ही रहती है।
कॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add scenario-labs/skills --skill scenario-blender-export -a cursor -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add scenario-labs/skills --skill scenario-blender-export -a claude-code -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add scenario-labs/skills --skill scenario-blender-export -a codex -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add scenario-labs/skills --skill scenario-blender-export -a grok -yकॉपी किया गया संदेश Grok Bot चैट में भेजें। Bot यह SKILL.md GitHub से लाता है और उसे उन स्किल में जोड़ देता है जो आपके सभी Bot साझा करते हैं।
Install this skill: https://github.com/scenario-labs/skills/tree/HEAD/skills/dcc/blender/scenario-blender-exportपब्लिशर से
An export is done when the file has been re-imported and measured, not when the exporter returned
FINISHED. Gate the asset first, export with a preset, then round-trip the file. This skill builds
on scenario-blender-expert (execution channels, the delivery gate) and imports its scripts, so
install the two side by side. If a sibling skill named here is missing from your available skills,
load it with skill_get (Scenario MCP) or ask the user to install it
(https://github.com/scenario-labs/skills#install); unattended, proceed from tool schemas and flag
the gap.
Toolkit: scripts/bx_export.py. Per-engine facts with their sources:
references/engines.md.
The Unity and Godot presets were imported into Unity 6000.3 and Godot 4.7.2 and measured; unreal,
unreal_skeletal and roblox follow Epic's and Roblox's documentation and pass the Blender round
trip only. The measurements live in references/engines.md.
bx_audit.deliverable(parts, profile) from scenario-blender-expert and fix every
error. Scale left on an object travels into the engine as the node's transform.
scenario-blender-retopology, bake the original's maps onto it, then
gate again.roblox requires watertight
meshes). Never deliver it as ready.bxe.ground(parts, width=0.9) (or height=, in meters) bakes the
transforms, puts the center of the base at the origin and scales to the real size. Ask for the
size when the brief does not give it; unattended, pick a plausible one and state it as an
assumption. Static meshes only.bxe.export(path, preset, objects, **overrides). Any exporter keyword overrides the
preset, such as bake_anim=True on roblox for an animated file. The result records the
settings used.
web then writes an uncompressed GLB,
which loads without MeshoptDecoder, and lists the option in skipped_settings. Report it to
the user. Any other setting the exporter lacks raises.bxe.round_trip(path, objects, preset=...) re-imports the file in a background
Blender, leaving the open scene alone. It compares size (1 mm), triangles, deforming bones, root
bones (one expected), armature scale, shape keys, every action stored for the objects, and the
image maps on each material (base color, metallic, roughness, normal, emission). Then it lists
every difference. Fix each one, or say why it is expected.bxe.glb_summary(path) lists extensions_required, morph targets, skins,
clips and image types without Blender. A loader refuses a file that requires an extension it
lacks.export_yup). FBX stores its axes as metadata; the presets write -Z forward, Y up.scene.unit_settings.scale_length at 1.0. Any other value rescales every export.obj.data.transform(Matrix.Diagonal(obj.scale).to_4x4()), then
obj.scale = (1, 1, 1), so the engine node imports at scale 1. bxe.ground() does it for every
mesh at once.unity writes FBX_SCALE_ALL (Unity reads file scale 1). unreal keeps
FBX_SCALE_NONE (Unity reads it as file scale 0.01, a centimeter file). roblox uses
FBX_SCALE_UNITS, as Roblox's export requirements ask.print multiplies by 1000.use_armature_deform_only leaves control bones out, so keep
every deforming bone in one hierarchy under one root bone. Unreal's importer reports "Found
multiple roots. The importer only supports one root per mesh."add_leaf_bones is off in every preset. Left on, each chain gains an extra end bone that breaks
retargeting.unity_skeletal and unreal_skeletal bake every action (bake_anim_use_all_actions), one clip
per action. Unity names each clip Armature|Action (measured: Rig|Wave), so name actions as the
clips should read. glTF exports each action as an animation under its own name.roblox exports no animation. For an animated file, pass bake_anim=True to export() and to
round_trip(), which then compares the actions too.extras.targetNames) and
USD. Building ARKit or viseme sets is scenario-blender-rigging's work.max(len(v.groups) for v in obj.data.vertices).bxe.lods(obj, ratios=(0.5, 0.25)) renames the mesh Name_LOD0 and adds decimated Name_LOD1..n
under an empty called Name, which takes the mesh's place under its parent. Static meshes only:
it refuses a skinned mesh. Unity builds the LOD Group from those names. Godot generates LODs at
import (Generate LODs). Unreal documents "Import LODs", all LODs sharing one pivot. The group
exports as a plain FBX Null, and Unreal's import of it is unmeasured. It welds the vertices a glTF
import splits at UV seams before decimating; without the weld, the LODs open into cracks.bxe.collision(obj, engine, shape, max_verts=64) adds a collision mesh named for the importer:
UCX_Name_00 (convex hull) or UBX_Name_00 (box), exported in the same FBX. Unreal
skips Auto Generate Collision when the file carries one.Name-convcolonly for convex (one hull) and box (the bounds, a box collider), or
Name-colonly for mesh (the mesh as a trimesh, static bodies only).max_verts vertices, spread over the shape. A generated mesh's full
hull runs to thousands of faces. 64 is this toolkit's budget, not an engine limit. None keeps
every vertex, and a dense full hull can come out with open edges.bx_review before export.blender -b --factory-startup --python-exit-code 1 -P bx_export.py -- \
--batch /abs/in /abs/out --preset godot --profile game
For every model in the folder (GLB, glTF, FBX, OBJ, USD, STL, PLY): import into an empty scene, run
the delivery gate, export with the preset, re-import and compare. It writes /abs/out/report.json
with each file's gate errors, size, skipped settings and round-trip differences. One failing file
never stops the folder: it gets a failed entry. Two inputs sharing a name keep their format in the
output name (hero_fbx.glb, hero_glb.glb). Open the report before calling the batch done.
import sys
sys.path.append("/abs/skills/scenario-blender-expert/scripts")
sys.path.append("/abs/skills/scenario-blender-export/scripts")
import bpy, bx_audit, bx_export as bxe
bpy.ops.wm.read_factory_settings(use_empty=True)
bpy.ops.import_scene.gltf(filepath="/abs/in/robot.glb")
parts = [o.name for o in bpy.context.scene.objects if o.type == "MESH"]
gate = bx_audit.deliverable(parts, profile="game")
print(gate["errors"]) # fix each one, then gate again until "pass" is True
bxe.ground(parts, height=1.2) # the robot's real height in meters, base center at the origin
bxe.export("/abs/out/robot.fbx", "unity", parts)
print(bxe.round_trip("/abs/out/robot.fbx", parts, preset="unity")["diffs"])
# ["Robot: material Body lost its Metallic, Roughness maps"]: write them for the engine
print(bxe.extra_maps(parts, "/abs/out", "unity")["written"])
bxe.export("/abs/out/robot.glb", "godot", parts)
print(bxe.glb_summary("/abs/out/robot.glb")["extensions_required"]) # []
A generated GLB often holds one object per part, all sharing the asset's pivot. Keep them as
separate objects when the engine should animate or swap parts. Join them (bpy.ops.object.join with
the parts selected) for a single static prop, then gate again.
FINISHED. The exporter succeeds on files the engine imports at 100x
scale or without the skin.web preset for Godot, or any compressed GLB for a loader without its decoder. Check
extensions_required first.path_mode="COPY",
embed_textures=True), so the file travels alone. export() gives packed images without an
extension (as a GLB import leaves them) a .jpg or .png name first. An image never saved (a new
bake target) or edited since travels as a packed copy of its pixels (packed_unsaved_images).round_trip() reports
the loss. bxe.extra_maps(parts, out_dir, engine) writes the two maps as files to assign:
<material>_MetallicSmoothness.png in the Metallic Map slot (Standard or URP Lit),
Smoothness Source on Metallic Alpha, sRGB unchecked. Unity's FBX import assigned only the base
color, even from a file carrying both maps (measured).<material>_Metallic.png and <material>_Roughness.png, 8-bit grayscale. On
Roblox, set them as MetalnessMap and RoughnessMap of a SurfaceAppearance. In Unreal, uncheck
sRGB on both.godot GLB, which keeps every map.Use when exporting a model, character or animation from Blender to a game engine, the web or a 3D printer: FBX, glTF/GLB, USD/USDZ or STL for Unity, Unreal Engine, Godot, Roblox, three.js or Apple AR
---name: scenario-blender-exportdescription: Use when exporting a model, character or animation from Blender to a game engine, the web or a 3D printer…---# skills/dcc/blender/scenario-blender-export/SKILL.mdओवरव्यू
Use when exporting a model, character or animation from Blender to a game engine, the web or a 3D printer: FBX, glTF/GLB, USD/USDZ or STL for Unity, Unreal Engine, Godot, Roblox, three.js or Apple AR Quick Look. Also when an export arrives at the wrong scale (100x, 0.01), rotated 90 degrees, facing backwards, with extra leaf bones, without its animation, blend shapes or textures; when an FBX loses its metallic or roughness map; when a generated model needs its real size and its pivot on the floor; when making LODs or collision meshes (UCX_, -colonly) for an engine; when converting a folder of models in batch; or when checking an exported file by re-importing it.
FAQ
पब्लिशर से skills/dcc/blender/scenario-blender-export/SKILL.md डाउनलोड करें, या पाथ कॉपी करके रिपॉज़िटरी खोलें। PlugMCP स्किल को सूचीबद्ध करता है, फ़ाइल होस्ट नहीं करता।
पब्लिशर इसे https://github.com/scenario-labs/skills पर रखता है।
Claude, Cursor, Codex और Grok Build वह SKILL.md पढ़ सकते हैं जिसे आप पब्लिशर की रिपॉज़िटरी से जोड़ते हैं। जब आप चैट में स्किल के GitHub फ़ोल्डर का लिंक भेजते हैं, तो Grok Bot उसे इंस्टॉल कर देता है।
scenario-unity-pipeline-automationscenario-unreal-pipeline-automationscenario-godot-pipeline-automation