Hello,
I was wondering if it was possible to model and adjust solids in Openbuildings without making a parametric solid that keeps every step saved. I have colleagues that tend to design in Openbuildings, but keeps adjusting certain volumes, cutting here and there, pushing and pulling a bit, cutting holes, and after a while we get parametric solids with a tree of around 50 steps if not more. We get the feeling that this might make for a very heavy object, and indeed files seem to be getting rather large rather quick. We can always drop the object, but it would be easier if we had access to either non feature tools, or to a setting to automaticly drop an object after using a tool.
Thanks in advance and with kind regards,
Jeroen
Hello Jeroen,
If you want the parametric solid to get changed to an smart solid, then instead of dropping the element, you can select the element & then in the key-in dialog type 'convert smartsolid' & once you hit enter from the MicroStation property dialog you will notice that element has turned into a smart solid.
I hope this helps you.
Regards,Alifur
Hi Alifur,
Thanks for your response. Unfortunately, when we use this key-in it cuts part of the name of the part, so that it loses the connection to the part, so this is not really an option for us.
Also, ideally we would like to just draw in smartsolids without having to always convert.
With kind regards,Jeroen
It seems that indeed the way you are describing is for now the best option. Bentley is looking into error of 'convert smartsolid', but until then I have to use this workaround. It would sure be easier if we could just work with smartsolids instead of parametric solids, but it seems that also isn't possible...
Regards,
Interesting that the family and parts info is lost when converting to smartsolids. Hopefully this will be fixed soon.
Not sure what kind of solids you are dealing with but one advantage p-solids have is inbuilt instancing. This makes it quicker than s-solids when there is a lot of repetition. Remember a tunnel model that was only 50m long formed out of segments of s-solids that was painfully slow.
This was mentioned in the Microstation Forum, and someone suggested using the Legacy Solids tools.
I don't know if this would help.
Thank you. I asked the representatives of Bentley repeatedly if there was an option to get the old smart solid tools back, and they couldn't help me, and here you are :) . I should have guessed they were called legacy solids, that would have saved me a lot of searching. Unfortunately, using the legacy solids also breaks the part... :( , but rest assured that we will have lots of use for the legacy solids tools.
don't think the old V5 legacy solids were much good for even low complexicity modeling. You don't want to have to switch horses mid stream when the older tech runs out of steam :-)
Legacy solids also have problems... with GC.
It would be good to test whether conversion to s-solids will really speed things up. You may find the p-solids might be better or about the same speed-wise inspite of having a long history tree. Not sure, maybe there is a way to collapse the sections of history tree. Top secret undocumented command?
I'll keep you posted if it makes any difference. It's my boss who wanted to try it anyway, and he was pretty convinced it would make a big difference.My dream solution would indeed be some kind of smart algorithm that combines, or removes irrelevant features from the tree. Maybe in the future... .
Hi Jeroen,
Thanks for raising this issue in SR 7001293335. I would like to inform you that this issue resulted in Defect Report 696666.
Shivam Soni