Dxf

A sheet metal enclosure for an elliptical staircase, a conical shroud split into two halves for shipping, a large cylindrical tank section cut into panels for laser cutting — these all share the same fabrication requirement: a curved sheet metal body that must be divided into manageable pieces, each with its own flattenable geometry and its own DXF. SOLIDWORKS’s Split feature appears to solve this. It doesn’t. Applied to a curved sheet metal body, Split divides the geometry but destroys the flat pattern capability on every resulting piece. This post explains why that happens and gives three approaches that actually preserve flattenability. ...

A r/SolidWorks thread from last week: user exports a sheet metal part to DXF, sends it to the laser shop, gets a call saying the file is corrupt. The file is 20MB for a bracket with three bends. The shop’s nesting software chokes loading it. The user is exporting from the drawing, not from the part. This is the most common DXF export mistake in SolidWorks, and it is invisible until something downstream breaks. ...

Every nesting operator knows the moment: 200 DXF files land in an import folder named Part1.dxf, Part2.dxf, FlatPattern-3.dxf. The cut program runs. Parts come off the machine. Now someone has to match each blank to an installation slot by hand—measuring, comparing, labeling. This is a manual step that costs 30–90 minutes per nest cycle, scales with order volume, and doesn’t improve no matter how much you spend on nesting software. The root cause is a mismatch between what SOLIDWORKS produces by default and what ProNest, Lantek, and JETCAM expect in order to route parts back to their jobs automatically. ...

You receive a STEP file from a supplier or another team. It opens in SOLIDWORKS as an assembly with hundreds of sub-components. Some of them are clearly bent sheet metal parts—brackets, enclosure panels, mounting clips. Your goal is to get flat-pattern DXF files for the laser shop. When you right-click a component and look for Flat Pattern, it’s not there. SOLIDWORKS treats every STEP-imported body as a dumb solid: geometry only, no feature tree, no bend data, no flat pattern. Even if the body was originally modeled as sheet metal, none of that intelligence survives the STEP format. ...

A r/SolidWorks thread from August 2026 captures the confusion exactly: an engineer is trying to export a flat pattern DXF from a SolidWorks weldment to send to a tube laser shop. Every suggestion in the thread involves model edits, workarounds, or converting the weldment to sheet metal. Nobody points out the real issue — they are trying to apply a sheet metal export workflow to a part that belongs in a completely different machine category. ...

If bend lines stopped appearing in your DXF exports after a SolidWorks service pack update, you are not alone. The r/SolidWorks threads from August 2026 show multiple engineers hitting this after 2025 SP5 and 2026 SP3. Some had working configurations for years. They installed the update, exported a flat pattern, and the bend lines were gone. The problem is fixable — but only if you understand that bend lines disappear for fundamentally different reasons depending on how you export. Applying the wrong fix wastes time and leaves you thinking the issue is deeper than it is. ...

FreeCAD’s PartDesign workbench is the closest equivalent to SolidWorks’ Part environment. It uses a feature-based, parametric modeling approach built on OpenCASCADE Technology (OCCT) — the same geometry kernel that powers CATIA and Salome. If you’re coming from SolidWorks, Inventor, or any history-based modeler, you’ll recognize the concepts but encounter a few structural differences that aren’t obvious from the UI. This guide covers what actually matters for getting productive: the Body container model, how the Sketcher’s constraint system differs from what you’re used to, the core PartDesign features and their underlying OCCT operations, the topological naming problem that plagued earlier versions (and the fix in FreeCAD 1.0), and how to export finished geometry to STEP, DXF, and STL using FreeCAD’s import/export pipeline. ...

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. ...