Solidworks_ClashMate_MechDog (wudahua) errors

5 recurring problems engineers report in Solidworks_ClashMate_MechDog (wudahua), ranked by impact.

#104 by errors trackedMCAD

Recurring Solidworks_ClashMate_MechDog (wudahua) errors, by impact

  1. 1A SolidWorks MCP tool for assembly mates. On a real column assembly (2 nodes, 6 mates) native error count was 0, but 3 mates had references that couldn't be read. On an 18-node frame with 51 mates, also 0 errors, but 4 unresolved references. The PR says a native error count of 0 can't be read as complete references or as safe to write, so the tool now stays read-only with all_mates_sufficient left as null. 804 offline tests, 803 pass. PR is in Chinese.MCAD · Agent failure · 1 report74
  2. 2An MCP tool that adds external mates to rigid sub-assemblies found that an internal fixed axis returns IsFixed false in the top-level context and true in its own assembly document. The tool now reports both values separately and refuses flexible, virtual, suppressed or mismatched-configuration sub-assemblies rather than guess.MCAD · Agent failure · 1 report74
  3. 3A SOLIDWORKS mate-completion MCP tool went from 8 targets per run to whole-assembly plans in batches, taking mates from 114 to 158 on an 80-component reducer. The author writes that a complete checklist and full target coverage do not mean the tool understood the mechanical purpose, and it keeps unknown original mates rather than guessing from names.MCAD · Agent failure · 1 report66
  4. 4The MCP assistant now adds missing mates inside rigid sub-assemblies, but only one external sub-assembly document per transaction and only after the plan is confirmed. Four CAD runs exited non-zero and the cause is not proven, so the author kept it as an open warning.MCAD · Agent failure · 1 report66
  5. 5The MCP now reports structure and mate health for 129 to 500 node assemblies in read-only mode, where before it lost the whole report past the 128-node write limit. They spell out that an empty candidate list means no search ran, not that no mates are missing. Conveyor sub-assemblies are still blocked by external modelling references. A real lift module read 150 nodes and 30 root mates across 3 sub-assembly instances. Agents in CAD hit hard limits on how much of an assembly they can safely act on.MCAD · Agent failure · 1 report66

How it fails

  1. Agent failure5

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