- Category Properties BYLAYER, overrides BYENTITY - This deals with differences between elements that have the same layer assignment but "look" different in Revit for some reason)
- All Properties BYLAYER, no overrides - This forces all exported elements to be bylayer which will change line patterns and colors so that they ARE By Layer)
- All Properties BYLAYER, new layers for overrides - This allows Revit to create a new layer when an element has a representation that a single layer will not support)
If you choose the second option you get a solid line for both circle and line which doesn't look so good when you see it or print it.
The last option will create a new layer for the Grid Line, S-Grid-1. You end up with S-Grid for the circle and text and S-Grid-1 for the grid Line. All the elements are By Layer.
If you are still with me, a little reminiscing... I remember a few years back (late 2004 or early 2005) when Jim Balding, my boss when I worked with WATG, and I were on a conference call with David Conant (Autodesk Revit Product Designer) for a couple hours discussing exporting to DWG.
We had just been through a fairly harrowing experience getting dwg files just so for an overseas client that was going to take over the project for construction documents. We even had our in-house programmer and cad manager in Honolulu, Danny Polkinhorn, create a clever little application to redress the dwg files after they were exported from Revit. He affectionately dubbed it "Revit DWG Fixer". One result of that phone call with David was these three options I just wrote about. I'm sure others echoed our desires but the result nearly matches what we expressed then. Not the solution but that we experienced these kinds of layer issues. The solution gave us an option that worked, for us at least. We usually chose Option 3...I still prefer it.
To digress a bit further, it is important to understand that the intended purpose for exporting to dwg is to create files that can be used as a background for other trades. It was never really intended to be a better way to make dwg files. Not to make files that a native AutoCAD user could just continue to work on as if they started the work themselves. The resulting files are not created the way a native AutoCAD user would create them. It does a really good job of getting close. Kind of like me claiming to speak Spanish. I know a few words but a native speaker will catch me in the lie pretty quick.
One practical example, AutoCAD users will usually create an overall floor plan file for each floor of the building. Partial plans are derived by using a sheet file that has the overall plan as a external reference (xref). The partial views are showing some of the same overall floor plan file and the viewport is adjusted for the correct scale and location.
If you export the same kind of information from Revit you don't get the same configuration. You get a sheet file referencing a model file that is the literal export of what was visible in the partial view in Revit. This means changing the dwg file of a partial plan is not really changing any other information in any other dwg files. There is an expectation that it does...but it does not.
Rather than driving Revit to create better and better exports I'd prefer that AutoCAD got smarter about extracting what it wants from a Revit model. Consider the goal really isn't for a Revit project to end up as dwg files. Dwg files are really just a common format that lets other firms that are not using Revit interact with the project using their own software choice.