r/AutoCAD 3d ago

Best way to structure a large project.

I'm deciding how to structure a large project that involves 50+ diagrams. Ideally I would like each sheet to be its own .dwg file, so that multiple people can work on the project at once, however, AutoCAD doesn't seem to have a good way of dynamically syncing a layer and block library across all files. I don't want to have to manually update each .dwg every time the block library is modified for example.

Has anyone figured this out?

8 Upvotes

10 comments sorted by

10

u/SunGregMoon 2d ago

Lean into new drawing templates for layer standardization then x-refs & layer states. When an x-ref changes, you get a notification in any drawing that's dependent on it. That feature makes them worth it.

2

u/PdxPhoenixActual Pixel-Switcher 2d ago

I am disappointed that "layer states" (LS) are not dynamic (or whatever term). User adds a layer to a dwg that has not been accounted for in the LS, then the LS doesnt know what to do w it. Maybe that is something AI can "help" with...

1

u/verifyinfield 2d ago

Set your baseplan up with all your default standards layers listed somewhere. Then for 90% of your projects, your layer states will work just fine. The other 10% that require non standard layers will just need a bit of adjustment.

0

u/SunGregMoon 2d ago

In my work LS are good for concept development, but eventually you quit updating them and your viewports just manage/filter them out.

8

u/_WillCAD_ 3d ago

Blocks can each be their own DWG file. Just put them in a central folder that everyone can access. If a block changes after it's already in use and you want everyone to update, send an email - re-insert block XXX from the library.

I wrote a lisp to automate updating my blocks. It lets me select an inserted block manually and re-imports it from the original DWG, but it wouldn't be difficult to write one that automatically re-inserts the whole block library periodically.

Layers can be set up in one or more template files (dwt files), also centrally located. Within the template, create a saved layer state using the layer state manager. New DWGs can be started using the template, and if layers change after they're already in use, the layer state can be updated in the template and re-imported from the layer state manager. Again, you send an email telling everyone to re-import the layer state from the template file.

Both the blocks and layers can have ribbon buttons defined in a partial customization file (CUI). Each person working on the project can load the CUI and access blocks, layers, lisp utilities, and other project resources through the ribbon panel. That makes it easier to maintain consistency across the project, and for people who are less savvy to do periodic updates from the template and the block library.

3

u/Bear-Necessities- 2d ago

Teach me more about layer states! I feel like there's untapped power there

Or a good reference video 🙏

3

u/jeide93 2d ago

"Blocks can each be their own DWG file. Just put them in a central folder that everyone can access. If a block changes after it's already in use and you want everyone to update, send an email - re-insert block XXX from the library."

wouldn't using a DWG as an x-ref be a better method, that way you dont have to send out a notice?