Monster projects: detail in the project or in AutoCAD?

[Wes Macaulay]

I only ask because of this: on larger projects the biggest holdup can simply be saving to central. As the file gets bigger, it would seem logical that the length of the process is tied to the size of the file.

So if you add a bunch of 2D details drawn in Revit, that would add to the file's size. So what if you link in AutoCAD details? They'll be outside of the database and not add to its size. I would think that a link is less data than a Revit-drawn detail.

So the idea here is to keep the Revit database as light as possible so Revit can take care of everything BUT the details, and do so as quickly as possible.

Any developers feel like fielding this one?

[bpayne]

Another option I was tossing around in my head was linking a seperate Revit file for just the details, especially typical details.

[Scott D Davis]

Another option I was tossing around in my head was linking a seperate Revit file for just the details, especially typical details.

But then how would callouts point to the detail number/sheet?

[bpayne]

I did say tossing..there's a reason why nothing has settled to the bottom yet.

Note: It's strange posting a reply to someone that sits 20 feet from my desk. Ahhh...technology!

[Scott D Davis]

Are you on that darn AUGI again?? Now get back to work!

[LRaiz]

I only ask because of this: on larger projects the biggest holdup can simply be saving to central. As the file gets bigger, it would seem logical that the length of the process is tied to the size of the file.

So if you add a bunch of 2D details drawn in Revit, that would add to the file's size. So what if you link in AutoCAD details? They'll be outside of the database and not add to its size. I would think that a link is less data than a Revit-drawn detail.

So the idea here is to keep the Revit database as light as possible so Revit can take care of everything BUT the details, and do so as quickly as possible.

Any developers feel like fielding this one?

When dwg file is linked (as opposed to imported) Revit still imports all ACAD entities and keeps their translations inside of rvt file. However when opening rvt file Revit will check if linked dwg is still there and if it is modified. If dwg is modified then its contents are reread and re-embedded into rvt. Thus linking instead of importing would not decrease the size of rvt file and is not likely to speed up STC.

On the other hand all view specific elements are kept in a separate workset that corresponds to this view. Details which are view specific will live in their own worksets. Furthermore during STC only worksets that contain changes will travel across network and be saved anew. The structure of workset-enabled rvt file is similar to a folder; it allows rewriting some worksets without rewriting entire file.

Thus Revit is already doing a number of optimizations and I doubt that simple minded end-user tricks will speed up much. But you can obviously try and measure your own mileage.

[bpayne]

Did he just call us "simple minded"? I think he did!

[JamesVan]

How many people on this forum have invented the world's greatest piece of software? I can think of only two members who are entitled to a zinger or two.

All kidding aside, I think that we've got XREF's in mind when assuming how Revit handles links. In Autocad, an XREF will only increase the size of host file by a miniscule amount compared to a regular insert. In Revit, linking only seems to maintain a tether to the original file when compared to importing.

An interesting concept to study is to take a linked RVT project and copy it a few hundred times. I've been told that this will not increase the file size of the host.

[Shaun v Rooyen]

Wes. Our smallest project is just short of 90MB. All documentation is done in Revit, not one ounce in acad. We build a stack of families!

There are two significant things we have noticed with big files:
1.Don't model anything in the project (in place families).Rather build the family.
2. Stay away from lines, both model + detail. rather build the family.
3. Reduce the dwg usage. ie We will bring a dwg in to model the topography. Once done the dwg is deleted. Same applies to existing buildings.We have no dwg's in our projects, what so ever!!!!!!

We have found that by eliminating the fore mentioned we have in some cases cleaned and reduced our file sizes up to 25%. Having said that, nothing is spared when it comes to detail. We have sometimes been criticized for over detailing ( and I am proud to say all done in revit!). What does help though is that we have been on Revit since 4.5 so the libraries to chose from are extensive. Families ARE your Friends!

[Martin P]

Now that it is possible with 8.0 (and I since found out 7.0 too?) to copy and paste an entire detail from a project to a new detail familiy (ie you wont get "unable to copy between project and family" error) EDITED - you cant copy detail detail components though, so I am wrong - its still not great.... - and the ability to automatically reload (and edit) a family within Revit... I think there will be a whole lot of new options open to us all with regards to how we create,store,archive and load details produced within Revit.... havent fully thought through a process yet, but this simple addition has REALLY opened up the detailing (from my point of view anyway..)

Massive advantages I see in 8.0 are........

Details can now be easily turned into families, EDIT - as long you dont use detail components!! - (copy/paste project to family) - separate detail files/families away from the models, a big advantage.....All our details in Revit we will now make into detail (component) families using copy and paste.

We can update them (families) from a know location with new feature in 8.0 -like xrefs or links, but they need to be told to update - so better - ie details in archived files will NOT end up changing unless I ask them to, unlike links/xrefs.......

Details can all be stored in one big file for quick copy/paste into projects.... much better than xrefs/links - find the detail on the drafting view, copy and paste - no need for trawling through loads of weird named details with windows explorer.... Just see the detail you need and copy it.

As far as I can see, my position on Detailing in Revit has changed. I have up until now not detailed in Revit and always in Autocad. We are re-thinking that

EDIT - I was wrong, as I cant copy details into detail families, I wont be doing the above... Sticking with Autocad for now. Maybe 9.0 will finally grant this wish.