We have many DGNs that appear to have phantom elements. That is elements that don’t display but ORD still appears to see.
Case 1: When moving the pointer over one of these phantom elements the element flashs on the display. At times they interfere with real element selection.
Case 2: I have a DGNs where I am trying to delete old feature definitions because they will not sync to the library definition and are out of date. So, I try to delete them from the DGN standards and add them back from the library. I have several DGNs that I cannot delete these feature definitions because ORD says they are in use, but there are no elements in the DGN. So, I believe it is these phantom elements that hold the feature definitions. Bentley support confirmed that it these phantom elements. It is also in these DGNs where these feature definition/phantom elements are causing failure of annotation – also confirmed by Bentley.
Case 3: This is not so much of phantom elements but instead elements that have broken rules, Red X, that are preventing them from being selected for deletion.
Why wouldn’t you not want to be able to delete phantom elements that may or may not be interfering with the operation ORD? Better yet why does ORD not maintain its database so these phantom elements are not created. Please elaborate.
https://bentleysystems.service-now.com/community?id=community_question&sys_id=4d3ca7fd1badce10f3fc5287624bcba9
There phantom element appear in Bentley communities as a problem. Here is a link to just one workaround and by our experience does not always work. https://bentleysystems.service-now.com/community?id=kb_article&sysparm_article=KB0019636
We have many DGNs that appear to have phantom elements. That is elements that don’t display but ORD still appears to see.
Case 1: When moving the pointer over one of these phantom elements the element flashs on the display. At times they interfere with real element selection.
Case 2: I have a DGNs where I am trying to delete old feature definitions because they will not sync to the library definition and are out of date. So, I try to delete them from the DGN standards and add them back from the library. I have several DGNs that I cannot delete these feature definitions because ORD says they are in use, but there are no elements in the DGN. So, I believe it is these phantom elements that hold the feature definitions. Bentley support confirmed that it these phantom elements. It is also in these DGNs where these feature definition/phantom elements are causing failure of annotation – also confirmed by Bentley.
Case 3: This is not so much of phantom elements but instead elements that have broken rules, Red X, that are preventing them from being selected for deletion.
Why wouldn’t you not want to be able to delete phantom elements that may or may not be interfering with the operation ORD? Better yet why does ORD not maintain its database so these phantom elements are not created. Please elaborate.
Can you elaborate on why you'd like this tool? When would such a tool be useful?