If you came up on AutoCAD, you already know the Overlay vs Attach rule. Attach nests. Overlay doesn’t. Attach drags every reference below it into every drawing above it. Overlay stops at the file where you made it. Most of us learned to default to Overlay years ago, and for good reason.
In plain AutoCAD, that rule was nearly the whole story. Two drafters could overlay each other’s files for background linework and the worst you got was some visual clutter. AutoCAD would warn you about a circular Attach, people clicked through it, things got flaky, but a mutual Overlay between two linework files was mostly harmless. That’s the instinct a lot of us carry around: Overlay is the safe button.
Civil 3D keeps the rule and adds a curveball.
The second reference system the Xref palette won’t show you (currently)
Civil 3D drawings don’t just reference each other through Xrefs. They reference each other through data shortcuts. Your grading file consumes the EG surface from the survey file. Your corridor consumes alignments from a design file. Your pipe drawings consume surfaces from grading. Drefs are real dependencies, they drive geometry, and none of them show up in the Xref palette.
So every Civil 3D project has two reference graphs stacked on top of each other. The Xref graph you can see, and the Dref graph you mostly can’t. The curveball is what happens when a loop forms across both.
The mixed loop
Imagine this, Grading.dwg consumes the EG surface from EG-Surface.dwg through a data shortcut. That’s a real dependency: Grading needs EG-Surface to build itself. Then someone overlays Grading back into EG-Surface, just for background linework, just for context. In vanilla AutoCAD this would be a nothing move.
Here’s what actually happens. The Overlay still loads the Civil 3D objects inside Grading for display. And Grading still has its own Dref dependency back to EG-Surface. The Dref doesn’t become a new shortcut reference in the EG drawing, but it doesn’t need to. The EG drawing now references a consumer drawing that already depends on it. A Dref one direction, an Overlay the other. The loop is closed, and neither reference looked wrong on its own.
That’s a mixed loop, and it’s the most critical problem your reference structure can have. Every open and regen chases dependencies in a circle. Open times stretch. Regens crawl. Data shortcut syncs can become unreliable, rebuilds can slow down, and crashes become harder to diagnose. And it lands on whoever touches those files next, usually the person who did nothing wrong.
An Overlay loop is lower risk when both drawings are only linework. Once Civil 3D objects and Drefs are involved, the risk changes. Your AutoCAD instinct says Overlay is safe. In Civil 3D, Overlay is safer than Attach, but it is not a free pass.
The rules still hold, plus one
Everything you learned in AutoCAD still applies. Overlay for anything someone else will reference. Attach only for the narrow cases: controlled deliverable packaging where the full nested tree is meant to travel together before binding or transmittal, standalone files with no downstream consumers, intentional nesting you fully control end to end.
Civil 3D adds one rule on top. Before you overlay anything into a drawing that publishes data, check what the file you’re grabbing already consumes. If it consumes from you, that innocent Overlay just closed a loop. The Xref palette won’t show you the whole picture. The Dref side of the graph is where the curveball comes from.
Know what your drawings carry before you reference them anywhere.
Cheers,
Shaan