Geometry differences between web-ifc demo page and OBC.IfcLoader

[robertbiskup]

Describe the bug 📝

Hi @agviegas and @HoyosJuan, could you please take a look at the issue disscused at ThatOpen/engine_web-ifc#1057 ? We got different results after uploading ifc files to web-ifc demo page(https://thatopen.github.io/engine_web-ifc/demo) and engine-components viewer using OBC.IfcLoader ( https://unpkg.com/[email protected]/58 and "@thatopen/components-front": "2.2.2",
"@thatopen/components": "2.2.11"). Web-ifc demo page all ifc files shows correctly - when using components - geometry errors appear. There are sample screenshots and ifc files.

Reproduction ▶️

No response

Steps to reproduce 🔢

Load ifc in newer components

System Info 💻

@thatopen/components-front": "2.2.2",
@thatopen/components": "2.2.11"

Used Package Manager 📦

npm

Error Trace/Logs 📃

No response

Validations ✅

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a repository issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
• Check that this is a concrete bug. For Q&A join our Community.
• The provided reproduction is a minimal reproducible example of the bug.

[HoyosJuan]

Hey @robertbiskup! That's beacuse we haven't update the web ifc dependency in components yet. Will be donee for release 2.3.0 coming this week.

[robertbiskup]

@HoyosJuan Thank you for the quick answer! This is crucial information, I thought that setting the "wasm" parameter was enough, so we are waiting for the update! ;)