IFC export from a Revit reader was missing area and volume quantities on all 279 office columns.
Import, export & interop reported against rvt-rs (DrunkOnJava)
What engineers report
A import, export & interop reported against rvt-rs (DrunkOnJava): breaks when reading, writing or converting files and data between tools.
Recorded mode: validation / interop
Analyst note
From the Grok pain-radar digests, Oct 26-27 2026 (Oct 26 12:41 PM ET through Oct 27 7:41 AM ET digests plus the Haitch editions). Verified live 2026-10-27: issue/PR/thread read; title and state confirmed.
What it costs a team
Modeled annual cost
$30,000
For a team of 5
Prototype delay
3 days
Modeled schedule slip per occurrence
Time lost
240 min
Per engineer per month, about 1 incidents
How the cost is modeled
240 min/month × 5 engineers × 12 months = 240 hours × $125/hour = $30,000
A modeled estimate with medium confidence. Swap in your own team size and loaded rate to size it for your team.
Engineering tools that address it
No engineering tool profile lists this error yet. Browse tools that connect to rvt-rs (DrunkOnJava).
Evidence
More recurring errors in rvt-rs (DrunkOnJava)
- A 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.Mechanical · impact 74
- A 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.Mechanical · impact 74
- On 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."Mechanical · impact 74
- A 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.Mechanical · impact 66
- A 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 & data · impact 66
- a 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.Mechanical · impact 66
Sourced from public community reports. Costs and delays are modeled estimates, not measurements. Know a better source or a fix? Tell us at hello@productflo.io.