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

Recurring agent failure issue in vcad (muni-works)

vcad (muni-works)MCADAgent failureMedium confidence

What engineers report

A recurring agent failure problem in vcad (muni-works) that mostly hits the mechanical designer.

Failure pattern: validation / failure

Analyst note

From the Grok pain-radar digests, Nov 11-12 2026 (Nov 11 8:41 AM ET through Nov 12 5:41 AM ET digests plus the Haitch editions). Verified live 2026-11-12: issue/PR read; title and state confirmed.

What it costs a team

Modeled annual cost

$30,000

For a team of 5

Prototype delay

3 days

Modeled schedule slip per occurrence

Time lost

240 min

Per engineer per month, about 1 incidents

How the cost is modeled

240 min/month × 5 engineers × 12 months = 240 hours × $125/hour = $30,000

A modeled estimate with medium confidence. Swap in your own team size and loaded rate to size it for your team.

Engineering tools that address it

No engineering tool profile lists this error yet. Browse tools that connect to vcad (muni-works).

Evidence

  1. 1muni-works/vcad PR #1126: fix(step): interop audit - no hangs, colours, assembly placement, NURBS exportgithub.com

More recurring errors in vcad (muni-works)

See all 4 vcad (muni-works) errors

Sourced from public community reports. Costs and delays are modeled estimates, not measurements. Know a better source or a fix? Tell us at hello@productflo.io.