Hi,
I'm using OBD update 5 and I have faced following problem.
Some of the developed bridge aburtment elments were modeled using smart solid intersection with "standard" OBD element, eg. retaing structures walls with variable height. The point is these elements but others as weell can't be selected using any of "soild" display style. After switching to Wireframe view mode these elements disappear, so also can't selected.
Any idea what can be a reason of such behaviour and how to reset selection mode, to make the selection active for all elements?
Regards,
Bogdan
General view
Ctrl+A selection
Crossing selection - e.g. retaining structures not selected
Wireframe model - no "unselectable" elements visible !
Hi Bogdan,
When you say "standard OBD element", are you referring to native MicroStation elements such as extrusions or other solids?
Also, from the View tab select the Toggle SWA Display tool - are any of the elements outside of the Solids Working Area? If so, if you copy one within the SWA does anything change?
Lastly, assuming these elements are Feature Solids, if you were to copy one and convert it to a Smart Solid using the Convert To Solid tool, does the behavior change?
Hello Steve,
"Standard OBD element" is the one like wall, slab, beam, etc. made using internal OBM command/tool (I'm using structural tabs for creation)
Yes, entire is placed within SWA
Elements copied form dwg refernce file were described as "smart solid" (see properties panel below), so I didn't convert them again. I have made the try to "renovert" it but this element can't be seleceted. This confirms it is smart solid I think.
The only good information for now is that it seems all items are poperly exported to IFC (even these "unselectable"), and IFC is the format I "talk" to the Client. The weak point is I can't modify element, rather create it from the beginning.
I had seen this issue, when there is a display rule defined, things are working fine in rendered mode. If you select ‘none’ display style this problem reappears. I have one defect for the similar issue which supposed to get resolved in Update 6.
For now just create any blank rule, and apply it instead of none, and check if it works for you.
Rg,
Sandeep
Hello Sandeep,
Unfortunately I'm not so advanced user to be familiar with so “deep” options. As I Understand Display rules is a kind of Display style “extension”.
I have tried to follow you advice but I can’t see any difference - probably it is a matter of my lack of Bentley software knowledge.
When I get into Display rules through the View Attributes panel I can see ("preview") the results of using different Display rules. After closing Display Styles panel when Untitled or NO_RULES option was pointed I could see only selectable elements.
Display Styles panel works different way when is opened through the Change View Display Style. “Preview” is not active and after closing the view is not changed. When Display Styles panel is open through View Attributes the Display Style is set to “none” again.
So no matter how I was changing Display Rules elements still can’t be selected. And it is not the solution I’m looking for :).
Where did I go wrong ?
“None“ Display Rule
“Untiltled“ and NO_RULES Display Rule (both "blank")
Best regards,
It's possible the elements you've created are demonstrating a slightly different behavior. Are you able to attach a DGN file with a few of those elements for further review? I suspect that may be the only way to make progress.
Thank you for your try. I was desperate enough to uninstall the newest update, back to the last "AECOsim" version and start from the beginning. I was quite surprised but "old good AECOsim" (update 4) did the same, I mean creates both selectable and unselectable elements. The good point is that menwhile I have discovered the "rule" to create only selectable elements. It works fine when elements are created just after the file is open. When I was doing it later during the session unselectable elements were created. It was easy to see it working in wireframe view/mode - created elements disappeared. So for now I'm happy with my "solution", I must only to reopen the file:). I will test it with OBD, but later.
Answer Verified By: Steve Cocchi
While I am glad to see you are at least able to continue working, this is a fairly unusual circumstance in that it only occurs after you've been working for a while. Particularly since the process is copying elements from a reference which wouldn't have changed at any point. If you ever wanted to pursue this further I would suggest submitting a test case (preferably good and bad elements) to support for review.