What problem does it solve?
This Skill helps you quickly identify why IFC models fail to load or render in ThatOpen when web-ifc/WASM initialization, worker setup, or data parsing goes wrong, turning vague black-screen failures into actionable recovery steps.
Core Features & Use Cases
- Pinpoint root causes by error message: Maps common failures like
RuntimeError: unreachable, CompileError, 404 on WASM/worker, undefined access errors, and worker/CORS issues to specific fixes.
- Guardrail checklist for reliable loading: Enforces the correct initialization order and required runtime configuration (IfcLoader
setup(), FragmentsManager worker init(), render loop, and scene insertion).
- Production-grade failure recovery patterns: Provides defensive loading retries and configuration adjustments for boolean timeouts, invalid/corrupt IFC, large coordinate precision, and WASM memory exhaustion.
- Use Case: When an external IFC file loads as a blank viewport or crashes your browser tab, use this Skill to determine whether the issue is WASM version mismatch, MIME/path/headers, worker initialization, data type, or importer category exclusions.
Quick Start
Use the thatopen-errors-loading skill when your IFC file fails to load or results in a blank viewer, and follow the error message mapping and initialization checklist to apply the correct fix.
