Layer Merge Damage on a 60-Sheet Courthouse Set
An eight-person architecture team is midway through a 60-sheet courthouse renovation using a firm template, A1-2025.dwt, which defines 52 layers, six layer filters, and three saved layer states: Plan, RCP, and Demo. A consultant delivers a base plan containing 140 layers with AIA-style names but different modifiers. To reduce clutter, a junior drafter runs LAYMRG on every A-WALL-* layer into a single A-WALL layer and purges the rest. Two days later, the project architect notices that fire-rated and non-rated partitions plot with the same lineweight, the Demo layer state no longer hides new consultant layers, and several sheets contain direct model geometry on layer 0. The client standard requires discipline-based layer names, no layer 0 geometry outside block definitions, and a 0.35 mm lineweight for rated walls. The team has 18 working days before issue.
1. What immediate checks and repairs would you perform after the LAYMRG operation, and how would you restore the rated/non-rated distinction without redrawing the plan?
Read the worked answer
First determine whether the merge was saved and whether a pre-merge backup, autosave, or the consultant base file is available. If not, the distinction may be unrecoverable from merged geometry alone unless rated walls are in blocks with attributes or on a hatch/object property. Use QSELECT and Properties to check for object-level lineweight or color overrides that survived; do not assume ByLayer values remain. Recreate A-WALL-RATED and A-WALL-NR layers from the template, then reassign objects using a selection method tied to fire-rating data, block attributes, or a new hatch boundary. For layer 0, isolate direct model geometry and move it to the correct discipline layer, leaving only block-definition geometry on layer 0. Restore the 0.35 mm lineweight in the layer definition and verify with a plot preview at the sheet scale. Update the Demo layer state only after the layer set is stable.
2. Design a layer translation and standards workflow for the remaining consultant files so this does not recur.
Read the worked answer
Build a layer translation table from consultant names to the firm standard and save it as a .dws or LAYTRANS mapping file, rather than using LAYMRG. In each host drawing, attach the consultant file as an XREF, use LAYTRANS to map layers, and keep VISRETAIN set to 1 so host overrides persist on reload. Apply layer filters and saved layer states to control Plan, RCP, and Demo views. Add the mapping to the template and the project standards checker, lock standard layers, and require the consultant to deliver a layer list before issue. Purge only after translation, and audit a sample sheet before applying the workflow to all 60 sheets.
3. The saved layer states do not include layers added after they were saved. How should the team update layer states across 60 sheets, and what is the risk of applying an old state?
Read the worked answer
Layer states store the properties of layers that existed when saved; layers added later are not in the state. Restoring an old state can reset colors, lineweights, plot settings, or freeze/off states on current layers, and if the layers-not-found option is used it can turn off new layers. Update the three states in the template after the final layer list is fixed, export them as .las files, and import/restore them per sheet type. Apply the state while no viewport is active, then check each viewport for VP Freeze overrides. Never restore an old state over unsaved work; save a copy first and compare a plotted PDF.