KiCad forum (community) errors

7 recurring problems engineers report in KiCad forum (community), ranked by impact.

#64 by errors trackedECAD

Recurring KiCad forum (community) errors, by impact

  1. 1SamacSys part fields like manufacturer_part_number vanished from footprints in KiCad 10, so the ODB++ export carried no MPN and the team only found out at export time.ECAD · Agent failure · 1 report74
  2. 2KiCad's Delete all markers but exclusions still wipes the exclusions even when the user picks only error and warning markers.ECAD · Agent failure · 1 report66
  3. 3The KiCad Fabrication Toolkit plugin's BOM and position file formats are rejected by JLC's JLCone ordering app, so makers wrote their own Python converters, and KiCad 11 drops the API the plugin uses.ECAD · Agent failure · 1 report66
  4. 4A KiCad 9 user on a large panelized board hit GPU memory exhaustion that dropped the PCB editor to fallback graphics at about 1 fps, with pcbnew using 2.6 GB of system RAM and about 1.5 GB of GPU memory.ECAD · Agent failure · 1 report58
  5. 5In KiCad 10.0.8-rc1, the leftmost column in the Symbol Fields Table cannot be edited, while moving it to second place works.ECAD · Agent failure · 1 report58
  6. 6Several Eagle .brd layers always need the same manual mapping on import, a bunch of manual clicks prone to user error, with no import profiles or API hook to automate it.ECAD · Agent failure · 1 report58
  7. 7The KiCad 10.0.7 pad preview fills with corrupted pixel noise once the mouse moves into the preview widget.ECAD · Agent failure · 1 report58

How it fails

  1. Agent failure7

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