CaseMaker (SlyWombat) errors

3 recurring problems engineers report in CaseMaker (SlyWombat), ranked by impact.

#159 by errors trackedMCAD

Recurring CaseMaker (SlyWombat) errors, by impact

  1. 1The CLI posted a 27-hour rotary CNC program that the app Save gate would have refused, and said nothing: the refusal lives in the app store and engrave.ts posts files directly and never consults it, so a headless run and the app disagree about what may leave the building, silently. A second bug in the same receipt has an oversize warning claiming Generate refuses a part before building the toolpath when it did not.MCAD · Agent failure · 1 report74
  2. 2CaseMaker posted a 25.3 mm freeing cut on a 0.9 mm PCB router bit whose flute length was blank. One path checks the stated flute length before giving a cutter the freeing contour, while the other path checks geometry only. When the picker chose a 25 mm flute bit for a 25.3 mm profile, the contour fell through to the 0.9 mm bit with flute length 0 in the record, and the program ran 1 h 51 min against 14 min 47 s on the right bit.MCAD · Agent failure · 1 report66
  3. 3The maintainer wants the elephant and panther demo parts passing before any bench work. The elephant mesh in a hardwood blank stops at "no candidate cutter plan." The stand-in reaches 32 percent of the surface from the top, proposes six setups for 80 percent, and one program runs about 18.5 hours. The gate is the simulation, and it isn't there yet.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.