RvtIO (mahach666) errors

6 recurring problems engineers report in RvtIO (mahach666), ranked by impact.

#79 by errors trackedMCAD

Recurring RvtIO (mahach666) errors, by impact

  1. 1When the Revit project's length format cannot be read, the IFC export quietly declares millimetres, even for metre or foot projects. The fix asks for the fallback to show up in diagnostics.MCAD · Agent failure · 1 report74
  2. 2An open Revit file reader: a truncated or damaged .rvt used to end in an unhandled exception. It now reports per-stream decoded fractions, but members that fail to decode still exit 0 so existing scripts keep working, and strict mode is a follow-up.MCAD · Agent failure · 1 report66
  3. 3Demolished or not-yet-built elements can still go out in the IFC export, along with properties that have no value in Revit. The export does not honor phase the way Revit does.MCAD · Agent failure · 1 report66
  4. 4IFC base quantities from a Revit exporter were derived from the exported mesh, so cutting solids entered volume totals and door and window sizes came from bounding boxes. They now come from the source geometry. Every quantity takeoff built on the old export was reading the mesh, not the model.MCAD · Agent failure · 1 report66
  5. 5On Autodesk's Snowdon Towers sample, ramps, elevators and escalators come out as IfcBuildingElementProxy instead of IfcRamp or IfcTransportElement. Category meaning gets lost in translation.MCAD · Agent failure · 1 report66
  6. 6RvtIO now reads the project length format in more layouts, including Revit 2020 and family files. When it still cannot, it writes millimetres and says why, since Revit length unit cannot be read in some file layouts, so IFC export used to guess millimetres.MCAD · Agent failure · 1 report66

How it fails

  1. Agent failure6

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