We've recognized that IfcProxy geometries are missing in flatMashes after the geometry loading with web-ifc:
const flatMeshes = ctx.ifcAPI.LoadAllGeometry(ctx.modelID);
When the same ifc model is loaded in the web-ifc-example viewer (https://tomvandig.github.io/web-ifc/examples/viewer/index.html), all IfcProxy geometries are there. Futhermore, if we rename the "IfcProxy" objects with e.g. "IfcWall", the geometries are also loading.
We've recognized that IfcProxy geometries are missing in
flatMashes
after the geometry loading with web-ifc:const flatMeshes = ctx.ifcAPI.LoadAllGeometry(ctx.modelID);
When the same ifc model is loaded in the web-ifc-example viewer (https://tomvandig.github.io/web-ifc/examples/viewer/index.html), all IfcProxy geometries are there. Futhermore, if we rename the "IfcProxy" objects with e.g. "IfcWall", the geometries are also loading.
@xeolabs Do you have any idea how to solve this?