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

When you cut a hole on a bent face in SolidWorks, you get a circular feature in 3D. When you flatten the part, that same hole can appear as an ellipse in the flat pattern — and that ellipse is what gets exported to your DXF and sent to the laser cutter. The laser punches an ellipse. Your hole doesn’t fit the fastener. This isn’t a bug. It’s geometry. But the fix is straightforward once you understand what’s happening. ...

If you’re still reaching for Shapefile or GeoJSON as your default format for large static datasets, FlatGeobuf is worth understanding. It’s been in GDAL since version 3.1 (2020) and QGIS since 3.16 — but most teams still haven’t adopted it where it provides the clearest advantage: large datasets served from cloud storage. Here’s what it does, how its internals work, and where it outperforms the alternatives. What FlatGeobuf Is FlatGeobuf is a binary encoding for vector geographic data built on FlatBuffers, a cross-platform serialization library developed at Google. A FlatGeobuf file has four sections in fixed order: ...

A fabricator opens your STEP file. They run Insert Bends. SolidWorks creates a flat pattern. The dimensions are wrong. Not slightly wrong — off by several millimetres on every bend. Enough to cause rework. Enough to get a call from the shop floor. The reason is that STEP files don’t carry k-factor data. They never did. Understanding why, and what to do about it, is the difference between a clean handoff and a rebuild. ...

The cloud CAD pitch is straightforward: access your designs from anywhere, collaborate in real time, no IT overhead for file servers. For small teams working on straightforward product designs, it largely delivers on that promise. But engineering teams hitting cloud CAD limits don’t usually fail on the simple cases. They fail six months into a project when assembly component counts exceed the comfortable range, or when a compliance audit asks where the design data is physically stored, or when an engineer needs to work on-site at a customer facility with unreliable internet and the tool won’t load. ...

When SolidWorks shows you the Save As dialog, three STEP variants appear in the dropdown: AP203, AP214, and AP242. Most engineers pick one, never change it, and assume the output is correct. Sometimes it is. Sometimes half the data you expected to transfer isn’t in the file at all, and you find out when the supplier calls. This post explains what each version actually carries, what SolidWorks and Inventor write for each, and which one to choose based on what your recipient needs on the other end. ...

TL;DR: If your QGIS buffer is the wrong size, your CRS is EPSG:4326 (degrees) — switch to a projected CRS (e.g. a local UTM zone) before buffering, or enable the Geodesic Distance option in the QGIS 3.28+ Buffer dialog. The QGIS Buffer tool has one requirement that is easy to miss: the distance you enter is in the unit of the layer’s CRS, not the unit of your project CRS, and not any intuitive real-world unit you might have in mind. ...