Several bugs

Arnbjerg

Looking at the newest version of Solibri I have seen multi-issues:

1/ Excluding components doesn’t work
Members being included in intersection check even though it should have been excluded (based on SOL/1/5.0). I only see it in new created/updated rules but on in existing rules.

2/ Warnings disappears
Warnings disappears as you fold out structure (based on SOL/1/5.0)

3/ IfcBuilding included in check
In the newest version IfcBuilding is also included in property check (based on SOL/203/2.5). This might be okay but I cant exclude it. How is this possible?

JSN

@Arnbjerg said in Several bugs:

1/ Excluding components doesn’t work
Members being included in intersection check even though it should have been excluded (based on SOL/1/5.0). I only see it in new created/updated rules but on in existing rules.

Ad 1: As the members are parts (“childs”) of the Curtain Walls solely excluding the memebers won’t work in your scenario. This is imho not a bug.

Ad 2 & 3 have been already adressed a (multiple times) in the past and nobody knows why nothing changes.

Pasi Paasiala

@Arnbjerg

Would it be possible to share an .smc file that duplicates the issue about folding?

Regarding building appearing in the issue, what does the issue description say? Typically building is added to the issue, if none of its components have a given property set. Instead of listing all components, the building is given.

Mario

No. 2 is a problem that also annoys me and massively. You always think that there are a lot of bugs and when you open the structure, you see that everything is fine anyway. It would be really nice if this bug would be fixed.

Pasi Paasiala

@Mario We couldn’t duplicate this. Is there a model you could share?

JSN

@Pasi-Paasiala @Mario

Isn’t that due to gatekeepers? Imho it’s indeed very irritating …

Mario

@Pasi-Paasiala Sure, here you can download the file:
Gatekeeper-Bug.smc

and above there’s a gif that shows the problem:

Arnbjerg

Hi @Pasi-Paasiala,
Thanks for your reply.
Regarding sharing a smc file, Mario have already done that. Thanks.

Regarding if the property set doesn’t exist and the saying IfcBuilding.
That just confused me and thought the checked didn’t worked properly

I can see the info is given - just one hierarchy level above. See picture

Suggestion:
Maybe the info could be a little more specific like:
Any components in (B) <Bulding Name>
or
Any window in (B) <Bulding Name>

Arnbjerg

Thanks @JSN for your reply.

Regarding 1/ my picture was maybe a little too simple.
Before it was possible for me to void members and plates (the childs) from the CW by using a Classification setup

As you can see in my other pictures I have this Voided in all Checks in all checks.
This have worked fine before the update.
Maybe I have just found a small shortcut that have been “fixed”

I just find it annoying to find all issues related to the CW, and then all the CW’s child’s issues.
The same goes for stairs / slab and railing.
Do manage this on a smart way?

JSN

@Arnbjerg said in Several bugs:

This have worked fine before the update.

I assume your classificaiton works on a best match and not on a first match and does not allow multiple matches. But still, are you sure this worked in one of the last versions? By classifying “All” including the parent components you will automatically always get the children - no matter how you classify the kids. So excluding only the childs does not really have an effect as long as you always include the parent and afaik this has been the case for a while.

What you can do is to avoid double trouble is excluding the parents (e.g. CW) and only including the children (Panels/Members/…) you want in you classification. So then excluding those child parts in rules should work. Though it might has other side effects.