[ORD R2] Doubling corridor elements

RE: [ORD R2] Doubling corridor elements

Alex Badaoui — Wed, 28 Aug 2019 19:28:46 GMT

Does this issue occur when creating corridors in a pure 3D environment, not creating them in a 2D, and having the software create the 3D for you? I have not explored ORD Connect as extensively as others on this post, but this method of building corridors in a pure 3D environment has worked very effectively in the SS4 series of products.

RE: [ORD R2] Doubling corridor elements

JeremieDL — Mon, 26 Aug 2019 00:46:21 GMT

Same here,but this is a first with this release: duplication of bad corridor 2D elements.

RE: [ORD R2] Doubling corridor elements

Mark Shamoun — Sun, 25 Aug 2019 13:09:58 GMT

Hi Kevin,

Are these defects for the 3d features and meshes only? Anything for duplicated 2d corridor geometry that we're also seeing in some circumstances?

RE: [ORD R2] Doubling corridor elements

Mark Shamoun — Sun, 25 Aug 2019 13:08:46 GMT

Hi Chase,

We're also getting some instances of duplication happening with 2D corridor geometry?

RE: [ORD R2] Doubling corridor elements

Chase Barbarick — Fri, 23 Aug 2019 18:40:53 GMT

To get rid of the mesh that it creates all you have to do is go to the 3D model and delete it as well as any other random 3D elements. To me the defect is not that it creates this mesh but the fact the mesh doesn't remember what it was created from and doesn't update when the corridor is altered.

RE: [ORD R2] Doubling corridor elements

Warren McLachlan — Wed, 21 Aug 2019 07:01:17 GMT

It would be really useful to see a list of defects, both outstanding and fixed.

We have teams looking to us with issues, asking if they're known or when they're going to be fixed.

RE: [ORD R2] Doubling corridor elements

Krzysztof Jedrych — Tue, 20 Aug 2019 19:35:34 GMT

Thank you Kevin. Is this list of defects available somewhere? Is there a list of fixed defects in last update?

RE: [ORD R2] Doubling corridor elements

Kevin McDonald — Tue, 20 Aug 2019 14:00:46 GMT

As an update, the development team has been able to reproduce this issue and is working now to provide a fix. I'll update here when we have something.

We currently have a few different defects in our database reporting this issue, for Krzysztof I have attached your data to Defect 1049753. Others you might see referenced are 1049160, 1048193, or 1049088.

RE: [ORD R2] Doubling corridor elements

Krzysztof Jedrych — Tue, 20 Aug 2019 08:59:05 GMT

We are struggling with it for a long time now. My SRs are not responded. I guess we won't find a way to solve this until next, I hope, update. Otherwise someone would have find a way.
As Mark said, it is terrible waste of time and money during live project delivery. Aren't we just too much naive to put too much trust in "improvements" in releases?

RE: [ORD R2] Doubling corridor elements

Adam Wieczorek — Tue, 20 Aug 2019 08:51:59 GMT

It is like a ghost from the SS3 when Openroads Technology was introduced. It was fixed and now it is back.

I sometimes feel like I've been in the Early Access Program since 2012 and ORD is still a Minimum Viable Product. Hopefully it will get better and more reliable with every release.

RE: [ORD R2] Doubling corridor elements

Mark Shamoun — Tue, 20 Aug 2019 08:40:50 GMT

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

RE: [ORD R2] Doubling corridor elements

Krzysztof Jedrych — Tue, 20 Aug 2019 06:17:55 GMT

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.

RE: [ORD R2] Doubling corridor elements

Warren McLachlan — Tue, 20 Aug 2019 06:10:20 GMT

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.

RE: [ORD R2] Doubling corridor elements

Lucas — Mon, 19 Aug 2019 06:56:31 GMT

I have the same problem. Do you find any solution?
I´m thinking to came back to a previous version where the corridors works.

RE: [ORD R2] Doubling corridor elements

JeremieDL — Sun, 18 Aug 2019 16:27:26 GMT

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...

RE: [ORD R2] Doubling corridor elements

Mark Shamoun — Sun, 18 Aug 2019 15:43:58 GMT

Same here, Definately started with Update 7. Template drop edit related but may also be profile, but haven't had the time to get to the bottom of it as were trying to deliver live projects. LEVEL ELEMENT DELETE is all we can use that works but very messy for project delivery.

Pretty fundamental bug that needs an urgent resolution...

RE: [ORD R2] Doubling corridor elements

Krzysztof Jedrych — Sun, 18 Aug 2019 08:02:40 GMT

Hi,

exactly, I also think that it is something concerning template, however many times my colleagues got this issue simply by changing profile. The whole road model was doubled then. I also think that it started since Update 7 but I cannot recreate the workflow of this problem for couple of months.
As for deleting method the one you mentioned is the only one working. We have to use it but, come on, every time I process corridor I cannot think about what is doubled and search through the whole file. I cannot make a new file every week because something got "infected". ORD is terribly slow even without it.

RE: [ORD R2] Doubling corridor elements

Ross Brown — Sun, 18 Aug 2019 00:17:30 GMT

Hi Krzysztof

I am also seeing this happen in release 2 2019. It appears to be when editing the template in some way, one time it was swapping to another template that caused it. I have yet to nail the work flow that will cause the bug.. It is very very concerning that this is happening in the software. The way I remove them from my corridor is place the lines and components on a new level e.g. 1_dump and then use this key-in level element delete 1_dump

Ross

RE: [ORD R2] Doubling corridor elements

Krzysztof Jedrych — Fri, 16 Aug 2019 15:17:17 GMT

Thank you for answer. I have sent it in private messsage.

RE: [ORD R2] Doubling corridor elements

Kevin McDonald — Fri, 16 Aug 2019 13:52:09 GMT

Hi Krzysztof, What was the SR # that did not get a response. The first thing I'd want to do is get the files from you that show this problem. I can follow up with the assigned analyst to make sure we're looking at it.