Solidworks

You build a steel frame as a weldment in one part file. Twelve identical 1500 mm long pieces of 50x50x3 square tube, plus eight 800 mm cross braces of the same profile. The cut list folder shows the right rollups: the long pieces grouped under one folder, the short pieces under another. The properties match. Then you drop the part into a parent assembly with a few other weldments, drop a BOM on the drawing, and the cut list items from the second weldment refuse to combine with the matching items from the first. Same profile. Same length. Same description. Different rows. ...

A fabricator sends you a DXF. It has the cut profile, the bend lines on a separate layer, and a note that says “10 ga A36, K=0.42”. You need to recreate it as a SolidWorks sheet metal part so you can validate fit, run interference checks against the assembly, and re-export a DXF that matches your shop’s layer conventions. There are two ways to get from that DXF to a working sheet metal body in SolidWorks. The discoverable path through the UI — Boss Extrude (Thin) → Convert to Sheet Metal → Sketched Bend — is what most users land on because every command is on a top-level toolbar. The cleaner path — Base Flange from sketch → Sketched Bend along bend lines — exists but it’s hidden behind a Sheet Metal toolbar that nobody opens until they’ve already started the wrong way. ...

A SolidWorks fab shop posted a sheet metal failure on Reddit last month. Their part had two L-flanges meeting at a corner with a small fold-back tab on one of them. The Sheet Metal feature kept throwing “Failed to compute flat pattern”, and after an afternoon of fighting it, they exported the DXF anyway, opened it in AutoCAD, and finished the cut profile by hand. Twenty-eight upvotes on a comment showing a five-step rebuild that worked for someone else but not them. ...

A user posted on r/SolidWorks asking why exporting a multi-view drawing to DXF produced a file with only one view. The replies suggested sheet templates, view scaling, and the usual draft-quality toggles. None worked. The actual cause was buried two dialogs deep: the DXF version dropdown in Tools → Options → File Locations → Export → DXF/DWG was set to R12. R12 cannot store layouts. SolidWorks wrote the model space and silently dropped everything else. ...

The r/SolidWorks thread that prompted this post had a line that anyone who has automated sheet metal exports will recognise: “I can’t for the life of me get the API to cooperate with DXF orientation on sub-bodies at arbitrary angles. Multibody DXF export wants to maintain the base part axis.” The comments offered advice that did not work, because the root problem is not in the macro — it is in how SolidWorks decides where a flat pattern lives in 3D space, and how ExportToDWG2 carries that decision through to the DXF. ...

Every few weeks a mold shop posts a job for a Python or C# developer who can automate their SolidWorks mold design pipeline. The scope is usually the same: take an incoming 3D model, run shrinkage, generate parting surfaces, split the core and cavity, and hand off tooling data. The assumption is that because SolidWorks has a documented API, every mold step is scriptable. It isn’t. Some steps map cleanly to IFeatureManager calls. Others still require a human to pick faces in the graphics area. Knowing which is which is the difference between a pipeline that ships and one that spends six months bouncing between the add-in and the user. ...

SolidWorks automation: four levels and where drawing creation fits SolidWorks automation exists on a spectrum. Understanding where each approach sits — what it costs to implement, what it can do, and where it breaks — saves engineers from picking a tool that is the wrong shape for the job. Level 1 — Record macro. SolidWorks’ built-in macro recorder captures UI actions as VBA code. You click through a sequence of steps, stop the recorder, and have a macro that replays those steps. This works for simple, identical operations: changing a document property across ten files, printing a drawing with fixed settings. It breaks immediately when the input varies — different part names, different view orientations, any conditional logic. The recorder also silently drops interactions with dialog boxes, property manager panels, and anything that requires polling SolidWorks for a return value. The SolidWorks macro recorder limitations guide documents exactly what it misses. ...

A replica-aircraft builder models an FW-190 fuselage skin in SolidWorks. Lofted surface, roughly 1.2 metres long, tapering and curving in both directions. They try Flat Wrap. SolidWorks flattens a strip down the middle and nothing else. They try Flatten Surface. It runs, produces a shape that’s 30% larger than the original, and when they cut aluminium to the pattern and try to form it, the edges don’t align by inches. ...

The DXF comes back from the shop and half the edges are gone. The drawing view looks correct on screen, the Save As DXF runs without errors, but the file a laser cutter opens has a rectangle where there used to be a contoured profile. If this part started life as a STEP import, the chain of failures is almost always the same, and the root cause is not in the DXF export — it’s in the imported body. ...

There is a habit you pick up after a few years in SolidWorks: if a part needs to become a DXF for laser cutting, you Convert to Sheet Metal. It is the path of least resistance. The Flatten button is right there. The flat pattern drops into the feature tree. Export DXF and move on. For parts with actual bends, this is correct. For flat parts — gears, brackets, plates, gussets, gasket profiles — it is the wrong default, and on patterned bodies it can turn a sub-second rebuild into a ten-second rebuild. This post explains what the sheet metal feature stack actually costs you, why circular and linear patterns amplify the cost, and when to stop reaching for Convert to Sheet Metal at all. ...