Linked dwg Line Styles and Intersections (Hidden/Dashed)

[Jeremy.Oakes]

Hello Revit Community. I have been searching for a solution to this issue for awhile now and finally decided to post the question here. If I am posting something that has been solved before, I apologize. I really have tried to find this.

Here is my issue. When linking a dwg file and assigning the layer (Category) a "Dash" line pattern the endpoint intersections (confirmed snapped) end up having gaps/voids. I am assuming this is because of the line pattern definition but am not sure.

Below are a few images to help clarify:

This image is a screen shot from AutoCAD.

The red entities are currently on layer "Hidden" though in AutoCAD they have a continuous line type.

Here I have selected polylines on the top entities and individual lines on the bottom entities.

Next image is just showing that the imported object styles are coming in with a line patter set to "Solid":

Next image shows that I change the "Hidden" imported object category to have a line pattern of "Dash":

The next image shows what I end up with. Notice that the way "endpoints" are connected doesn't seem to change based on LWPOLYLINE's or LINES.

Next image. When I create a detail line in REVIT with a line pattern of "Dash" I get the rectangle on the right. Notice how the endpoints do not have gaps like the imported AutoCAD lines.

Does anyone know how to resolve the gaps and have the imported lines display like a REVIT detail line with the same line pattern?

Any help is appreciated.

[kadmonkee]

depending on the use of the AutoCAD linked dwg.

I typically only use the ACAD link as a temporary guide to convert AutoCAD to Revit.

I change all Linked AutoCAD lines to a particular color to distinguish between Revit and AutoCAD 

it might help to change the scale of your working view if it helps with the line gap spacing of the AutoCAD linetype

trial and error, if the line style isn't critical then search for one that suits your needs and use all Revit Line patterns / Style and drop the AutoCAD file when complete.

[BIM-CONG]

It seems that the joined line/pl in linked/imported CAD is treated as a entirety, which behaves like a single line in revit. So the gap appears where dash stopped. I think since the CAD is imported not linked, maybe you could explode it. By this way, all the line in cad will be convert to detail line in Revit as a new line style of each layer in cad. You may clean your dwg file first before this action.

[kadmonkee]

honestly that is a longer process than linking the AutoCAD dwg into a Revit model

it always creates more work in the end , which doesn't always happen after the fact.

if you use the pick lines options to create a revit native line style you will work faster and cleaner in the end.

imho

[Jeremy.Oakes]

Thank you @kadmonkee & @BIM-CONG for the suggestions. These are the only ways I have been able to overcome the issue. I should have added that note to the OP. What I am/was hoping for is a solution that works with dwg links. Redrawing/tracing/pick lines/etc. is what I would prefer to avoid.

[tbrown6608 · Accepted solution]

I know this post is a bit old, but I thought I'd share my workarounds for this as I didn't see them mentioned here and they do work while keeping your CAD files as a link.

If you put the lines on separate layers in CAD, Revit will apply the linestyle to them separately and it will appear the same as a Revit detail line corner. For example on the square image, put the 2 vertical lines on one 1 layer, and the horizontal lines on another. Then just apply the same visibility settings to both layers.

Another way around this is to separate the lines in CAD at the corners by a very small distance. This way Revit will treat them as separate lines since they don't actually connect, but the distance is small enough that it isn't noticeable. I typically don't use this solution since I use the trim and extend commands in CAD often, but it can be a quicker fix.

[Jeremy.Oakes]

Thanks @tbrown6608 

The workarounds work. To bad I have to use bad CAD practices. Oh well. Someday these details will make their way to revit.

[Jhallock!]

I'm working in 2024 and still no solution to this issue.