Transition between Assemblies

[Anonymous]

I've attached a screenshot of some "webbing" I have going on between regions in my corridor.  As you can see on the left, there's the start of a left turn pocket lane, which is why I have two different assemblies.  This is just one instance, but this is happening along my entire corridor.  I've given up on trying to resolve and have made gaps in my corridor.  But me being an engineer, gaps bother me and would rather figure out a solution.  I'm wondering if it has anything to do with point codes?  An answer would be greatly appreciated!  If no answer, I'll resign myself to being okay with the gaps.  Thank you in advance!

[tcorey]

This could definitely have to do with point codes. Civil 3D connects like point codes to one another, so if there's a P2, that shouldn't be connecting to another P2, change the point code to something else. If you hover over the feature lines, you will see what point code it's using.

[MikeEvansUK · Accepted solution]

Yes this is definatley the subassembly codes.

There is an option in the corridor props under feature lines section for branching inward/outward. Try changing this and see if it still happens.

This is why I tend to use the generic pavement assembly as you have more control and can change the codes to ensure they are different on all lanes so will not join up like this.

You may have to remake the assembly to correct this.

[Anonymous]

Thanks for the suggestions.

I've been trying to research how to edit point codes.

The inward/outward choice didn't work.

I guess I will have to try the generic links. I don't mind redoing the assemblies.  If it means solving this problem, it will be worth it.

Thanks again!

[Anonymous]

Changing everything to a generic assembly worked!

Thanks all!

Robyn

[Anonymous]

I am having a gap problem can take a look at my screen shot and see if **** the same problem you were having and would I resolve my with generic assemblys?

Thanks