Diy Geometry Checklist

Why You Need A Checklist Before Exporting Your Models

I used to skip the verification step and ship projects with bad topology. It cost me two clients in the same quarter. After that, I built a systematic approach that now takes about three minutes to run through on any model, and it catches issues that automated mesh cleanup tools routinely miss. The core idea is simple enough, but the execution has some traps. The diy geometry checklist isn't fancy software. It's a repeatable sequence of verifications you run on any 3D model before committing it to production, export, or client delivery. Below is the exact workflow I use. It covers mesh hygiene, topology quality, normals, UV integrity, and a few edge cases that trip people up constantly.

How to Use The Diy Geometry Checklist

Run these steps in order. Do not skip ahead. Each step depends on the previous one being clean. If something fails early, fix it before moving on. A manifold mesh has no holes, no loose edges, and every edge connects exactly two faces. Non-manifold geometry breaks Boolean operations, 3D printing, and baking pipelines. Select all geometry and check the edge count versus face count. In Blender, pressing Ctrl + Alt + Shift + B highlights non-manifold edges. In other DCC tools, the equivalent is usually under a "Select by Feature Type" or "Mesh Analysis" panel. I ran into a specific case last year where a scanned architecture model had perfectly closed faces visually but contained internal co-planar edges from a merge-by-distance threshold set too high. The model looked manifold at a glance. Running the edge analysis revealed over 400 sliver edges that would have caused a slicing failure in PrusaSlicer. My workaround was setting the dissolve distance to zero, remeshing with a lower voxel size, and then manually healing only the faces that needed it. That took fifteen minutes instead of three hours of debugging a failed print later.

Step 2: Check Normal Direction Consistency

Face normals point the wrong way and you will never catch it visually until you are in render or bake mode. Enable face orientation display in your viewport. Everything should be blue on the outside, red on the inside. If you see a mix of colors on an exterior surface, flip the normals and recheck. Be careful with imported models. FBX files frequently have inconsistent winding orders depending on the exporter settings. When someone sends you an asset pack, assume the normals are wrong until you verify them. This step takes about twenty seconds and prevents an entire afternoon of troubleshooting baked AO shadows that appear inverted.

Step 3: Remove Redundant Geometry

Double-sided geometry, overlapping vertices, and duplicate faces are the most common problems in production models. Run a merge by distance operation with a threshold of 0.0001 world units. After that, select all faces and check for doubled normals by using a face select mode that shows both sides. Any face you see from behind is likely a duplicate that needs deletion. The overlap issue is especially sneaky with procedurally generated geometry. Subdivision surfaces and array modifiers can create internal faces that look harmless but add thousands of vertices to your final mesh. I once had a character rig that failed to export to a game engine because the merge step was never run and the vertex count was forty thousand over the limit. The file itself was unoptimized. Running the merge dropped it to twenty-two thousand and everything worked. This is why I always run a merge before any export, not just when something goes wrong.

Step 4: Validate Edge Flow On Deformed Surfaces

Topology matters differently depending on where the model lives. A static prop does not need clean edge loops. A character or anything that will bend does. For deformable models, verify that supporting edge loops exist around joints, knees, elbows, and the base of the neck. The loops should be evenly spaced and form quads rather than n-gons or triangles. If the topology converges into a single point at a joint, subdivision will collapse and you will get ugly pinching when the rig is animated. I encountered this on a mechanical armature where the creator had tapered everything into a single vertex for cleanliness. The rig deformed correctly at rest pose but looked completely broken at ninety-degree bends. Adding two supporting edge loops resolved it without any visible change to the surface at rest. That is the difference between clean edge flow and what people usually call "good enough."

Step 5: Check UV Layout For Distortion

UV distortion happens when islands are stretched or compressed non-uniformly. Open your UV editor and enable the checkerboard texture view. Any square that appears as a rectangle or parallelogram has distortion. Acceptable distortion varies by use case. A low-poly game prop can handle five to ten percent stretch. A high-poly character ready for normal map baking needs less than three percent across the entire map. Seams matter here too. A poorly placed seam will show visible texture jumps even if the islands themselves are clean. Place seams along hidden edges or areas where texture blending is natural. This is not something you fix with a button. It is something you fix by moving the seam to a less visible location and re-baking if necessary.

Step 6: Inspect For Loose Geometry

Loose geometry is any vertex, edge, or face that is not connected to the main mesh. It does not affect rendering but it causes massive problems in export pipelines, collision detection, and physics simulations. Most DCC applications have a command to delete loose elements. Run it and verify that the command deletes nothing unexpected. If it deletes something, you have a disconnected piece that should either be merged or intentionally separated. I found a loose wireframe once that had been left over from a sculpting pass. It was invisible in the viewport because it had no face data, but it was still in the scene file. The engine import crashed because the plugin tried to process it as collision geometry. Deleting loose elements with a single command prevented that issue from recurring.

Step 7: Rebuild Or Confirm Scale And Units

Wrong scale is a silent killer. A model that looks correct at one unit scale will be impossibly large or microscopic in the target engine or printer. Apply all transforms and confirm the bounding box dimensions match the intended real-world size. If you are exporting for Unity, the scale is one unit equals one meter. For Unreal, the same convention applies. For 3D printing, confirm that the printer's build volume matches your model dimensions before slicing. I inherited a project where the artist had modeled at centimeter scale but the engine expected meter scale. The character appeared as a ten-centimeter figure walking across a room. The fix was applying a global scale transformation and updating the material scale settings accordingly. This happened because nobody verified the export scale before building the scene.

Step 8: Test With A Quick Bake Or Sim

Before finalizing, run a quick bake of the normal map or a short subdivision simulation. This catches issues that no manual inspection will reveal. Bad normals, flipped UVs, and overlapping geometry all produce visible artifacts in bakes even when the model looks fine in the viewport. A ten-second bake on a test surface is faster than debugging a failed render later. For collision or physics validation, run a single frame simulation to confirm that the mesh does not tunnel through other objects or intersect unexpectedly. This step is optional for purely visual assets but essential for anything that interacts with gameplay or simulation systems.

When The Checklist Fails And What To Do Instead

Sometimes a model is too far gone for this workflow to help. Heavily tessellated scans, destroyed topology from previous reboots, or meshes with thousands of n-gons that cannot be cleaned by merging will require more than a checklist. In those cases, rebuild the problematic areas by hand or use a retopology tool. The checklist is designed for prevention, not for rescuing a broken file. If you are working with procedural geometry, the checklist still applies but the order changes slightly. Apply modifiers first, then run the verification steps on the final mesh. Do not verify before applying, because modifier stack changes can invalidate earlier results. There is no substitute for running through this sequence every time. I used to think I could skip it on small projects. I was wrong. The time saved by skipping the checklist is always lost later when something breaks in export or rendering.