Corridor won't tie to another corridor through certain length of template

I am having an issue trying to tie one corridor to another. I have done this before with no problem but for some reason it won't work this time. The below picture is a plan view of the corridor and for some reason it jumps in through a length of the corridor. I have looked and don't have and duplicate point controls. etc and what is weird is the jump happens in the middle of a template.

This is the 3D view and you can see where is jumps in and doesn't tie down:

Cross section view:

The target aliasing looks like this:

Any ideas on what could be causing this?

Parents

0 Offline Nico Roman Wed, May 25 2016 11:36 AM
can you analyze those elements you are targeting and make sure there is nothing wrong with them. Maybe redraw them after a file compress.

http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/19151.video-target-aliasing-and-corridor-clipping

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel
0 Offline Wesley Nyberg Fri, May 27 2016 8:12 AM in reply to Nico Roman

I analyzed the corridor I was targeting and the one that is doing the targeting and nothing looked wrong with them. So I did a file compress on each dgn and reprocessed the corridor and it didn't change anything. I watched that video and that is the way I expect it to work and have used it in the past.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline Derek Schmidt Fri, May 27 2016 10:32 AM in reply to Wesley Nyberg
Is it possible that the referenced corridor is in any way derived from the referencing corridor? It might be in the form of a ditch profile or anything. I know that corridors that would trigger a circular reference would not appear on the target aliasing list as an eligible target, if it was already added to the list of targets prior to the circular reference, it might remain on the list.

Stuff like this is going to be difficult to troubleshoot since source elements can have many derivatives that are impractical to trace.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline Wesley Nyberg Fri, May 27 2016 11:58 AM in reply to Derek Schmidt

ORka311001rbs-22.dgn

ORka311001cor-01.dgn

6138.ORka311001cor-02.dgn

I double checked that the corridor is not derived from the referencing corridor. Well what's really weird is that in the same template in one section it does tie down and in another it doesn't and nothing seems to be different.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline Wesley Nyberg Fri, May 27 2016 12:03 PM in reply to Wesley Nyberg

For some reason it won't post the last file correctly. You will just have to delete the 6138. in the file name.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline Derek Schmidt Fri, May 27 2016 12:03 PM in reply to Wesley Nyberg
It's somewhat alarming that in your cross section screenshot, the corridor on the right is stopping in space. Maybe right-click and hold on that and say edit section. See if you can determine what it's intersecting, or what controls where it stopped. Also, look at that drop's template, to see if that end condition (as both you and I may be assuming it's an end condition, but it might be tricking us) is targeting a surface other than <Active>.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Offline Derek Schmidt Fri, May 27 2016 12:03 PM in reply to Wesley Nyberg
It's somewhat alarming that in your cross section screenshot, the corridor on the right is stopping in space. Maybe right-click and hold on that and say edit section. See if you can determine what it's intersecting, or what controls where it stopped. Also, look at that drop's template, to see if that end condition (as both you and I may be assuming it's an end condition, but it might be tricking us) is targeting a surface other than <Active>.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data