SpindleLabs (SpindleLabs-app) errors

3 recurring problems engineers report in SpindleLabs (SpindleLabs-app), ranked by impact.

#205 by errors trackedMCAD

Recurring SpindleLabs (SpindleLabs-app) errors, by impact

  1. 1One cut through two boxes followed by an edit to the first box's position left three bodies and 31,200 mm3 instead of four bodies and 41,600 mm3, a missing 10,400 mm3 chunk with no row in the Bodies list and nothing in the STL. In a second case a Join left a body drawn on screen but out of the Bodies list, and STL export reported 'Checked solid' at 1,480 mm3 instead of 2,480.MCAD · Agent failure · 1 report74
  2. 2In a browser CAD tool, a body used as the tool in a later Combine vanished from the Bodies list and from the exported STL. Export STL also gave no file while any Combine was failed, and the Body panel showed the wrong piece. Four fixes came out of one readiness check, all behind a flag.MCAD · Agent failure · 1 report66
  3. 3In a browser parametric CAD, a fuzzer found an edit that moved a feature with no dependency on the edited one. Step 224 of a seeded run set a size, and feature-170's end centroid jumped from z 85 to 47. It is a fuzz report with a replay command, not a user complaint, but it is the exact failure that makes people distrust a parametric history.MCAD · Agent failure · 1 report66

How it fails

  1. Agent failure3

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