Nesting

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

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

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