PDA

View Full Version : Using Acad details - "Best Practices"



Steve_Stafford
2004-06-17, 04:07 PM
I was preparing a short discussion for our local Revit user group meeting (LUG) to cover detailing with Revit. While not an expert at detailing as an architectural person by any means I have spent a fair amount of time working with acad details and microstation too...the following applies to AutoCAD detail files specifically but most will apply to Microstation as well.

This list was also assembled assuming that "you" are not abandoning the acad files in favor of Revit only based details. These tips will help you keep the details portable and useable in either application.

First, stay focused on your goals and choose common ground that helps you achieve them. Avoid statements that start with; "I can't..." We can't..." "I won't...."

Font and Dimension Tips:

DON'T use a width factor other than (1) in AutoCAD text styles (Revit now supports width factors in text and dimension styles but may not import them initially)
DON'T use custom symbols that aren't also present in the TTF font.
DON'T use a custom leader routine and/or custom arrows/terminators


DO use a TTF font in AutoCAD OR
DO use Revit's shxfontmap.txt to map shx fonts to a TTF font in Revit)
DO use the dimension leader object in AutoCAD
DO use a standard arrow or dimension terminator
DO make sure that blocks with attributes follow these rules too
Project Mgmt and General:

DO put details in a project specific location and don't move them
DO Import and link details and check the "current view" option
DO consider a separate detail project if you are dealing with a large multi-building project
DO manage them in "one" place, for consistency (AutoCAD since that's what were talking about here)
DO use a detail specific layer structure to manage lineweights more easily if required
DO make sure your details are located near 0,0 (origin)
DO use custom programming routines to automate changes these tips require
DO make sure drafting views use the same scale as the imported detail


DON'T move the details once linked
DON'T explode details (change them in Acad, if you want to keep them useable for both)
DON'T put multiple details on one AutoCAD file. One detail per dwg file (added per Brenehan)
DON'T have temporary details and sketches off to the side of your AutoCAD detail file (added per Brenehan)
DON'T import cad Details that have attached xrefs (added per Brenehan)

If you follow these "rules" you will find that you can, nearly always, import a detail "as is" and minimize rework on libraries that will likely remain available for both applications. (stay dwg that is)

All for now...

Scott Hopkins
2004-06-17, 05:10 PM
Thanks Steve - Good Tips!

Wes Macaulay
2004-06-17, 08:51 PM
Yeah - super stuff, Steve. Very handy and good to know...

Phil Read
2004-06-17, 10:41 PM
DO link (and import) "Current View Only"
DON'T explode
.02

-Phil

Steve_Stafford
2004-06-18, 12:14 AM
DO link (and import) "Current View Only"
DON'T explode Well said and I've amended the list accordingly...thanks for "proofing", Phil! 8)

jontramos
2009-02-10, 04:02 PM
Hi Steve,
Any Do's / Dont's for hatching? Sharing .pat files between Revit & ACAD?

- Jon

Steve_Stafford
2009-02-11, 02:10 AM
Hi Steve,
Any Do's / Dont's for hatching? Sharing .pat files between Revit & ACAD?

- JonWow, this is an old thread! Um...avoid really dense patterns or really large patterns, they seem to annoy Revit when importing them as part of a dwg detail file. Revit also doesn't really like those really short lines so if a boundary of a hatch has a really short line segment it may also object to the hatch as being "unbounded".

RevitRonin
2009-06-01, 06:05 PM
Hi Steve,

I've heard that placing AUtocad details in Detail Component Families will improve performance.

Since this is a more cumbersome workflow that does not allow linking of the detail I'm wondering if you can confirm or deny the rumor?

Thanks

Eric

brenehan
2009-06-02, 12:22 AM
DON'T put multiple details on one AutoCAD file. One detail per dwg file and view to allow full view cross referencing if required.
DON'T have temporary details and sketches out to the side of your AutoCAD detail file.
DO import all your AutoCAD files on a specific Autocad drawing workset.
Avoid importing cad files with attached xrefs.

Steve_Stafford
2009-06-02, 06:41 AM
Hi Steve,

I've heard that placing AUtocad details in Detail Component Families will improve performance.

Since this is a more cumbersome workflow that does not allow linking of the detail I'm wondering if you can confirm or deny the rumor?

Thanks

EricHey Eric...how's Dallas?

I've put cad details in Detail Components as a way to deal with a good many "line as inaccurate direction..." errors and such. One cad detail per detail component and the detail component is placed in a drafting view. The annotation won't come across so it will have to be added to the detail inside Revit. It isn't a pretty solution but it avoids having to spend time resolving mess lines that generate errors when you try to sketch over them with Revit linework or worse...explode the detail. Isolating the cad detail in a detail component traps the errors there...or at least they don't show up in the Review Warnings report in the project. I think the Baylor team did this to remove a good many warnings at one point as a stop gap measure until the details could be "Revitized".

Steve_Stafford
2009-06-02, 06:49 AM
DON'T put multiple details on one AutoCAD file. One detail per dwg file and view to allow full view cross referencing if required.
DON'T have temporary details and sketches out to the side of your AutoCAD detail file.
DO import all your AutoCAD files on a specific Autocad drawing workset.
Avoid importing cad files with attached xrefs.
Added these to the list with attribution...thanks! I didn't include the workset item since cad files imported into drafting views are assigned to the view workset and not assigned to a user created workset. Only files that are imported without checking "Current View Only" are affected in this case.

kenmarcus
2009-06-03, 09:04 PM
Hey Steve,

great list. Came across another Don't for your list recently

DON'T use polylines for Arrowheads.

Had a client that used polylines to control start and end weight to look like an arrowhead, when import, lose all of the weight and was just a single angled line. Had to replace all of the arrowheads.

Steve_Stafford
2009-06-04, 12:31 AM
Yep, that's actually covered under the don't use custom routines for leaders...they usually use polylines for them. For Revit to really understand the leader it needs to be a native Acad leader element.

luke.s.johnson
2009-09-30, 11:15 PM
I found that I had problems using LEADERs and MTEXT - wrapping didn't work properly when linked into Revit.

I fixed it by exploding MTEXT to DTEXT and replacing the LEADER object with an MLEADER object with no text - not a great solution, but it suited our problem.

If you need to edit the DTEXT later, you can use the Express Tool to convert back into MTEXT before editing...

I blogged about it at:
http://whatrevitwants.blogspot.com/2009/10/tips-for-linking-autocad-details.html