You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's related to closed issue 504.. Hey @agviegas, I updated libraries to "@thatopen/components-front": "2.4.2",
"@thatopen/components": "2.4.3",
"@thatopen/fragments" : "2.4.0",
"web-ifc": "0.0.66", and there are still a few errors (less than before) on the components side that are not present on the web-ifc demo page, I sended you fragment of this model in private message to check
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.
Describe the bug 📝
It's related to closed issue 504.. Hey @agviegas, I updated libraries to "@thatopen/components-front": "2.4.2",
"@thatopen/components": "2.4.3",
"@thatopen/fragments" : "2.4.0",
"web-ifc": "0.0.66", and there are still a few errors (less than before) on the components side that are not present on the web-ifc demo page, I sended you fragment of this model in private message to check
Reproduction▶️
No response
Steps to reproduce 🔢
Load ifc in newer components
System Info 💻
Used Package Manager 📦
npm
Error Trace/Logs 📃
No response
Validations ✅
The text was updated successfully, but these errors were encountered: