Community
How practical is it to create and manage surfaces across multiple DWG files? One of the reasons I'm asking is some of our users are insisting their work can only done in a single file, resulting in massive DWG files and naturally, Civil3D slows to a crawl. I'll admit I'm not a full time Civil3D user or specialist - thats not my job. I'm reasonably certain it can be done from the most basic of research (which apparently nobody else wants to do...), but am UNcertain what the potential pitfalls are.
They complain of slowness and are requesting better computers from IT (I've talked them down to more RAM). I'm trying to forestall a potentially nasty political situation spiralling out of control: they get better computers, others will want them as well and either get them only because of connections, or won't get them and are resentful for the perceived lack of importance. We don't need people doing 2D schematic drawings on gaming rigs...
----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
I can't say I am a paragon of efficiency (because I am not), but I have very good success with multiple files. For instance; I have been working on a 10 ac site and until I broke my surface definition into components I was dead in the water.
There is a short coming to it though - you do tend to flip through various files when your in file A and see something that needs to be changed in file B and so on, but the lower overhead has payed its dividends.
I've have gotten bit by a few surfaces pasted into one and they may rely on another and I have found myself opening files to get DS to update. But I'd rather not have all my eggs in one basket if you get my drift.
Your Name
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
It's impossible to work with a large data set in a single file. When they insist their work can only done in a single file they are just wrong. Drawings MUST be split up if they want any semblance of performance. You can have the best PC in the world, but if you're not walking the line you're going to have performance issues.
It may sound harsh, but they just need to suck it up and learn how to use data shortcuts. Indeed, there are some management issues, but once documented and taught to the users, they can easily be managed.
Matt Kolberg
SolidCAD Professional Services
http://www.solidcad.ca /
SolidCAD Professional Services
http://www.solidcad.ca /
Ok i'm a loud mouth and I have to add my two cents as well. 🙂 I agree with all of the comments here from some very good contributers.
In my experiance a single faimly home project with everything in one file will slow a core i7's with 12 GB of ram to a crawl. This is not so with data ref's and xref's.
You should check out the Best Practices manual in Help. There is a section on data management. In particular you can try searching this in help. Drawing and Object Relationships
AutoCAD help will also point out the advantages of using XRef's as well.
A typical project in our office has these basic files that all get xref's into sheet files.
existing property lines
existing easements (if applicable)
proposed property lines (if applicable)
proposed easements (if applicable)
exisitng topo (blds, roads, utls, etc)
existing trees, field surveyed. These files can crush performance if you have complex blocks and a large number of trees.
That's a min of 3 files for existing conditions alone. For propsed conditions you may want one file for a FG srf, one for pipes, another for earthwork calcs and so forth. It is no problem managing the data for us. If we need to edit on of the xref's in your file. Select it, right click and choose Open Xref. If we need to edit a C3D object that is Data referenced in you file. Select it. Right click and choose Open Source Drawing.
Now if I need to create a property survey, an existing topo map, a site plan, an as-built. I have building blocks to make all of these sheets. I don't need to have 4 copies of the existing conditions on the server. I don't run the risk if having to update 4 files if the survey crew shoot more trees orr adds more topo to the existing conditions. There can be a lot of storage and data management overhead with everything in one file.
One other thing to add. If you place all of your work in one file and that file becomes corrupt you need to recover all of your work. With references if a file becomes corrupt you need to recover a small portion of your work.
John Mayo
Thanks all, thats very helpful - information is ammunition. I'll have to keep pushing the department head for training as well as nudging the users towards better work processes. Its not like they're doing anything "exciting", just industrial site work in very flat areas. A few access roads, some berms, level site with appropriate drainage, thats it.
Most of our current hardware is HP Z420's (or thereabouts - IT keeps changing their purchases). I don't think there is much of a problem with hardware or drivers, as we have been doing 3D using AutoCAD 3D solids for some time. A decent workflow, appropriate level of detail, and you can move mountains using less than bleeding edge software.
----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
Can't find what you're looking for? Ask the community or share your knowledge.
Post to forums
![Autodesk Design & Make Report](https://forums.autodesk.com/t5/image/serverpage/image-id/1350519iCB55845EBFC43016/image-size/large?v=v2&px=999" "Autodesk Design & Make Report")