there is an ORD's problem which I cannot solve for a very long time and since I did not get any response from Bentley on my SR the Communties is my last chance. I implemented ORD in quite a big project (12km of expressway) so we have plenty of road models. Most of them after reproccessing the corridor leave old elements. Sometimes these are lines, sometimes mesh components and sometimes everything. It's very annoying because I cannot find the reason for this and almost everytime it's something different. I thought that maybe clipping elements mess with corridor functionality (they do but in a different way), but after few tests I have excluded them as a reason of doubling corridor elements. Our team is terribly frustrated of losing precious time because most of the times the only solution is to make a new clean, file, which will be infected after few weeks or even days.
Is there anyone who had similar issues or knows something about this defect? I would be grateful for any reponse.
Also what we do is set our corridor to have a feature definition where everything is turned off so we can spot those elements quickly. On my side It happen most of the time because of profile, often instead of using the complexe redefine command, we just explode the profiles do the modifications then recomplexe everything. It's after those modifications that often I notice the corridor ''corruptions''. But again there may be other things...
I have the same problem. Do you find any solution?I´m thinking to came back to a previous version where the corridors works.
We're having the same problem here. Random stray Additional 3D Linear Elements that refuse to delete.
In the example below (brand new dgn, new corridor, not many edits done), the 3D element for my shoulder road marking (upper cyan line) stayed behind when I assigned superelevations to the corridor. I cannot delete the element that shouldn't be there.
Try the method mentioned above. Place the old, doubled line on separate layer and the type Key-in: level element delete "Layer_name". This will delete all elements assigned to that layer. It's only temporary because probably during next corridor processing something else will be dooubled.
Anyone have any idea how we can stop it happening? Any SRs in for this one - its turning our models into a mess during live project delivery
OpenRoads Designer 2020 R3 (10.09) | Microstation CE Update 15 | ProjectWise CE 3.4