xeokit-convert v1.3.1 currently depends on web-ifc 0.0.70 (released July 2025).
Since then, several relevant fixes have been released, most notably:
- PR #1701 "TriangulateBounds-check-OUTERBOUNDS" (merged November 19, 2025,
included in web-ifc 0.0.74+): fixes a critical issue where IFC models that
incorrectly declare inner face bounds as OUTERBOUND cause malformed meshes.
This directly affects the "No basis found for brep!" errors observed in
production when converting complex IFC files.
Impact of staying on 0.0.70:
When converting IFC files with complex or invalid B-rep geometry, web-ifc
enters an infinite retry loop in TriangulateBounds(), causing unbounded memory
growth and an eventual OOM kill (signal: killed). The process fails entirely,
producing no output.
We cannot use the 2-step pipeline (IFC → GLB via IfcConvert → XKT) as a
workaround because IfcConvert does not preserve IFC metadata (property sets,
element names, classifications) in the GLB output. The direct IFC → XKT path
through web-ifc is the only option that retains full metadata.
Request: update the web-ifc dependency to 0.0.77 (latest as of March 2026)
to benefit from the TriangulateBounds fix and other geometry improvements
shipped since 0.0.70.
Linked to this issue : #176
Thanks !
xeokit-convert v1.3.1 currently depends on web-ifc 0.0.70 (released July 2025).
Since then, several relevant fixes have been released, most notably:
included in web-ifc 0.0.74+): fixes a critical issue where IFC models that
incorrectly declare inner face bounds as OUTERBOUND cause malformed meshes.
This directly affects the "No basis found for brep!" errors observed in
production when converting complex IFC files.
Impact of staying on 0.0.70:
When converting IFC files with complex or invalid B-rep geometry, web-ifc
enters an infinite retry loop in TriangulateBounds(), causing unbounded memory
growth and an eventual OOM kill (signal: killed). The process fails entirely,
producing no output.
We cannot use the 2-step pipeline (IFC → GLB via IfcConvert → XKT) as a
workaround because IfcConvert does not preserve IFC metadata (property sets,
element names, classifications) in the GLB output. The direct IFC → XKT path
through web-ifc is the only option that retains full metadata.
Request: update the web-ifc dependency to 0.0.77 (latest as of March 2026)
to benefit from the TriangulateBounds fix and other geometry improvements
shipped since 0.0.70.
Linked to this issue : #176
Thanks !