Using Rhino 8.18.25090 and VisualARQ 3.4.0.19712. This issue was discovered a couple of days ago so before the latest Rhino and VA release candidates.
Using V 3.6.2 IFC import engine (Geometry mode) some of my geometries are distorted but parameters seems to import just fine. Using V4.4.0 engine it’s the opposite, geometry is ok, but parameters are not imported.
The question is: What’s the current state of development of the IFC import? Are these isssues known?
@Czaja excuse the late reply on this issue. The V3 engine for importing IFC files is the same as it exists in VisualARQ 2.
In VisualARQ 3 we have added the V4 engine which is the one that can read IFC 4 files, and it is much faster than V3 Engine. However, it still misses the option to read parameters on geometry, and export to IFC 4. We are currently working on these functions and as soon as we ensure V4 engine works completely, we will remove the former engine V3.
Thanks,
I’ve only recently become interested in IFC. I’m hoping that VisualARQ will make it easy for me to import geometry and analyze parameters. I’ve also run into a broader problem with parameters names and effectively referencing desired parameters. If not VisualARQ, then I’ll have to look into GeometryGym.
