Tech Talks

Our colleagues are experiencing the same problem. The update affects the loaded role as well.

Thank you!

A little late but i was searching for the answer after an installation of a new laptop.
I couldn’t find the answer here, so after a little research i find this page.
https://help.solibri.com/hc/en-us/articles/27373469393815-Switching-to-a-Dedicated-Graphics-Card#UUID-89d0fc6f-aa94-b5cf-602a-e0928a133473_UUID-b6cd7b93-cba3-6d01-d98f-fb5a4405f8f1

With every update, and especially for new users, it’s always a hassle to get the roles configured correctly. Let alone the right settings for everything that isn’t included in the role—things like dimensioning and disciplines.
So there’s also a strong desire here to improve this.

As an update on this, we have reported this as a false positive towards Microsoft and are still awaiting an answer. It does seem however, that at least internally Defender no longer gives any notifications on our end.

@lal In the current Python script, the line:

ET.SubElement(target, “file”, file=ifc_file, shortname=shortname)

generates the following XML element:

<file file="modelname" shortname="shortname" />

However, since there is no autorun task associated with the ‘file’ tag, this needs to be updated.

To resolve this, please modify the line to:

ET.SubElement(target, 'openmodel', file=ifc_file, shortname=shortname)

Hope this helps.

Thank so much to the Solibri support, it was cleared up immediately. My fault and probably will happen to someone else as well: I renamed at some point my originally named “Solibri 25-6-0” installation folder into simply “Solibri” and that caused this strange blank screen.

Hey @Remco !

Thank you for inquiry and sorry for delay. The fix for this is underway and we aim to deliver it with next release. Thanks for reporting!

Still not fixed. Still no relief.

Could send some example IFC to [email protected]?

The properties and property sets that are with Italics in Solibri UI are coming from type object and defined for that.

Having a duplicate name is not good practice: https://standards.buildingsmart.org/IFC/DEV/IFC4_2/FINAL/HTML/schema/ifckernel/lexical/ifcpropertyset.htm
“Every property within the property set shall have a unique name attribute value.”

The fix for comments jumping up and saving mid-sentence is now available in 25.6.0:

https://society.solibri.com/topic/3367/solibri-25-6-0-has-been-released?_=1750918619539

Morning Simon,

I followed the above and this seemed to fixed the issue. However, we are now a few months on and i seem to be getting the same issues. IfcDoorStyle, IfcWindowStyle are being used but now the COBie_Type and COBie_Component PSets arent coming through.

image.png

image.png

This seems to only be an issue with Doors and Windows as i can see these PSets on other discipline items

image.png

@Harmen-Jorritsma I guess this should be implemented in the BCF standard ?
Because most platforms do it similarly (one responsible + additional notified people)

Same problem here. If I scale it manually, the UI scales better and is sharp, but the 3D viewport becomes blurry. This shouldn’t be a workaround, but rather a proper fix.

https://society.solibri.com/topic/2229/date-of-checked-model-version-and-current-model-version-in-report-result-sumamry?_=1749108385407

Hello Jim!

Nothing comes quickly to mind which might cause this sort of behaviour. Please send a support request to [email protected]. It would be good to include a screen recording of the behaviour, along with the log files and model (if possible).

Logs can be found here: https://help.solibri.com/hc/en-us/articles/21911035161111-Where-do-I-find-my-log-files

@manuel-furia I used getFootprint().getArea()
As a result, I get the points:
===group

(67.94999694824219, 54.125999450683594), (67.94999694824219, 57.21698760986328), (67.94999694824219, 57.2760009765625), (67.94599914550781, 57.46659469604492), (67.94599914550781, 69.76399993896484), (64.80999755859375, 69.76399993896484), (64.80999755859375, 71.95999908447266), (77.20077514648438, 71.95999908447266), (78.33565521240234, 71.78034973144531), (79.36084747314453, 71.25615692138672), (80.16404724121094, 70.45094299316406), (80.79560089111328, 69.3504409790039), (81.30156707763672, 68.17298126220703), (81.66816711425781, 66.9449691772461), (81.86998748779297, 65.79915618896484), (81.8904800415039, 65.68283081054688), (81.94999694824219, 64.66832733154297), (81.94999694824219, 54.125999450683594)

The draw look likes:
f433a431-847a-4c3f-9ee4-5a3e0d0912ba-image.png
zooming to the gap:
d5ab0390-c1e6-40ca-b0a3-2b9bc8464fa4-image.png

then I back to use getFootprint().getOutline() and find the draw look likes (the red one, the green one is from above)
39a0d287-e00c-410d-8d04-51c52fbcbd9d-image.png
Isn’t getFootprint().getArea() the API to get footprint of component?
0d454e27-8efb-4ead-bd0d-cfd8d8d6f1ad-image.png

I have the same issue.
Using “Remove Paint from Visible Objects” fixes the issue, even though I haven’t manually added the wrong colors to the .IFC:

image.png