Tripo generates 12 textured game assets in 30 minutes for Amir Mushich
Amir Mushich says Tripo generated 12 textured models for a game level in 30 minutes. He used Blender for layout, collisions and animation before shipping a browser-shooter level.

TL;DR
- A 30-minute Tripo run produced 12 textured models for a browser-shooter level, according to AmirMushich’s demo. He assembled the level in Blender afterward.
- The models already included UVs and PBR textures, as he explained in a technical follow-up.
- The agent’s workflow stays visible and editable, a feature egeberkina highlighted while describing their limited 3D experience.
Crates, barrels and tyres initially arrived as one fused mesh, which Mushich says another prompt split into separate props. The playable result is Tidefall, with a Salvage Harbour level. Tripo also lets users clone shared workflows and replace their inputs for another run.
The 12-model asset kit
Mushich described three stages inside Tripo Agentic Canvas:
- Generate the scene concept.
- Break it down into individual assets.
- Produce 12 textured 3D models.
He clarified that an image sits between the initial prompt and the models in a reply. The reported 30 minutes covers the prompt-to-asset-kit run; the Blender assembly and browser-game deployment are subsequent steps in his account.
UVs, PBR and separate props
Mushich supplied refreshingly concrete output specifications in his follow-up:
- Geometry: 18,000 to 23,000 triangles per model.
- UVs: already present in the generated output.
- Materials: PBR, or physically based rendering, textures already included.
The fused crates, barrels and tyres needed a correction inside Tripo. Mushich says he asked the agent to split them into separate props, keeping that repair out of Blender.
Blender level design
Mushich handled five production tasks in Blender:
- Scaling the assets.
- Placing them in the level.
- Setting up colliders.
- Positioning enemy spawns.
- Animating the crane hook, radar dish and trawler.
Those responsibilities come from the same technical follow-up, which specifies where the generated assets ended and his level-design work began. He also said in a reply that the game’s AI was too strong and needed balancing.
Control and Auto modes
For egeberkina, who said they knew almost nothing about topology, UVs or rigging, the appeal was having the agent plan the workflow while leaving its steps available to inspect and change.
Tripo documents two execution modes in its Canvas guide:
- Control: the agent pauses at review checkpoints for input.
- Auto: the agent works through the confirmed plan.
New projects start in Control, including projects created from templates or shared workflows. Switching modes during a run takes effect after that run finishes.
Changing an upstream input also requires rerunning the downstream step to produce a new result. The canvas preserves the connections, but changing an input alone does not regenerate its dependents.
Canvas access and asset visibility
Canvas access is rolling out by account inside Tripo Studio, according to Tripo’s guide. Export availability and limits depend on the Studio plan.
Planning costs no credits; charges begin when generation starts, according to Tripo’s billing page. Most nodes match the credit costs of their equivalent Studio tools, with the amount displayed before execution; AI 3D Lab charges vary by task.
Both AmirMushich and egeberkina included signup-credit and first-month-discount promotions in their posts.
The guide also specifies separate visibility rules for saved assets:
- Free accounts: newly saved assets default to Public and are published to Gallery.
- Paid accounts: newly saved assets default to Sharing only.
- Projects: new projects default to Only you, but project privacy does not override asset visibility.
- Published assets: an asset already published to Gallery cannot subsequently be made private or unlisted.