We use to be able to delete some corrupted elements (because that do happen with corridor element and or civil geometry) using the command key-in "civil display browser" but now it only display bad elements. Now what is the way to do?
The civil display browser wasn't intended for users to be able to make edits and modification to elements or objects in a file. We certainly know there are times where this tool was used by users and was successful in resolving problems, but there are also other instances where this was a cushion for users and they would go in and just repair relationships and delete information from the civil display browser, thus causing more harm than good. There are times where we could use that to troubleshoot corruption in a file and if you run into a case where you cannot find the root of the issue and resolve conflicts and such through the available tools, please let us know. We would love to get a dgn or dataset if there is corruption in the file so we can troubleshoot and test to improve on the options we have in the program.
Please let me know if there is any follow-up necessary if you have corrupt data. I would be more than glad to file a defect.
https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/114971/openroads-civil-display-browser-and-one-element-s-profile-model-crash-in-one-ss4-file/352658#352658
For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki
This is an answer is unacceptable. Most users that search these forums understand the power of design intent and how the rules work. This tool is used when the inevitable change happens and we are trying to avoid losing all of our work. Instant crashes when selecting an invalid element is bad enough, not being able to fix it is worse. The key-in is already hidden and is not something you stumble upon when using the software. Our business is too fast-paced to send a corrupt file to you every time we have an issue.
OpenRoads Designer 2022 R1 | MicroStation CE Update 17 | ProjectWise CE 3.434
I completly agree with you, I have spent so many hours just for deleting corrupted entity. And also I never got an email adress to send corrupted files.
Although I agree, shouldn't the software be healing or stripping invalid rules/relationships instead any way? The instances of corrupt elements is completely resolvable by some fixes to the software if you ask me.
Regards,
Mark
OpenRoads Designer 2022 R3 (10.12) | Microstation 2023.1 | ProjectWise CE 3.4
except it doesnt. I still get corruptable elements and then I'm hosed. I need to delete, rebuild, or start over. Wo we need an equal or better replacement.
That is a great idea. Self-healing relationships would solve almost all issues with file stability and corruption. I would only ask for a notification or log of these changes so we can track them. This way you don't assume a rule is still holding its original design intent if it is broken.