Sheet-Metal

If your flat pattern dimensions are wrong, the K-factor is usually why. But “set the K-factor” is the third step in a process that starts with understanding what K-factor is, what bend deduction is (they are different things expressed in different units), and — critically — knowing which of three separate places in SOLIDWORKS is actually controlling your flat pattern. K-Factor and Bend Deduction Are Not the Same Thing Both K-factor and bend deduction describe what happens to material during bending, but they describe it differently. ...

SOLIDWORKS 2026 SP3.2 introduced a regression specific to the flat-pattern DXF export path: bend lines appear in the cleanup window preview, the Bend lines checkbox in the DXF/DWG Output PropertyManager is checked, yet the written DXF has no bend line entities whatsoever. The geometry exports fine. Layers are correct. But the press brake operators get a DXF with no fold marks. This is a distinct failure mode from the SP3 regression documented in the general bend lines troubleshooting guide. That post covers the mapping file regression (enable-flag rows silently cleared) and per-user registry mismatches. The SP3.2 bug is different: the mapping file is intact, the registry value is correct, the entity bitmask is correct — and the export still omits bend lines. ...

A DXF file represents geometry in 2D — lines, arcs, splines, and circles with no thickness, no material, and no bend information. SOLIDWORKS’s sheet metal system represents a 3D part with folded geometry derived from a flat pattern governed by a K-factor and material thickness. The import workflow is about bridging those two representations, and there are three different paths depending on what you start with. What You’re Actually Working With Before choosing an approach, establish what the DXF contains: ...

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

The SOLIDWORKS sheet metal environment has two entry points: you either start with a sketch and build the part as sheet metal from the beginning, or you convert an existing solid into a sheet metal body. The second path—Convert to Sheet Metal—is the right tool for STEP imports and inherited legacy parts with no sketches. But it fails silently on a specific class of solid bodies, and understanding why matters both for fixing production parts and for writing API macros that won’t break on edge cases. ...

A user on the SOLIDWORKS 3DEXPERIENCE forum posted a question about elliptical cutouts in a sheet metal flat pattern. After exporting the flat pattern to DXF, every elliptical hole appeared as a SPLINE entity in the file. The laser cutter’s controller — a Trumpf TruTops installation — rejected the file. TruTops can cut true ellipses from native ELLIPSE entities but has no NURBS solver for arbitrary-degree SPLINE entities, so the holes were silently dropped from the cutting plan. ...

Every sheet metal shop with more than a handful of active parts runs into the same gap. The model changes — a bend radius is revised, a hole pattern shifts, a flange length is adjusted — and the SLDDRW already has everything: dimensions, bend notes, tolerances, title block, revision table. But the DWG that goes to fabrication is still sitting at the old revision. Someone has to open the drawing, let it rebuild, and export. Every time. ...

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