Archicad IFC wrong behavior in the XbimWebUI

[untecnologo]

We have noticed that when the IFC model is exported from Archicad, some elements have unexpected behavior, even when we are by code verifying that they are present in the 3D model.

There is a file attached in the below link.
https://file.io/LML93RL5LibH

This file in the viewer just shows the window:

But also there is a wall that the viewer is not showing.

Do you have any solution, or have you noticed this before?

We can reproduce this if the file comes from an Archicad IFC exporter.

Thank you in advance for your kind support!

[andyward]

How are you generating the wexbim - can you show the code? I've just tested and it renders fine:

Looking at the model, the Wall is modelled as an assembly/aggregation of multiple BuildingElementParts (representing the different layers in the wall). So the wall itself has no representation - it's all in the children. My guess is that somehow this is being overlooked in your wexbim generation, or the Geometry generation.

Here's the canonical way of creating wexbim. Are you doing something different?

[untecnologo]

Hello @andyward
This is the code that creates the wexBim.
All our files work fine, but for this specific case, it doesn't work as expected.

[andyward]

Presumably you're saving the (wexbim) MemoryStream to a file at some point? Or are you streaming it somewhere?

Hard to reproduce without seeing that. Can you also confirm which the versions you are using of

1. xbimEssentials
2. xbimGeometry
3. xbim WebUI (viewer)

[untecnologo]

Yes, we are returning to the front-end the MemoryStream and we process it as a blob in js.
About our versions:

xBim WebUI:

[andyward]

Thanks, so I have confirmed that's an issue in the latest v5.1 code, and is reproducible in wexbim/web viewer and in Windows UI. It's been broken for a long while - since 5.1.239 GE.

It's needs some analysis to see if it's an issue in the Tessellator or the Geometry.

The good news is it's fixed in v6 (albeit with some warnings, which may indicate why it has been failing). Let me know if you want a preview of v6.

[untecnologo]

Thank you very much for your reply.
I appreciate it.
We are in the middle of a feature development and all the feature run and use version 5.
For now, we will keep version 5 because we are almost at the end of the module.
But as soon as V6 is released in the nugget package we will be happy to update our project.
We need also V6 because, in that version, the issue of the DLL creation is fixed.

xBimTeam/XbimGeometry#455

[untecnologo]

Hi @andyward,
I have considered your proposal about the V6 of the plugin. After having too many issues with the topic we discussed here, I would like to have the opportunity to upgrade to V6 please let me know what I need to do or the repository link to access the V6.

Thank you in advance for your kind support.
Best regards,

[andyward]

Hi do you want to email me (email on my GH profile) and I'll get you invited to the preview nuget feed?

[untecnologo]

Done! I really appreciate it!

[spcaala]

Hi @andyward,

Thanks for looking into the issue and providing some pointers.

However, we still have this issue with the viewer not recognising and visualising walls from Archicad IFC models to be specific and some revit models. @untecnologo never did get access to the nuget preview feed, so we were not able to verify your suggestion.

However, we found a link from #526 to your myget resources and were able to get the latest develop for xbim essentials.

This solved one of the issues we were having with some models not being converted to WexBim, however, the invisible wall is still a problem.

xbim.geometry is still v5.1.742 and this all we can see from the resources link. Not sure if we are missing something.

Is there a separate resource link for xbim geometry ?

Here is screen shot all the updated packages.

For context:
Our project is .net48

Thanks for your time. Appreciate it.

[klamarth]

I had a similar problem with Archicad files. Where some walls were not exported. It may not be the same problem (I could not test your file as it was deleted).

I resolved it using this approach, that may or may not work for you.

I noticed that for CoordinationView export Opening and Additions must be added to the Wexbim
And for ReferenceView I should omit it.

This is inside the SaveAsWexBim() method

      // For CoordinationView we must use Openings and Additions
      // For reference view, we should not set this info and use the default setting
      var xbimShapeInstances = (isCoordinationView
              ? instances.Where(si => !toIgnore.Contains(si.IfcTypeId)
                                      && si.RepresentationType == XbimGeometryRepresentationType.OpeningsAndAdditionsIncluded
                                      && prodIds.Contains(si.IfcProductLabel))
              : instances.Where(si => !toIgnore.Contains(si.IfcTypeId)
                                      && prodIds.Contains(si.IfcProductLabel)))
          .ToList();

I extract the info about view from Header.FileDescription.Description

This is not a prod code, and may not be the correct approach. These are just some tests I'm conducting. It worked for all Archicad (so far) exported using the default settings.