Gaps in the exported corridor to Civil View

[stardust1611]

Hi. I created a curb subassembly with a curve segment in a corner, and created a corridor with this subassembly. Then I tried to export it to 3DS Max Design Civil View, but there is a gap where the curve is supposed to be. The curve has 8 segments, and when I import the corridor surface to 3DS Max everything looks fine, but when I try to import the corridor itself, there is a gap. Can anyone please tell me what is going on?

[Yonas89]

I consider it as  a corridor bug. Try to extract solids from your corridor and  take a look if there is a gap at the same place. I think it's not a civil view export issue. 

[stardust1611]

Hi Yonas, thank you for replying. You are right, I extracted solids from the corridor, and there is no gap on the solids. I attached two screenshots, one showing the solids and the other showing imported corridor in 3DS Max. The solids look like the corridor surface, exactly as they are supposed to be. The same is happening in Civil 3D 2013 and 2016.

[Yonas89]

No I was not right, I thought it's a problem with corridor. However, do your curb links have code? If it doesn't then this might be the problem, because civil view looks for link codes

[stardust1611]

Yes, I added link codes. The curve has "Top" and "TopKerb" codes. I'm exporting the links with the Top code, therefore the curve should've been exported as well. It would be easier if I knew at least what app is creating this problem. Is the problem in Civil 3D or in 3DS Max?

[Yonas89]

Aaa, ok very good. I still think that the problem is related with transferring data from Civil 3d to Max and not with the civil view itself. I can see that the curb arc is very smooth (L8). Again, just guessing here, but my advice would be to play with tessellation parameter in SAC.  Maybe it's the case here. When you create TIN surface of Top links, do you get any problems with this part? 

[stardust1611]

I tried. I reduced tessellation from 8 to 3, but it didn't help. Corridor surface looks perfect, no gaps in it.

[Yonas89]

could you share sac file and dwg file here? would be much easier if i could check it by myself

[stardust1611]

ok, here you go. Subassembly was created with SAC 2013, but I think I opened it and saved it last time with SAC 2016. DWG was created with Civil 3D 2016. My version of 3SD Max is 3DS Max Design 2014, but the same is happening on 2015 as well. I had to zip the PKT file because the web site didn't allow "a zipped file with altered filename extension" to be uploaded on the forum.

[Yonas89 · Accepted solution]

ok, the only conclusion I can say is that it's problem with arc element of your curb and Civil view itself. It looks like civil view cannot read arcs, that's why i said about tessellation value before. If you would add a straight line instead arc it would work. I think civil view needs to see points on both sides of link. Like it's said in definition: link is the connection of 2 points( or something similar), but in this case the arc element is created of multiple lines between 2 points and you control the number of lines through tessellation property. I don't know how civil view is built but it does not recognize those lines and don't consider them as links. That's why you have manually create arc of multiple links in SAC( see the image below).

And you get the result: 

[stardust1611]

Hello Yonas, thank you very much for your efforts to resolve this problem! I'll accept your answer as the solution since this seems a good workaround, and no one else has responded anyway. But, I would like if someone from Autodesk would respond and give a definite answer whether Civil View can read arcs, fillets and daylight roundings or not.