Rhino 3D Tip: DWG Export Checklist — Units, Layers, and Entity Mapping

Exporting DWG for consultants is all about clean layer structure, correct units, and predictable object types. Here’s a focused checklist to ensure your DWG lands perfectly in AutoCAD and downstream CAD/CAM tools.

• Start with a clean model
  • Confirm units and tolerances in Document Properties before exporting; agree on units with your recipient.
  • Run Purge to remove unused layers, blocks, linetypes, and hatch patterns.
  • Use Check to catch bad objects; fix or delete anything reported as invalid.
• Get layers and attributes right
  • Set object Color, Linetype, and Print Width to ByLayer whenever possible. This is critical for CAD standards.
  • Verify layer colors, linetypes, and lineweights match the target standard (AIA/ISO or your office template).
  • Know that Rhino sublayers export as names like Parent::Child. If your partner dislikes the double-colon convention, rename layers (e.g., Parent_Child) before export.
  • Use Layer States Manager to store export-ready configurations you can recall in one click.
• Choose the correct DWG scheme
  • File > Save As > DWG, then click Options. Pick a scheme that fits your deliverable:
  • For 3D handoff: AutoCAD 2007+ Solids (exports NURBS as ACIS solids). This yields the most usable solids in AutoCAD and many CAM apps.
  • For 2D drafting: R12 Lines & Arcs (suppresses splines; outputs only lines and true arcs for fabrication and legacy workflows).
  • Save your custom export settings as a named Scheme so your team can reuse the exact mapping.
• Map geometry to appropriate DWG entities
  • Curves: If your recipient cannot handle SPLINE, convert to polylines with a tight tolerance, but allow true arcs where possible.
  • Surfaces/Polysurfaces: Prefer ACIS solids when exchanging with mechanical teams; choose meshes only when file size or game engines require it.
  • Blocks: Keep repeated elements as block instances for smaller files and consistent editing downstream.
  • Hatches: Use standard patterns (ANSI/ISO names) to avoid DWG remapping issues.
  • Text/Dimensions: Export as native DWG text and dims, not curves, unless you must “bake” a graphic look.
• Model Space vs Layouts
  • For production drawings, export from Layouts to include paper space, details, and title blocks.
  • Confirm print scale and page size match the recipient’s plotting standards.
• Units, scale, and linetype scale
  • Keep Model Space at 1:1 in the target units. Avoid last-minute unit conversions at export time.
  • Check linetype scale so dashed/center lines read correctly in AutoCAD.
• Validate the handoff
  • Reopen the DWG in a fresh Rhino session to verify layers, object types, and annotations.
  • If possible, spot-check in AutoCAD to confirm layer names, ByLayer attributes, and plotting behavior.
• Pro tips for repeat deliveries
  • Create a project-specific DWG Scheme and a Layer State tied to the client’s CAD standard.
  • Automate boring steps with a macro or toolbar button that sets the scheme and exports in one action.
  • Document the agreed export protocol in your project README for consistency across the team.

Need trusted licenses, upgrades, and expert guidance? See Rhino at NOVEDGE, explore CAD workflows and training via the NOVEDGE hub, and ask their team for configuration advice tailored to your consultants and fabrication partners.

You can find all the Rhino products on the NOVEDGE web site at this page.