Dxf

A forum thread from 2026-08-06 captures the problem precisely: a user has a manual workflow — roll back to a feature state, show the body, align the view normal to the target face, then do File > Save As DXF. It works. They then try to replicate it in VBA using IPartDoc.ExportToDWG2, pass the same file path, and get either a failed export (False return, no error) or a DXF that contains nothing. No accepted answer exists because the root cause isn’t obvious from the API documentation. ...

Fabrication shops that receive DWG files from SolidWorks drawings often expect specific AutoCAD layers — BRASS, STAINLESS_STEEL, ALUMINUM — matching the actual part materials. The native Save As layer mapping table in Document Properties → DXF/DWG Export → Map SolidWorks to DXF/DWG maps entity types to layers, not component materials. There is no UI checkbox that says “use material name as layer.” This post shows the API approach: read each component’s material from the drawing views, create named layers in the drawing document, assign components to those layers, then export to DWG. It covers the key API calls, a complete working VBA macro, and the three edge cases that will silently fail on a naive implementation. ...

A Reddit thread about exporting countersunk flat patterns to DXF recently generated 14 replies. Every single one suggested a model edit: suppress the countersink, delete the chamfer feature, open the flat pattern in a drawing and manually remove the circles before exporting. Not one mentioned that SolidWorks has had a built-in DXF layer mapping feature for years that routes countersink geometry to a separate reference layer at export time — no model changes required. ...

If you’ve tried to get a flat pattern from a cylindrical collar in SolidWorks, you’ve hit this wall: the Sheet Metal toolbar’s normal workflow assumes you start flat and bend up. A cylinder was never flat. SolidWorks has no direct “unroll cylinder” command, and if you try to use the Convert to Sheet Metal tool on a solid cylinder, it either rejects the geometry or produces a body with wrong thickness. ...

SolidWorks exports flat patterns correctly. Nesting software imports DXF correctly. The problem is that what SolidWorks produces by default and what nesting software expects are often misaligned — and the failures are silent. Profiles import with no errors but cut the wrong features. Bend lines disappear. Splines approximate differently on each machine. Scale is off by 25.4×. This post covers the specific mismatch between SolidWorks DXF output and what ProNest, SigmaNEST, Lantek, and similar nesting tools expect, and the exact export configuration changes that fix it. ...

Every SolidWorks tutorial on flat pattern views shows the same thing: open a sheet metal part, drag the flat pattern from the View Palette into a drawing. That works perfectly when you have one part and one drawing. It doesn’t help when you have an assembly with twelve sheet metal components and you need all the flat patterns in a single drawing document. The assembly case has two complications that the single-part case doesn’t. First, the View Palette shows assembly-level views, not individual part views — so the flat pattern doesn’t appear there. Second, when you insert from the assembly, SolidWorks shows views relative to the assembly coordinate system, not the part’s sheet metal orientation. Knowing which insert path to use for each scenario saves the frustration of inserting views that display the wrong orientation or can’t locate the flat pattern at all. ...

Every SolidWorks user who sends DXF flat patterns to a laser or plasma table eventually runs into this: the file imports into the CAM software, but the part is floating somewhere off in negative coordinate space, or centered around zero, or positioned wherever it happened to be when someone modeled the part. The CAM operator repositions it manually. Every. Time. This is not a CAM software bug. SolidWorks exports the flat pattern geometry exactly as it exists in the part’s coordinate system — wherever that happens to be. The fix is to tell SolidWorks to reframe the export around a specific point on the part, usually the lower-left corner of the bounding box. ...

When you cut a hole on a bent face in SolidWorks, you get a circular feature in 3D. When you flatten the part, that same hole can appear as an ellipse in the flat pattern — and that ellipse is what gets exported to your DXF and sent to the laser cutter. The laser punches an ellipse. Your hole doesn’t fit the fastener. This isn’t a bug. It’s geometry. But the fix is straightforward once you understand what’s happening. ...

The question of SolidWorks versus Fusion 360 for sheet metal comes up constantly in manufacturing communities. Most comparisons focus on modelling speed, K-factor accuracy, or bend table flexibility. What they skip is the output side: what the DXF file actually looks like when it hits the laser cutting operator’s desk, and whether the nesting software can consume it without manual cleanup. This matters because the DXF is the handoff document. Everything downstream — nesting, laser cutting, press brake setup — depends on the geometry, layers, and metadata in that file. A flat pattern that looks identical in both tools can produce dramatically different DXF outputs. ...

Drop a DXF file onto your GIS and the geometry lands in the middle of the ocean, rotated 90 degrees, scaled by 25.4. Or it lands in the right country but offset by a few hundred metres. Or it imports cleanly into QGIS but every feature ends up on a single layer called “0” with no attributes beyond the original AutoCAD entity type. This is not a bug you can fix with a setting. The CAD-GIS format gap is structural. DWG and DXF were designed for engineering drawings, not for placing things on Earth. GIS formats were designed for the opposite. The two worlds have different answers to three fundamental questions: where are these objects, what do we know about them, and how do they relate to each other? ...