BIMCraft (IPedrax) errors

5 recurring problems engineers report in BIMCraft (IPedrax), ranked by impact.

#90 by errors trackedMCADPLM

Recurring BIMCraft (IPedrax) errors, by impact

  1. 1A room separation line snapped wall face to wall face closed nothing when rooms were measured at wall centre lines; its ends stopped half a wall short, so each room on either side reported the whole open space in the room list, in schedules, and in the IFC GrossFloorArea. The Revit import's room matching used the same code path.MCAD · Agent failure · 1 report74
  2. 2An IFC4 file from Renga for a low-voltage design came in with every cable, conduit and pipe missing and every room name printed as '????'. 783 cable segments and 104 pipe segments were skipped because the reader had no case for IfcSweptDiskSolid; after the fix, 608 duct segments are still left out.MCAD · Agent failure · 1 report74
  3. 3On IFC import, an IfcDoor or IfcWindow with no opening or fill relationship to a host wall is dropped without a warning: on a 15 MB hospital model doors went 436 to 0, windows 305 to 0, with an empty warnings list.PLM · Agent failure · 1 report74
  4. 4a user driving BIMCraft from Claude Code reports Claude appears to open a project while the desktop window never changes, so Claude keeps working on something and it is unclear which project.MCAD · Agent failure · 1 report66
  5. 5The IFC export writes no type objects at all; every occurrence stands alone, so checkers and take-off tools cannot group by type, and beams and columns have no base quantities.MCAD · Agent failure · 1 report66

How it fails

  1. Agent failure5

Engineering tools that address these errors

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