vcad (muni-works) errors

4 recurring problems engineers report in vcad (muni-works), ranked by impact.

#140 by errors trackedMCADECAD

Recurring vcad (muni-works) errors, by impact

  1. 1A SolidWorks 2021 STEP file came into a CAD app missing 112 of its 294 faces, with loose patches scattered around the body. The reader took B-spline control points in [v][u] order instead of [u][v], so 79 patches failed the knot check and the square ones came in transposed. All 33 rational B-spline patches were rejected, B-spline faces were meshed over the whole untrimmed surface, and partial cones came out as full 360 degree bands at about twice their real area.MCAD · Agent failure · 1 report74
  2. 2An open-source CAD kernel audited STEP import against 21 public files from Fusion 360, Onshape, SolidWorks, FreeCAD and KiCad. Before the fix, 9 of 21 hung for over a minute, no file kept its colours, assemblies collapsed to one copy of each part at its local origin, and 4 failed STEP export. One root cause was ignoring a face-orientation flag that OCCT and KiCad StepUp write on nearly every face. After the fix, 20 of 21 match OCCT face counts, but most files still import as open shells.MCAD · Agent failure · 1 report74
  3. 3Fab-prep converged on an incomplete board and the app reported 0 unrouted because the gate never checked whether the board was complete.ECAD · Agent failure · 1 report74
  4. 4vcad's dogfood pass found a fillet that made the part vanish with no message, and a 111-part ECAD board that hung the app at 6.7 GB. A fresh window could not model anything because every tool was disabled behind a hover hint, and an edge fillet on a boolean result failed to resolve its edge name and the part disappeared silently. Failed features now undo and show the kernel's reason.ECAD · Agent failure · 1 report66

How it fails

  1. Agent failure4

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