BUG report 9.12 - Check selected not updating old results
-
Version 9.12 has a Major Flaw…something that has worked perfectly before:
If you check something, these results appear to be stored somewhere in the Rule. If you change the setup, that a rule check only “Check Selected”, the results are not updated.
- I have created a simple model where 2 spaces on the top floor are intersecting and 2 spaces on the ground floor are not intersecting.
- After the check, the top spaces are shown as Moderate Issue, which is correct.
- then I created the selection basket, with only the bottom floor
- after “Check Selected” the top floor components (which are not in the selection basket) are shown in the results
how is something like this possible?
pretty sure it has something to do, or it is a similar problem. see my old post.
https://society.solibri.com/topic/965/bug-in-solibri-9-12-gatekeeper-ruleshere are some pics and the file
test.smc
-
[0_1604513270150_original-smc-api-info-examples-1.0.0.jar](Uploading 100%) Hi. This was actually changed in 9.12.0 on purpose (https://www.solibri.com/news/solibri-9-12-0-release-notes)
What happens is that the possible previous results are not removed for those components that are no longer in the selection basket. The idea being that you are able to recheck certain components when changing parameterization and not losing the results for other components.
One way to get the old behavior back would be to set current selection basket to the main component filter. But that is not so easy, it would have to be done manually. It can be achieved with custom infos (https://society.solibri.com/topic/563/information-api)
We happen to have a property called “Is in selection basket” in our examples (https://github.com/Solibri/api-examples/blob/master/info-examples/src/main/java/com/solibri/smc/api/examples/IsInSelectionBasket.java)You can try the attached pre-built example property and see if that fits your workflow. Just choose that property in your component filter in the rule you want to recheck and check all instead if selected. Download the attached ZIP, extract the JAR file inside it to C:\Users\Public\Solibri\SOLIBRI\API and try it out.
-
Hello @marchi!
I updated the title for you. As Lasse already mentioned, this behaviour is intentional, and there has been a discussion here. The main idea here is to take a logical approach that, if you have not made changes to your previous checking results, and if those components are not included in the selection basket (i.e. you will not be making changes), then they should not be altered while using check selected on separate components.
Kind regards,
Toni on behalf of the Solibri team
-
thank you both, @lasse-lindqvist and @tonigyllenberg for your fast response. I must admit this time I did not check the release notes, as I was in a hurry and now made a fool of myself.
you can probably close this topic as solved, I will write my thoughts on this in the link provided by Toni and also check the stuff from Lasse.
-
@lasse-lindqvist said in BUG report 9.12 - Check selected not updating old results:
We happen to have a property called “Is in selection basket” in our examples (https://github.com/Solibri/api-examples/blob/master/info-examples/src/main/java/com/solibri/smc/api/examples/IsInSelectionBasket.java)
Could it be that the usage of this custom property slows down Solibri tremendously? Not only in the mentioned rule example but also when used in classification?
-
@jsn said in BUG report 9.12 - Check selected not updating old results:
@lasse-lindqvist said in BUG report 9.12 - Check selected not updating old results:
We happen to have a property called “Is in selection basket” in our examples (https://github.com/Solibri/api-examples/blob/master/info-examples/src/main/java/com/solibri/smc/api/examples/IsInSelectionBasket.java)
Could it be that the usage of this custom property slows down Solibri tremendously? Not only in the mentioned rule example but also when used in classification?
Definitely possible that custom properties do that. You can check the effects by removing usages of any custom by removing it and comparing the speed. This particular one shouldn’t be that slow. Maybe if you have a huge selection basket (+100K components), but otherwise it is not doing very much calculation.
-
@lasse-lindqvist said in BUG report 9.12 - Check selected not updating old results:
Definitely possible that custom properties do that. You can check the effects by removing usages of any custom by removing it and comparing the speed. This particular one shouldn’t be that slow. Maybe if you have a huge selection basket (+100K components), but otherwise it is not doing very much calculation.
It definitely was the culprit this time causing a lag of one or two minutes. Tried it out in a rule, classification and the filter and every time the same slow down. There were more than just a few components in the basket but less than 50k. Anyhow will try it out in a fresh file the other day to see if it is just file (or instance) related as I have had similar lags in the past without being able to clearly identify the reason for it.
-
In case the example is something you want to use and it is causing slowdown, there are ways to make it faster, but it does require some development effort. Basically you need to cache the results and listen to onBasketSelectionChanged events and then recalculate the results.
-
Well, basically what brought me here was the original issue of this topic. I have to check the model by using the selection basket (Check Selected) because I just want to check and create a report for e.g. the first two floors of the model.
My problem now is that after updating models, I still get the “old” results showing in the results box altough that there have been already resolved issues - most likely due to the fact that there are now components (probably because they have been removed e.g. duplicates) which are not in the selection basket anymore.
So I can filter the results, and even the result summary is not taking the “old” results into consideration. However updating presentations still creates or keeps old slides with issues - so there are slides indicating duplicates in the model altough those components may have already been removed. And I can not even change the coordination status of those slides manually - all I do is I can delete them but it seems like the next time I update the presentation, they appear again (as the triangle is still there, yet not really existing).
That’s why I hope to resolve this behaviour by using a gatekeeper at the top using the custom property. Unfortunately this did not work due to the performance crash. Any ideas left?
-
Using it would be faster if it was in a single rule filter in addition to the normal filters, because there you likely do some other filtering as well. So for example for door rule you would only have to check if it is in the selection basket for all the doors, not for all the components.
Of course it is cumbersome to add the property to all subrules, maybe it is not suitable for your case either.
One alternative is to have a custom rule. A custom rule that returns an issue for all components in the selection basket, or all components not in the basket. Then this rule can be used as the gatekeeper rule.
Copyright © 2025 Solibri Inc. | Powered by NodeBB