AI 3D to Game-Ready: The Full Pipeline

What “game-ready” means depends on the destination

We know of no engine that publishes a universal triangle or texture figure. In the documentation we could read as of November 2026 we saw no official recommended per-asset budget for Godot, Unity or Unreal. Epic’s Nanite page, when we last read it, gave no per-mesh triangle limit and told you to measure on your own hardware; it refused our final re-check, so confirm it there. Where a platform does publish a figure, it is a hard rule worth holding your output against:

• Roblox: “Individual meshes can not exceed 20,000 triangles” (Roblox Creator Docs, modeling specifications; avatar items have their own budgets; more on AI 3D models for Roblox).
• Unity: a convex Mesh Collider is limited to 255 triangles (Unity 6.0 manual).

So the first job is to name your target (a Nanite scene, a Godot mobile build, a Roblox experience) and look up its limits. The polycount budget calculator is the place for those figures as they get collected.

Be wary of a budget quoted without a target. Vendor guides give ranges that do not agree: 3D AI Studio suggests 10k to 50k polygons for game props, StraySpark says 2K to 15K triangles for a prop depending on screen importance, and Nilo treats anything far above 30,000 triangles on a simple prop as a warning sign. All three are advice, none is a platform rule, and they cover different scopes. The role of the asset matters as much as the engine. Customuse’s point is worth keeping: decide whether the thing is a driven vehicle, a static prop or background dressing before you prompt, because that sets everything after it.

The pipeline in order

1. Import and normalize scale. Bring the GLB or FBX into Blender and check object count, dimensions and orientation. See importing AI 3D models into Blender and scale, pivot and axis fixes. Doing this first means every later number (voxel size, bake distance, collision size) is in real units.
2. Repair the shell. Remove floating pieces, merge near-duplicate vertices, fill small holes. See repairing holes, floaters and broken pieces. StraySpark, which sells a cleanup add-on, reports one Meshy robot export with 271,174 triangles, 633 separate shells and 35,842 open border edges, and says QuadriFlow “wants a closed, manifold surface with consistently oriented faces” and rejected that file. That is one file from one vendor, not a rate, but it shows why this step comes before remeshing.
3. Decide if you need to reduce at all. For static, opaque meshes in Unreal with Nanite, you may not. See do you still need retopology with Nanite and LODs.
4. Reduce and rebuild topology. Pick a method with retopology for AI 3D models, then follow the Blender retopology procedure. Keep the untouched dense mesh; step 6 needs it.
5. Fix UVs and textures. The new topology needs usable UVs, and AI textures may carry baked lighting. See UV and texture fixes.
6. Bake. Transfer detail from the dense mesh to the new one: baking normal maps from a high-poly AI mesh.
7. LODs and collision. LODs for AI-generated models and collision meshes for AI props. Do these after the final topology exists, not before.
8. Rig if needed, then import to the engine. Characters go to rigging before engine import.

Some generators can now do parts of steps 4 to 6 inside their own web apps. You trade the settings below for fewer tool changes, and we have not seen independent evidence of how the results compare. Whatever does the work, the same exit tests apply.

Exit tests for each step

A step is finished when its test passes, not when its tool stops running.

The Statistics and Face Orientation overlays are in the 3D Viewport’s Overlays popover; the Blender procedure pages give the exact menu paths.

Why each step exists for AI meshes specifically

• Reduction and retopology are separate decisions. Reducing the count is one job; getting edge loops that deform well is another. The Blender manual says automatic remeshing usually does not produce topology that deforms well, so animated characters typically need manual retopology. StraySpark says the same of its voxel and QuadriFlow paths.
• UVs. When topology changes, the old UVs no longer fit. The Blender manual says Voxel Remesh will “lose all mesh object data layers” of the original, so plan to re-unwrap and bake (its Preserve options can reproject some data, such as color attributes; see the Blender procedure page).
• Floaters are disconnected pieces. They add triangles, and StraySpark says that “hundreds of open shells” is the opposite of the closed surface QuadriFlow wants.
• Baked lighting is shading painted into the base color texture, which will not respond to your engine’s lights. We found no one-click fix in the Blender manual pages we read; see the UV and texture page for options.

What happens when the order is wrong, in three common cases:

• Texturing before retopology. Customuse reports that texturing after retopology gave its creator a better result than texturing the high-poly, because the engine runs the final mesh. That is one vendor walkthrough. The mechanical reason holds regardless: a new mesh needs new UVs, so texture work on the old surface must be transferred.
• Remeshing before saving the original. The bake then has no source. Keep a copy from step 1 onward.
• Building LODs before the bake. LODs inherit the final topology and shading, so doing them first means doing them twice.

Three routes, by target

Route choices below are our judgment from the documentation, not measured results.

A static prop in a Nanite scene. Steps 1 and 2, then import and check. Epic’s Nanite page, as last read, supports Opaque and Masked materials and lists further limits, covered on do you still need retopology with Nanite and LODs. Add collision if the prop is touched.

A static prop in Godot, Unity or a Roblox experience. Steps 1 to 7. The fixed number to hit on Roblox is 20,000 triangles per mesh. Godot’s docs say it generates mesh LODs automatically for imported 3D scenes (glTF, .blend, Collada, FBX) but not for OBJ by default, which can save step 7’s LOD half. A convex Mesh Collider in Unity has to fit 255 triangles, so plan a separate simple collision shape.

A rigged character. Every step, with manual retopology at joints and the face, UVs and bake after, and rigging before engine import. Apply scale before rigging: the Blender manual warns that applying transforms to armatures does not touch pose or animation data.

Automating the mechanical part

StraySpark’s pipeline post argues the mechanical stages (cleanup, reduction, LOD generation, export) can be scripted through Blender’s Python API, while retopology decisions, UV seam placement and material checks stay with a person. A paid route to the same idea is on Blender retopology add-ons compared. Automation does not remove the need for the exit tests above; it makes them more important, since nobody watches each asset go by.

When to stop

Stop at the first step that meets your target’s documented limits and passes a visual check in the engine. A prop that is seen at a distance in a Nanite scene may only need steps 1 and 2. A character needs the full route. The honest answer to “how long does this take” is that we have not seen independent, reliable figures for AI meshes; log your own using the method on the cleanup time page. Vendor guides do quote minutes per asset, and they vary widely, so treat them as vendor claims until you have logged a few of your own.

What is still unknown

The planned work for this page is timed end-to-end runs per generator on the standard prompt set. None has been done. Treat the sequence above as a documented workflow, not a ranked result, and expect the failure points to vary by generator and by asset.

This page is part of the Cleaning Up AI 3D Models section.