Friday, June 25, 2010
A couple things to note:
1. Every project will be different...
2. Step #8 (Removing the Architectural Sheets + purge) may be skewed slightly since this is the first purge I did.
3. I compacted the model during each STC. Most of the time, Windows Explorer reported a larger number (typically 2x the "real" size), but a quick refresh (F5) displayed the correct size.
4. The file I worked with was a detached copy of the original central file.
Thursday, April 08, 2010
So, you have a Revit project where you've overridden some objects using "Override Graphics in View > By Element…
When you export to a .DWG, you have the following options under DWG Properties that will give you some control of the conversion to .DWG process.
When a Revit element with view-specific graphics is exported, in AutoCAD those differences (overrides) are applied to the individual entity, but the entity resides on the same layer as other entities in the same Revit category or AutoCAD layer.
Notice that all the walls are on the A-WALL layer and overrides are made to the color and linetype (highlighted yellow). Note that there is no change to the halftone override.
When a Revit element with view-specific graphics is exported, in AutoCAD those differences (overrides) are ignored. The entity resides on the same layer as other entities in the same Revit category or AutoCAD layer, and it loses its unique attributes. This option forces all entities to follow visual properties as defined by their layer. It produces the least number of layers and provides by-layer control over the exported DWG file.
All Revit overrides are lost… Notice how all objects are on the same layer and color andd linetype are set to Bylayer.
When a Revit element with view-specific graphics is exported, in AutoCAD the entity is placed on its own layer. This option provides by-layer control over the exported DWG file, and preserves graphical intent. However, it increases the number of layers in the exported DWG file.
As you can see below, each object with a Revit override is placed on its own layer (with the exception of the halftone override).
Monday, March 22, 2010
IMO - the most common reason for Revit to crash at our firm is the lack of resources (RAM). Most of our computers have at least 2 GB or RAM and up to 4 GB). The majority of our users have 4GB...
Our PCs range from 3.8 Pentium 4's to Core 2 duo (better) and we're running on XP Pro (32 bit) at the moment, so adding more RAM won't help because of the OS and it's RAM limitation. We do have the 3 GB switch enabled on most PC's, (a few just didn't like this setting so we couldn't utilize..). You can go here is you want more information on this subject.
SOLUTION: 64 bit OS with at least 8 GB of RAM... (now if money only grew on trees!)
If you don't have this as a option, then you can also use the Worksharing Monitor's System Performance Monitor to help catch a low resource issue prior to it happening. As you can see in my System Performance monitor, running a 64 bit OS (Windows 7) with 8 GB of RAM, I have ton's of resources compared to a 32 bit OS with 2GB of RAM. Also, with notifications on when using the Worksharing Monitor, you will get a window popup window letting you know you're running low and had better save.
Windows XP - PRo - 32 bit:
Windows 7 - 64 bit:
Another issue that will not cause a crash, but will prohibit you from saving due to insufficient resources when your temp folder is full. What is full you may ask? I asked Revit support the same question and didn't get a definitive answer, but I can tell you this, if Revit crashes and you don't clean out this folder (see more on this below), you WILL have this problem eventually... My guess is if you get around 1 GB of "stuff" in there, you'll start to have problems.
Revit creates temp files during normal use of the application. When Revit closes normally, these files are deleted. If you crash, they are not... and they can take up quite a bit of space. Here is an example of the files I'm talking about and you can see that they're pretty big. As you can see, this is only one day - imagine if you crash multiple times over different days!
Tuesday, March 02, 2010
To give you a little background on our Imperial Library - It's primarily EUA created with very little remaining out of the box (OOTB) content. We actually started with the OOTB content during our initial Revit migration (5 years ago), but quickly came to the conclusion that it was lacking in many facets. It was fine for our pilot project, but that's where it ended. Content creation has been a 5 year project and will probably never end, but we're definitely over the hump. Content request by our staff have leveled off, but we still get one or two weekly. So, if you're a firm making the switch to Revit, be sure to consider the importance of quality Revit content. Don't get me wrong - Revit it AWESOME and we love it, but it's a shame that most of the content that ships with Revit doesn't have the quality or consistency required. Sorry Autodesk, but I don't think the content that ships with Revit has been updated for years...
The results below are a quick overview of our Imperial Library:
Total number of EUA Revit families: 6260
(FYI - Revit ships with ~1165 families out of the box)
EUA Revit families with a size over 500k: 35
EUA Revit families over 800k: 1
Thursday, February 18, 2010
Wednesday, February 10, 2010
"Ignorant" Door Schedule
Tuesday, February 09, 2010
You can also download some supporting documentation depending on if you're using Revit or AutoCAD or Microstation.
Here is the info on the company offering the webcast. I can't endorse them as I haven't worked with them, but we do use the Riverbed appliance and are very happy with it.
Thursday, January 28, 2010
Monday, January 25, 2010
Thursday, January 21, 2010
Affinity is a early architectural design application that's strengths lie in programming, space planning and schematic design. Affinity can run stand alone or linked with Revit (bi-directional link). For more on this go to the Revit and Affinity page.
We had around 20 in attendance today including architects, engineers and contractors. Larry did an excellent job explaining the software and then doing a live presentation which included working in both in Affinity and Revit and syncing any changes between the two applications.
A few of the cool things I picked up today were:
- Affinity can leverage Sketchup for creating and modifying the "footprint" of your model which then updates in Affinity.
- Affinity symbols can link to Revit families.
- As Revit's API is opened more with each release, Affinity plans a more seamless "sync" as data changes. This seamless sync already occurs in Affinity, but will be further integrated with Revit as the API opens. (it's not a big deal, but you may have to hit the "refresh" button... currently)
- Start in Revit, then create the Affinity project
- Start in Affinity, then automatically populate a Revit model.
- Start in Revit (using Excel for programming), then combine both in Affinity
Tuesday, January 19, 2010
Check it out!
Remember, you can also subscribe to our posts and be notified via email when a new tip is avaialble for viewing.
Let’s bring things into focus by increasing the magnification of the screen!
There are a couple ways to accomplish this.
- Use the scroll bar or drop down to increase/decrease the zoom percentage. All applications are similar in concept, but you may access the tool in a different way.
- Hold down the "Control"
key and roll the wheel in/out on your mouse. The zoom percentage noted above will also reflect this change, so getting back to 100% is pretty easy!
Wednesday, January 13, 2010
InPro is launching a BIM library for their line of products. As part of their marketing effort, you have the chance of winning a 2011 Harley-Davidson® Heritage Softail® Motorcycle!
Go here to register for the bike!
Tuesday, January 12, 2010
Monday, January 11, 2010