@JeroenKoomen yes it should be ok: we got in contact with Autodesk and the change of endpoints is indeed happening. They added us to the list of customers that get extra time until the 31st of July. The reason why we don’t need to make a hotfix release is that contrary to the earlier information we had, the required changes can only be done in the backend, which doesn’t require a new release. We have already implemented the changes in the backend but it may take some time until they become effective i.e. when V2 endpoints are in use. There should anyway be much enough time for that to happen before the end of month. So everything should be fine but we’ll follow up the situation in case problems would arise.
Today i had the same kind of problem with missing elements, if i open the IFC as a stand alone the element are present. if i update the ifc in the SMC they are still missing.
removing the ifc totaly from the SMC and ADD the model then the missing elements appear.
this totaly makes updating models not reliable and is an absolute a no go for using Solibri
This should be resolved in the latest build of the Fire Stopping rules, the issue is related to components distance from the origin. We now transform the Door to the origin create the studs and re-position to carry out the clash.
@Matti-Kannala So as I understand, the Location will auto regenerated for comp that has spaces in relation and it will not appear if the comp doesn’t have any spaces in relation.
Hi, This is a known bug and is logged to be fixed. The COBie project has to be the first project opened once Solibri is started otherwise this happens. Simply close the project (save if required), shutdown Solibri and then restart Solibri opening the same project, load your COBie settings and the calculate button should now be available.
@agroni If the property sets you accept follow some naming pattern, you could have a regular expression that matches all other property set names and prohibit all properties in those with a regular expression matching any string.
Hi Mathieu, The Identification rule has a check box for identifying where this occurs
Check the option and the supply the component that it needs to cross i.e. a BWIC or Fire Seal using the filter / filter with classifications.
image.png
We have a update coming soon to this rule which will allow you to check for different scenarios.
image.png
Were you ever able to resolve the issue? A client of ours has the same problem and we’re not sure whats causing it. Now we have a ton of duplicates in our Database. Did the problem go away by itself and do you know at what Version it stopped?
