Cadshift

GIS format conversions do not crash loudly when they fail. They produce an output file, report success, and leave you with data that is wrong in ways you may not notice until the analysis is already done. Field names get silently cut at 10 characters. Geometries disappear without warning. Coordinate systems shift without errors. Attribute types coerce to something that looks right but produces wrong numbers. These are not edge cases. They are the default behavior of the tools most GIS teams use daily — including GDAL/OGR, QGIS’s built-in export, and ArcGIS Pro’s geoprocessing toolbox. None warn you by default. ...

You add a louver, a lance, or a drawn cutout to a SolidWorks sheet metal part, flatten it, export DXF, and the cuts that should appear in the flat layout are either missing or positioned wrong. The forming tool placed correctly in the bent part. The flat pattern shows the footprint outline but not the cut geometry. The laser operator can’t nest from this file. This happens because of how SolidWorks models forming tool geometry — and the fix depends on which features are actually in play. ...

Open Task Manager during almost any SolidWorks session and you’ll find sldProcMon.exe sitting quietly next to SLDWORKS.exe. Most of the time it’s invisible — a few megabytes of RAM, no window, no icon you’d notice. Then, on some machines, it pins a full CPU core at idle, spawns a fresh copy every time you relaunch SolidWorks without cleaning up the old one, or — in scripted and remote-desktop automation — climbs to 90%+ CPU and refuses to let go. ...

The “Abnormal bolt pretension is detected during the modifying pretension cycle” warning stops your simulation run and tells you nothing useful. The docs say check material and geometry. Forums say add contact sets. None of that is wrong, but none of it explains the actual failure mechanism. This post covers how bolt connectors work internally, why the two-step pretension analysis exists, what “abnormal” actually means in this context, and the specific setup errors that trigger it. ...

You’ve spent an hour adding custom properties to each cut list item — part numbers, supplier codes, cost-per-unit. You modify a structural member, hit Rebuild, and they’re gone. Not obviously corrupted. Just attached to the wrong items, or pointing at stale folders that no longer exist in the tree. This is the cut list auto-update problem, and it’s not a bug. It’s the expected behavior of a consolidation system that doesn’t know you cared about those specific folders. ...

Some SolidWorks settings save reliably between sessions. Others reset silently every time you restart, or behave differently depending on how SolidWorks was installed, what Windows profile type is in use, and whether any admin policy overrides your preferences. This post covers the specific settings that fail most often, where they’re stored, and the fixes that work. Where SolidWorks Stores Its Settings SolidWorks stores user settings in two places: the Windows registry and document files. Knowing which is which tells you immediately whether a reset issue is a machine problem or a template problem. ...

The Wrap feature works instantly or fails with a cryptic error, with little indication of which outcome you’ll get until you click OK. Three modes — Emboss, Deboss, Scribe — fail in different ways and for different geometric reasons. Knowing which one applies to your geometry, and why the others will fail, stops the rebuild-error loop before it starts. What the Three Modes Actually Do All three Wrap modes start with a sketch on a flat plane and project that sketch geometry onto a curved or non-planar face. The divergence is what happens to the geometry after it lands. ...

A supplier discontinues a product line. You need to find every SKF bearing in a 600-part machine assembly and evaluate alternatives. With the standard Select menu you can hunt them down individually — or you can open Advanced Component Selection, type vendor = SKF, click Apply, and have every matching component highlighted in 3 seconds. Most SolidWorks users have never touched this tool. It sits one click off the cursor menu and handles property-based selection that would otherwise require a macro or a full PDM search. ...

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

If you’re moving from ArcGIS Pro to QGIS, Attribute Rules are one of the first things you’ll miss. ArcGIS Pro’s Attribute Rules let you attach Arcade scripts to a geodatabase layer that fire automatically on edit — calculating fields, enforcing constraints, validating records. QGIS has equivalents for all three categories, but they work differently, and none of them are geodatabase-level rules that execute independently of the client application. This matters: QGIS’s field rules live in the project file, not the data source. If someone opens your GeoPackage or Shapefile in a different QGIS project — or in a different GIS tool — those rules don’t travel with the data. That’s a significant architectural difference from ArcGIS Pro, where rules are stored in the geodatabase and enforced by the database engine. ...