cadmpeg (cadmpeg) errors

14 recurring problems engineers report in cadmpeg (cadmpeg), ranked by impact.

#25 by errors trackedMCAD

Recurring cadmpeg (cadmpeg) errors, by impact

  1. 1A SolidWorks-to-STEP reader gives every face the same orientation, so on NIST CTC-01 all 45 concave cylinders became convex, while cadmpeg check reports OK with 0 errors.MCAD · Agent failure · 1 report74
  2. 2After a parser change, real SolidWorks parts that used to decode now come back with zero bodies, or 1 body where there were 23, with nothing crashing; only bisecting against real parts caught it.MCAD · Agent failure · 1 report74
  3. 3Surface-intersection edges are written as straight-line polylines with no tolerance and no loss reported, while the STEP file declares 1e-6 mm uncertainty. On a CC0 crane part the chords stray up to 1.280 mm off the cylinders they are supposed to lie on.MCAD · Agent failure · 1 report74
  4. 4The reporter converted 171 public SolidWorks parts (NIST and CC0 repos) with cadmpeg 0.6.7. 27 came out with no solid at all, written as an open shell; in 20 of them the internal model was a proper solid and the writer dropped 941 faces, 747 of them blend and offset faces.MCAD · Agent failure · 1 report74
  5. 5Upgrading the decoder dropped a ten-design Fusion 360 verification set from 9 of 10 passing to 3 of 10: a malformed component link became fatal with no flag to proceed, and 0.6.6 STEP output wrapped solids so the next tool in the chain read zero bodies from a file holding two solids.MCAD · Agent failure · 1 report74
  6. 6A CAD checker refuses a valid FreeCAD 26.3 file whole with 13 errors over edge ranges 1e-16 outside the knot domain, while OpenCascade and FreeCAD accept the same file fine.MCAD · Agent failure · 1 report66
  7. 7A Fusion .f3d decoder decoded zero dimension frames in all 15 public files from its first census, so dimensions either stayed native or fell back to guessing by measurement, due to two bugs: lookup by the wrong key, and only one of two type IDs accepted. On current main, 47 of 2,394 constraints come through as native.MCAD · Agent failure · 1 report66
  8. 8CATIA decoding assigns face colors to the wrong faces on a 112-face part despite matching color counts.MCAD · Agent failure · 1 report66
  9. 9CATIA decoding exports a 34-face part as a solid with negative volume.MCAD · Agent failure · 1 report66
  10. 10FreeCAD files restored with null shapes after alphabetic member sorting, meshes lost their owning placements, and STEP replica operators omitted inherited attributes.MCAD · Agent failure · 1 report66
  11. 11FreeCAD files with features inside an App::Part or used through an App::Link decoded with wrong positions while volumes and topology stayed correct, because the decoder applied a member's placement twice and the STEP writer dropped root occurrence placements.MCAD · Agent failure · 1 report66
  12. 12Inventor extrusions whose sketch has no closed neutral graph used to keep their whole native definition. They now project as Extrude with a native profile, and every extrusion left native records a pinned loss so the gap is visible.MCAD · Agent failure · 1 report66
  13. 13Inventor surface extrusions stay native with a recorded operation-graph loss; a neutral projection needs the operation map, Boolean slot roles and exact curve selection.MCAD · Agent failure · 1 report66
  14. 14Inventor Thicken features that stayed native carried no loss record; only partial ones did. The private corpus has 1,094 Thicken features, 745 of them native.MCAD · Agent failure · 1 report66

How it fails

  1. Agent failure14

Engineering tools that address these errors

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.