Preparing and Repairing Meshes in Rhino 8: A Guide to ShrinkWrap, Mesh and Check

Rhino 8’s official documentation describes distinct roles for the Mesh, ShrinkWrap and Check commands in mesh creation and geometry inspection. Mesh generates a mesh from a NURBS surface, polysurface or SubD, while ShrinkWrap creates a new mesh that wraps selected geometry; Check reports errors in object data. This guide explains when to use each tool in Rhino 8 before export or 3D printing, and how settings affect the results.

1. What should you check before converting a model to a mesh?

Before converting to a mesh, inspect the geometry via Analyze › Diagnostics › Check. Select the object and run the command to get a report on the integrity of its data structure. If errors are listed, you may need to delete the object or remodel it. Check is a starting point for finding issues; a successful result does not prove that the model is 100% flawless. The documentation notes that some surface issues, such as surfaces that fold back on themselves or intersect, can be difficult to detect automatically.

Small edges—especially very short edges created by trimming or edges that curl back on themselves—are among the common sources of model problems. To join parts, aim for cleanly matched edges instead of adding very small lines along a curve. If Check reports errors, use the report to investigate whether fixes are needed; a clean report alone is no guarantee that the model is problem-free in every respect.

1. Convert a NURBS, polysurface or SubD to a mesh. The Mesh command generates a polygon mesh from these three geometry types. The resulting mesh is editable and separate from the source object. When creating a mesh from a solid object, Rhino creates a mesh without holes—that is, a watertight mesh—which is useful when exporting to rapid-prototyping file formats such as STL.

Simple controls in the mesh settings let you increase or decrease density. Detailed controls manage criteria that affect surface accuracy, polygon count and processing time. The values below are defaults or recommended ranges given in the Rhino 8 documentation; they do not represent a single ideal setting for every model.

1. Adjust refinement and joining behavior. When Refine mesh is enabled, Rhino subdivides quads until they meet the specified criteria. Disabling this option speeds up mesh generation, but results in a less detailed mesh with a lower polygon count. The documentation notes that Refinement is disabled for extrusions and ruled surfaces.

When Jagged seams is enabled, mesh edges on surfaces within a polysurface are not stitched together. This can speed up generation and reduce the polygon count, but gaps may remain between surfaces. When disabled, Rhino creates a watertight mesh. The Simple planes option fills planar surfaces with triangles along their boundary edges. It can be slower, especially on surfaces with complex trims; when this option is enabled, the other mesh settings are ignored for planar surfaces, except for Jagged seams.

1. Consider ShrinkWrap for damaged or fragmented inputs. The ShrinkWrap command, found at Mesh Tools › Mesh › Shrink Wrap, creates a mesh that encompasses NURBS surfaces, SubDs, meshes, point clouds and point objects. It can be used to create a solid mesh from multiple objects, mesh fragments of a 3D scan, or a closed mesh from geometry that is difficult to repair. Preview the result and adjust the options; the command is not intended to guarantee automatic, flawless repairs for every model.

Target Edge Length sets the approximate edge length of the output mesh; the default is calculated automatically. A positive Offset inflates the mesh and increases the face count, while a negative value shrinks the mesh and reduces the face count. A Smoothing iterations value of 0 disables smoothing; higher values smooth the mesh further, reduce the face count and pull the mesh further inward. Polygon Optimization ranges from 0% to 100%; a higher value removes more faces while preserving hard edges.

How should you use these tools in architectural and visualization workflows?

Architects and interior designers can convert geometry from Rhino to a mesh according to the requirements of its intended use in manufacturing or another application. Visualization teams can also create NURBS surfaces as editable meshes and adjust polygon density to suit their needs. Those working with 3D scans or point-cloud data can take note that ShrinkWrap supports these inputs. However, higher density can mean more polygons and slower processing, so settings should match the requirements of the scene and export target.

For 3D printing or STL/SLA preparation, don’t stop at creating a mesh. Rhino’s documentation notes that long, thin faces can slow printers, cause unexpected results or create memory issues; naked edges can also cause problems in rapid prototyping. Checks using tools mentioned in the documentation, such as MeshRepair and ShowEdges, can help investigate issues in files destined for production.

Common mistakes

• Treating a clean report from the Check command as proof that all geometry issues are gone.

• Assuming that higher mesh density is always necessary; polygon count and processing time may also increase.

• Expecting joined surfaces to be watertight when Jagged seams is enabled.

• Overlooking that positive and negative Offset values in ShrinkWrap affect the mesh in different directions and change the face count differently.

• Assuming a mesh is ready for 3D printing without checking for naked edges or long, thin faces.