General Discussion

@Mats_Knutsson said in Possible to get cset header to report?:

I have namned my csets and rules in an easy to understand manner and would like them to come in as headers in the report so that I could organize them nicely. I this possible or a wish?

Isn’t that the case?

32afae5e-ba80-42f1-86b4-d1010cfd6c5b-image.png

Afaik in the last update the rule order on export should be fixed as well and therefore you should be able to easily use power query to get any transformation of the list you want.

Ok now it is there. Thx. I must have fiddled around so much the original rule I wanted to go to was deleted/changed and thus greying out the option.

Hello @teun_1!

Thanks for your message. While 9.13 is compatible with older Solibri versions, 9.13 does bring in support for additional IFC4 components, which are not supported in previous Solibri versions.

More informaiton on these are available in the Release notes.

Kind regards,

Toni on behalf of the Solibri team

@john-lipp I’m not worthy…

@Mats_Knutsson You can add this to the Feature Requests list.

Hi @david-polanski ,
Is Dalux also confirmed?
Thanks!

Hi @Matti-Kannala

Thanks for your answer… i understand most of what you say.

I can send you a smc file… maybe you can check it there.

Below an ITO of the levels… here you can see 2 models with different elevations but close to each other…
this is what is causing the extra footprint.

52a078a4-a412-4ef7-ba1d-86d9c328a3b2-image.png

The strange thing is… that if I add another model with lots of different levels with Elevations that do not match… no footprints are added.

Good luck on the new release!

Well, it is as I expected…

For some reason, the integers are not working. Maybe this has something to do with the German version?

For the time being, I simply used a text to get what I needed to work (working with variables of 0, 1 and 2.)

I didn’t play around with length that much…but I suppose that would be the only other possible option to use operators. “Real” Numbers also didn’t seem to work.

Since there are no replies, I figured I would revive this topic.

I have a similar issue. I am exporting a model with information regarding the concrete finishes. I would like to avoid setting unnecessary values in Revit. When I export my revit file, parameters which contain no value are no exported.

The operators in the classification are actually very very weak, and if I were able to, I could just handle this issue with wildcards.

What to do? It seems I need to create multiple rules just to handle a short-coming in the software. Is that so?

I guess if it’s Nemetschek…that makes sense…

Yes of course.
the issue is that accessibility rule gives quite many results. I’d like to know only if there is enough head space. So I thought that minimal distance rule should work, but is seams stairs do not work with it like slabs do.

In any case minimal distance rule should work or does the element need to be more regular shape?

Just seeing this post by now.
I just created a similar issue, which I found were related to the volume and size of the objects the rule is checking.

https://society.solibri.com/topic/2251/small-components-and-sol-234-1-2-issue

Hi Jeronen,

thanks again!
That’s a solution for me. Not as intuitive as i hoped it would be, but ok.
🙂

br
Marcus

@JSN

Then it partially explains, the level hierarchy is not taken by global coordinates, but by Top and Bottom elevation (properties) (*sea level or project), and the problem might lie inside of different software.

AR model is done in Revit, where is possible to export project coordinates and shared coordinates which include sea level, by defining sea level height - the top and bottom elevation in Solibri will show sea levels.

And EL model is done in CADmatic, and they have set floor heights by project heights.
and there is no such thing as a project or shared coordinates, where the model is set - that’s what you export. (with or without coordinates)

And seems that this explains the problem 🙂

As Solibri is unifying software maybe would be possible to integrate if there would be a possibility to pick by what the flooring hierarchy is done - top and bottom elevations or global Z elevation

This would solve some problems if the project is already done, for example,
we gonna test, EL gonna set the floor height by sea level and see if this works, or any other solution I will post an answer here. 🙂

Thanks.

@build-effects @JeroenKoomen @Harmen-Jorritsma @Ricardo @hkringsKUBUS

It seems that this is now working. Apparently Bimcollab is throwing and exception that version 9.12 can handle. Yesterday it threw an exception that 9.12 cannot handle, but 9.13 can.

Hi @cecilia-wang and @Paul-Linder

The new Info view looks like a great improvement 🙂

I agree with everything said (sticking the closest to bS terminology would be best, IfcQtoSets should have their own tab, selecting elements with same property value, seeing IfcProject in the hierarchy).

I have a related suggestion: pinning/bookmark some properties so that they appear on top of their tab or in a dedicated tab. That way you could have a quick manual check on how they are used throughout multiple elements. It would be nice to arrange and maybe even group your own pinned properties to your preference.
In this use case, it is also slightly annoying that the active tab is “reset” when you click on an element that doesn’t have the pset.
e.g I’m checking content of Pset_DoorCommon but click on a Door that doesn’t have it. Then when I click on the next Door, I need to reselect the Pset_DoorCommon.