28 lines
1.5 KiB
Markdown
28 lines
1.5 KiB
Markdown
# BIM IFC and OBJ batch 227c6067037c75d001fc9641
|
|
|
|
The format workflow now routes OBJ import to FreeCAD's native Mesh.insert
|
|
with the active document name, paired with the existing Mesh.export path.
|
|
Export recomputes the current document first. IFC import uses the desktop
|
|
importIFC.insert entry point rather than the empty importers package's
|
|
nonexistent load function.
|
|
|
|
IFC import and export still require a real IfcOpenShell backend in the BIM
|
|
WASM runtime. The source-inspection stub is explicitly rejected before
|
|
creating a document or invoking the IFC modules. This is an unresolved
|
|
business dependency, not implemented IFC support or acceptance evidence.
|
|
The desktop exporter and its geometry semantics remain intact.
|
|
|
|
IFC/OBJ input readability and destination directory structure are checked
|
|
before native format calls. This avoids entering native file handling for
|
|
the known missing-input and file-as-parent cases without changing geometry
|
|
or truncating an existing output during validation. It does not establish
|
|
the cause of the reported WASM memory-access failure; that remains subject
|
|
to isolated runtime verification.
|
|
|
|
Build, synchronization and business acceptance belong to the outer pipeline
|
|
and were not run in this edit batch. Reuse tools/bim-recovery-business-cases.mjs
|
|
for the four selected IFC/OBJ IDs; retain failed IFC results until the real
|
|
dependency is available and roundtrip geometry passes. OBJ grouping,
|
|
placement, overwrite, append preservation and recovery remain to be verified.
|
|
Other format workflows are outside this batch.
|