partcad (partcad) errors

10 recurring problems engineers report in partcad (partcad), ranked by impact.

#45 by errors trackedMCADVerificationPLM

Recurring partcad (partcad) errors, by impact

  1. 1A second caller could get a part object half built, before its path and cache dependencies were set; that failed CI as os.path.exists(None). The fix registers an object only once its factory has finished.MCAD · Agent failure · 1 report74
  2. 2partcad gen skills now write target dimensions down with a source, datum and tolerance, draw a candidate, render it, measure the same dimensions on the render, and correct until each is in tolerance. It is a full verification loop bolted on because the agent guesses were not good enough.Verification · Agent failure · 1 report74
  3. 3A part referenced through an alias, like goBILDA's E-clip bought under each shaft's SKU, was drawn in the default colour and weighed nothing, because the alias did not carry its source's material and mass. Export and info commands found no material data on it.MCAD · Agent failure · 1 report66
  4. 4Each exporter used to say its own thing about a face, and an uncoloured face came out goldenrod. Now one module feeds STEP, glTF, 3MF and URDF so they agree on colour and material.MCAD · Agent failure · 1 report66
  5. 5partcad CMF series packs a palette of colour, material and finish sets into a binary section after the BREP, per part, per solid and per face, and has the core write it after any offset or scale so assemblies keep it. OCCT readers ignore the trailing bytes, and a test holds them to reading the same geometry.PLM · Agent failure · 1 report66
  6. 6PartCAD first CMF PR adds colours, materials and finishes as declarations. A manufacturable flag separates this can be bought from a display hint, so a render colour is not mistaken for a finish spec.PLM · Agent failure · 1 report66
  7. 7PartCAD now reads Fusion, SolidWorks, Inventor, CATIA and other native formats by converting them to STEP with cadmpeg, and a part that isn't a clean solid fails instead of becoming a broken part. Results are checked against cadmpeg's own volumes and diffs. cadmpeg 0.6.7 drops a face from an IGES file, and a test makes sure that part fails.MCAD · Agent failure · 1 report66
  8. 8partcad third CMF PR reads colours and materials from STEP and KiCad through XCAF, and from build123d, CadQuery, OpenSCAD and 3MF sources. Geometry stays byte for byte the plain reader, and it follows an earlier finding that CMF got lost through assemblies.PLM · Agent failure · 1 report66
  9. 9Running a Gazebo simulation of a CAD package in a remote container failed five ways in a row, each hidden behind the last: stock images have python3 but no python, one CAD library's install overwrote another's geometry module so every CadQuery part failed, and a world exporter's meshes didn't come back with the world file so Gazebo couldn't load it.Verification · Agent failure · 1 report66
  10. 10The partcad remote sandbox rewrote file paths on the command line but not in the request on stdin, so readers looked for files that did not exist in the container. IGES parts failed with OpenCASCADE could not read plate.igs, and STEP assembly imports broke the same way. The sandbox lost every file path passed in the request, so STEP, IGES and URDF imports failed in upload mode.MCAD · Agent failure · 1 report66

How it fails

  1. Agent failure10

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