rvt-rs (DrunkOnJava) errors

15 recurring problems engineers report in rvt-rs (DrunkOnJava), ranked by impact.

#24 by errors trackedMCADPLM

Recurring rvt-rs (DrunkOnJava) errors, by impact

  1. 1A field report tested 49 project files saved by Revit 2024 to 2027; 25 carried an older release's element-record marker and all 25 read as zero elements and zero Levels. 8 of those markers turned out to be Revit 2022 and 2023 schemas in files whose history starts in 2014 to 2020.MCAD · Agent failure · 1 report74
  2. 2A user ran 49 of their own Revit files through v0.6.1 and v0.12.0 and matched elements by Revit id. On 9 files, 665 elements that used to export as real meshes came out as 12-triangle boxes, mostly beams, plus railings, lights and doors. One light fixture went from 18,944 triangles to 12. On a 438 MB file, 73 doors were written as IfcOpeningElement instead of IfcDoor. The new version also reads 16 files the old one couldn't, and is faster. Nothing errored. You only see it if you diff the two exports element by element, which is what they did.MCAD · Agent failure · 1 report74
  3. 3IFC export from a Revit reader was missing area and volume quantities on all 279 office columns.PLM · Agent failure · 1 report74
  4. 4On a Revit 2024 project, rvt-ifc wrote 73 AR_DOR_ doors as IfcOpeningElement and the other 361 as IfcDoor. The converter decided "this type only cuts its host" from a byte scan that missed a geometry-material map, so a door with unread materials became a hole in the wall. The PR calls it "a standing misread rather than a regression," unchanged since v0.6.1. Fix reads the type's native map and labels the case "materials not read" instead of "draws no geometry."MCAD · Agent failure · 1 report74
  5. 5A Revit file reader dropped the transform of door instances whose element data sat in two partitions with disagreeing origins, leaving the doors with no transform at all.MCAD · Agent failure · 1 report66
  6. 6A Revit file reader had been excusing a differing wall Width whenever two exports disagreed on wall type, which would also hide a Width that is wrong because the reader picked the wrong type.PLM · Agent failure · 1 report66
  7. 7a Revit file reader named 12 pipes, 9 wall sweeps and 5 ramps with generic ids and no type where Revit's own export names the type.MCAD · Agent failure · 1 report66
  8. 8A Revit-to-IFC converter exported monolithic stair landings as boxes spanning the whole storey, making them 12.7 to 15x Revit's volume.MCAD · Agent failure · 1 report66
  9. 9a Revit-to-IFC fidelity census never counted quantities (52,038 Qto_ values across 12,910 objects) and skipped property sets held on type objects (1,618 values), so both were neither scored nor reported missing.MCAD · Agent failure · 1 report66
  10. 10a Revit-to-IFC reader drew saved meshes that were only part of an element's body because nothing in the file says whether a saved mesh is complete, and the mesh step ignored the per-element decode log.MCAD · Agent failure · 1 report66
  11. 11an open-source Revit file reader found 195 walls in an office model off by up to 1.65 ft because the IFC export carries no wall-join relationships.MCAD · Agent failure · 1 report66
  12. 12even after reading each wall type's core layers, only 482 of 607 walls on the as-built office model match Revit at T-joints.MCAD · Agent failure · 1 report66
  13. 13mullion NetVolume was the largest missing quantity in the IFC export (10,003 values); a simple box volume matches Revit on only 9,791 mullions, so it ships only where a rule can prove it right (7,795 of 10,003).MCAD · Agent failure · 1 report66
  14. 14Revit's IFC export writes a CrossSectionArea on all 10,003 curtain mullions that grows with length; on 4,413 it is half the surface area (0.3625 m² on a 3.6 m, 50×50 mm mullion whose section is 0.0025 m²), and any downstream takeoff trusting the export inherits the error.MCAD · Agent failure · 1 report66
  15. 15the Width parameter Revit's exporter reads is not OverallWidth (the cut outline); on the office model they differ on 259 of 269 doors, mostly by 10 mm, and picking the wrong one is silent.MCAD · Agent failure · 1 report66

How it fails

  1. Agent failure15

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