Why AI 3D models fail in the slicer, and how to fix them

Meshy's documentation was checked on 7 November 2026. The before-and-after numbers come from our own test files, described in the text.

A model from Meshy, Tripo, Rodin or Hunyuan3D often fails in the slicer because it is a surface that looks right, not a solid: parts overlap and pass through each other, a few triangles are missing, some face inward. A slicer needs one closed surface in which every edge joins exactly two faces. You can fix that with the generator's own repair, with a mesh editor, or by uploading the GLB, OBJ or STL to make the AI model printable, which rebuilds it as one watertight shell and shows a before-and-after report.

What a slicer actually needs

A slicer cuts the model into horizontal layers and, in every layer, has to decide what is inside the part and what is outside. That decision is only unambiguous for a closed, manifold surface: no gaps, each edge shared by exactly two triangles, all triangles facing outward, and no part of the surface passing through another. Meshy's own printability check looks for exactly these problems: whether the surface is fully closed, non-manifold edges (edges shared by more than two faces), holes and degenerate faces with no area.

When a file breaks those rules, slicers react differently. Some report hundreds of errors and repair what they can, some silently drop a shell, some print a wall that is not there in the model. The error list itself is explained in what slicer STL errors mean.

Why generated models break the rules

Image-to-3D and text-to-3D generators are built to produce something that looks right from every side in a viewer. A viewer does not care whether a sword and the hand that holds it are one solid or two shapes stuck through each other, or whether a strand of hair is a closed tube or a single sheet. A printer cares about all of it. The typical problems, in the order we see them most often:

• Overlapping shells. A head, a hat and an ear are separate closed pieces pushed into each other. Each is fine; together they cross.
• Holes and open edges, often where two pieces meet or at thin details.
• Faces that point inward, so a slicer reads part of the model as empty space.
• Floating specks: tiny disconnected pieces left over from the generation.
• Scale. Generators export in their own units. Meshy, for example, asks for the printed height and uses centimetres by default; a model exported without it is often one or two units tall.

Three ways to fix it

The generator's own repair. Meshy offers a free printability check and a repair that costs 10 credits; for models Meshy generated it needs a paid plan. It is the quickest route if you are already a subscriber.

A mesh editor. Blender's 3D-Print Toolbox, Meshmixer and similar programs can merge overlapping parts with boolean unions and close holes by hand. It works and gives full control, but it takes time per model and a boolean union of dozens of intersecting pieces often fails or leaves new errors.

Rebuilding the surface. Instead of patching triangles, a rebuild works out what is inside the model and wraps a new, closed surface around it. Overlaps disappear because the inside of two overlapping parts is simply one region. That is how our tool works: it decides inside and outside by counting how rays from three directions cross the surface, builds a new surface on a fine grid, and snaps it back onto your original wherever the two match, so the detail is kept.

Which file to export from the generator

Export the most detailed version the generator offers, as STL, OBJ or GLB. The rebuild keeps detail down to its grid step and simplifies the result at the end, so starting from a version that was already reduced throws away detail you cannot get back. Textures do not matter for printing; a file without them is smaller and uploads faster.

One catch with GLB: some exporters compress the geometry with Draco or meshopt. Those files look normal in a viewer but need a decoder to read, and our tool asks you to export again without compression, or as OBJ, rather than guess.

What a rebuild changes: a test case

To see what happens on a deliberately broken file, we made a test model that has the typical problems: two overlapping spheres, 8 percent of the faces flipped, 40 faces deleted and 30 tiny floating specks, then exported it as a GLB 1.2 units tall, the way a generator would.

The volume of the result matched the exact union of the two spheres to within half a percent, and the specks were removed. On real scans with overlapping parts the same holds: one closed part comes out, and the average change from the original surface is a few thousandths of a millimetre, because most of the new surface is snapped back onto the old one.

What a rebuild cannot do

• Keep detail finer than the grid. A hair-thin sword tip or a strand thinner than one grid step can thicken or close up. A finer setting helps, at the cost of time.
• Keep colours and textures. STL carries only geometry. Keep the GLB for rendering and use the STL for printing.
• Decide what you meant. If two parts touch at a single point or edge, a rebuild joins or separates them by its own rule.

After the rebuild

1. Set the size. The file format has no units, as the STL specification itself notes, and slicers read the numbers as millimetres; if the model arrives tiny, see why an STL imports at the wrong size or resize the STL to an exact size.
2. For resin, hollow the model to save resin, with drain holes.
3. Open it in your slicer: it should load as one part with no warnings.

In the report from the tool, check three things: watertight should say yes, the part count should usually be 1, and the volume should fit the size you expect. If the original file had surfaces passing through themselves, the report notes that separately, which tells you the problem came from your file and not from the rebuild.