Data Referenced Corridor Code Set Style not working properly

[kovacsv1]

Hey Guys! 

In a quite big project (33 km new highway and related roads) with 5-6 road designers working on it, we figured out a workflow which seems to fall into pieces.

The whole project is in separate model files, we dref everything, and there are clean files (so there are no drafting lines to delete and using the final style, annotate etc.) for only output purposes (export, printing etc.)

The problem is that the corridors do not appear the same in the model files(dref host) and the output(dref client) files. Same code set styles are used in both files via style referencing, and the host file works perfectly, but in the client files, at corridor region ends the feature lines switch sides for unknown reasons, even though the codes don't change. Links and surfaces work perfectly only feature lines go crazy. We use custom pkt subassemblies, but we could replicate the problem with built in elements.

I attached some images to understand the problem.           

Has anyone met this anomaly or has any idea what's wrong?

I'm a long time surfer, first time poster here and english is not my native language, so please be gentle. 🙂

  

Thanks in advance.

[DKathy]

Here is a sample about the problem:

[cwr-pae]

The issue is only when changing from assembly 3 to assembly 1. You can try to correct this by changing the settings of the Feature Line tab of Corridor properties (see image) or recreating the assembly - (3) being careful of left/right side insertion. If not, as work arounds, in those areas use offset alignments and target the preceding/following regions or change edge of lane way code to edge of pavement lane on one side of all the assemblies.

[DKathy · Accepted solution]

The Autodesk Support team find the solution.
You can find it here:
https://knowledge.autodesk.com/community/screencast/66b91fe4-1e90-481a-824f-addc3a9a94c2

1. Delete the refrenced object.

2. Edit the corridor feature setting here, and switch it to NO.

3. Create the reference again.
Thank you for Wojtek Garczewski for the solution!

[Wojtek_Garczewski]

Hi @DKathy 

Thanks for putting the solution here. I will  "Accept as Solution". This helps everyone find answers more quickly!

If you will have any other questions, please let us know! 

Thanks,
Wojtek

[kovacsv1]

I just wanted to post the solution @DKathy  sent us. Thank you for the solution @Wojtek_Garczewski.

[Bill-Paddock]

Hello, Using v2019 this fix does not resolve the problem for me. It's happening to multiple different corridors from different source drawings. Been troubleshooting this for days. Is there anything else I can try?

This is the source corridor.

This is how it looks when data referenced.

Thanks

[Wojtek_Garczewski]

Hi @Bill-Paddock 

Did you try to delete xrefs, change mentioned setting, then add DWG as XREF again?

Can you share sample data where that occurs?

Thanks,
Wojtek

[Bill-Paddock]

Wojtek,

thanks for the reply. I assume that when you say "Xref" you mean "Data Reference" so yes, I have detached and reattached per the instructions provided in the fix. It just doesn't work on my end.

I've attached a simplified version of the source corridor and a drawing that has it data referenced so you can see the error. This is happening in multiple different corridors/drawing files. I have even rebuilt the whole thing from scratch and still get the same result.

[Wojtek_Garczewski]

Hi @Bill-Paddock 

Yes, DRefs. Thank you for the heads up.

Thank you for the files. I will check on that and let you know about my findings.

Regards,
Wojtek

[Wojtek_Garczewski]

@Bill-Paddock 

I've noticed you are using some custom subassemblies. (Shouldering_Daylight_AltAndVert_NR_2014_v4_02)

Can you please share that one (PKT file) so I can fully reproduce your drawing on my end? Thank you.

Wojtek

[Bill-Paddock]

Here is the subassembly. Change the file extension to .pkt if you want to work with it that way. It would not let me attach as a .pkt file.

[Wojtek_Garczewski]

Hello @Bill-Paddock 

Thank you for PKT file. I did reproduce your issue. 

In this case, changing the branching method to Outward solved the issue. Please see:

Regards,
Wojtek
______________________________________________________________

If my post answers your question, please click the "Accept as Solution" button. This helps everyone find answers more quickly!

[Bill-Paddock]

That did it. Huge help. Thank you! I don't think I can accept as solution since it wasn't my original post. Sorry for the hijack 😉