Game asset pipeline
Recipes on top of the tripo-3d skill. Read that skill first — it explains how
to pick the execution path (MCP tools vs tripo-cli), authorization, blocking
behaviour, exit codes, and credit rules.
The recipes below are written as CLI commands because game work happens in a
project tree where a shell exists and assets should land next to the code.
The same pipelines map onto the MCP tools when the user prefers them:
tripo_text_to_3d/tripo_image_to_3d with face_limit for budgeted props,
tripo_rig (spec: "mixamo") + tripo_animate for characters (humanoid rigs
take preset:biped:* clips, creature rigs the plain preset:walk family — the
tripo_rig result says which), tripo_convert
for FBX/texture-size export, tripo_decimate per LOD level, and
tripo_upload_ticket → tripo_import_model for a mesh the project already has —
then download the fresh result URL into the project. Only tripo batch (bulk,
resumable) genuinely requires the CLI; say so instead of improvising.
The point of these recipes is that assets land in the project's own directory
structure. Always pass -o pointing at wherever the project keeps its art — but note
-o is the parent: the files end up in <dir>/tripo-out/<name>-<id8>/, so move them
to their final location afterwards if the user named a specific path.
Pick a budget first
| target | preset | what it does |
|---|---|---|
| mobile, WebGL, many instances | --for game-mobile |
P1 low-poly model, face_limit 15000, 2K textures, FBX |
| PC / console hero asset | --for game-pc |
v3.1, detailed PBR |
| animated character | --for anim |
rig-check, then rig, then retarget |
Two budget-related choices the presets do not make for you:
- Quads at low poly — P1 rejects
quad; use--model tripo-p2(wireP2-20260801, Preview; face_limit 48–25000 quads, ~5× the P1 price, output is FBX) or v3.1 with-p smart_low_poly=true -p quad=true(face_limit 500–10000). On MCP passmodel: "P2"/quad: true. - v3.1 quality under a face cap — any
face_limit≤ 20000 auto-selects P1, so add--model tripo-v3.1(MCPmodel: "v3.1") when the user wants v3.1 geometry with a budget.
Override the face budget when the project has a stricter one:
tripo make "a health potion bottle" --for game-mobile \
-p face_limit=3000 --then convert:format=FBX,texture_size=1024 \
-o ./Assets/Art/Props --json --yes
Props
tripo make "an ornate treasure chest, fantasy style" --for game-pc \
-o ./assets/models --json --yes
For a set of props, generate them one at a time and check each preview.png before
continuing — a bad seed early is cheaper to catch than at the end of a batch. For
genuinely large sets use tripo batch run manifest.yaml, which is resumable.
LOD chain from one source
tripo make "a stone golem" --for game-pc --then decimate:5000 --json --yes
tripo make @last --then decimate:1500,convert:fbx --json --yes
decimate bakes normals by default, so the low LODs keep the silhouette detail of
the source. Each @last continues from the previous task rather than regenerating.
decimate's face budget is a target, not a ceiling — a 1500-face request can come
back at ~1900 triangles. Read the actual triangle count from the result before handing
an LOD to a project with a hard budget, and reduce it locally if it overshoots.
Generation's own face_limit does hold as an upper bound, so this caveat is specific
to decimate.
Characters with animation
tripo make "a knight in full armor, T-pose, standing straight" --for anim --json --yes
--for anim runs rig-check first, which gates the chain: if the mesh is not
riggable it stops before spending rigging credits.
Explicit control over the rig and clips:
tripo make "a robot soldier, T-pose" --json --yes \
| tripo anim check --json \
| tripo anim rig --spec mixamo --out-format fbx --json \
| tripo anim retarget --animation preset:idle preset:walk preset:run --json
- Prompt for a T-pose — rigging quality depends heavily on it.
--spec mixamoproduces a Unity Humanoid-compatible skeleton.--animate-in-placefor locomotion clips driven by game code rather than root motion.- Retarget is billed per animation and accepts at most five.
- To animate a mesh the project already has:
tripo make hero.glb --then rig-check,rig,retarget:preset:walk --json --yes
Format notes
- Three.js / web: GLB.
--for ar-webadds the web-oriented defaults. - Unity / Unreal: FBX via
--then convert:fbx, or--for game-mobilewhich already converts. - Quads (
-p quad=true) force FBX — glTF cannot store them, soconvert:glbcombined with quads is rejected. texture_sizeis set on the convert step, not at generation:--then convert:format=FBX,texture_size=2048.
Wiring into the project
After a successful run, model_file in the result JSON is the path to import. Do the
integration work the user actually asked for — add the loader call, register the
prefab, update the asset manifest — rather than stopping at "the file is generated".
Check preview.png first so a wrong asset does not get wired in.