The Revit Clinic

Placing exported MEP systems onto separate AutoCAD layers

A known limitation, and often raised issue by Revit MEP users, is the inability to have individual MEP Systems end up on separate layers when exporting to CAD drawings.  Instead, all elements of the same category, regardless of the system that they are part of, wind up on the same layer.  This makes it more difficult for a CAD user to separate and control the visibility of separate MEP systems in AutoCAD.

As an example, a Revit MEP user may have a model consisting of several pipe systems (e.g. Domestic Cold Water, Hot Water, Hot Water Return).  When exporting the information to CAD, all of the pipes, pipe accessories and pipe fittings are placed on a single layer in the AutoCAD drawing, M-PIPE (default specified in Revit MEP).  Therefore, the user has to manually separate these items into layers to turn them on/off or change their appearance.

However, one workaround that I wanted to share may simplify this process somewhat for the AutoCAD user.  The key is to create view filters to physically differentiate between systems in Revit, so that when exported, the items belonging to each system will have unique properties, such as color or linetype.  This will then allow the AutoCAD user to use AutoCAD filters to quickly select and control the objects based on their properties.  An advanced user can even create a macro or script to automate the separation of these elements.

In the video here (no sound), I have shown an example of a Revit model with the three piping systems referred to above.  The view filters are rather simplistic, overriding the color and linetype of the pipes and fittings based on a unique comment (DCW, DHW, or DWHR).  When exported, the objects maintain their color and linetype in AutoCAD.  Once in AutoCAD, the user can use Qselect, filters, or some other function to select the objects that they want.

In short, it would be ideal to be able to export systems to individual layers.  This is a wish request that development is looking at.  For now, this may be an acceptable alternative.

If anyone else has come up with a workaround, please feel free to share.

The case of the deleted elements…

Many of us have been in a situation where we create a new local file, and notice specific elements missing from the file.  It might be tags, keynotes, text, etc...  The question is how did these elements get deleted?

More often than not if a specific object type is missing throughout the entire project, “Select all Instances” may have been used to select them.  Once selected they may have been deleted from all views.

The following journal excerpts will give you a better idea of what to look in a journal file to isolate this scenario.  In this example let’s use “text” as the missing object type…

The user selects a portion of text:

"SEL RESULT: Text Notes : Text : 1/4"" Arial"

User then right-clicks, “Select all Instances”:

Jrn.Command "ContextMenu" , "Select all elements that have the same type as the selected element , ID_PRJBROWSER_SEL_ALL"

User then deletes them:

Jrn.Command "AccelKey" , "Delete the selection , ID_BUTTON_DELETE"

All matching instances of this text deleted from project:

Jrn.Data "Transaction Successful"  , "Delete Selection"

Rendering output shows red & black squares

If when rendering in Revit 2009 or 2010 products, you come across some materials appearing as black & red squares, I want to pass along what to look for in the project.  This issue should look similar to the example image below:

 

This typically occurs with a light fixture family in the project or nested in other families.  Keep in mind they do not have to be in use in the family, but simply loaded in.

Under some circumstances if the light source definition uses an IES shape definition that cannot be located, some of the final rendering materials will be distorted.  This occurs even when no artificial lights are used in the rendered scene.

To resolve this issue:

1.  Edit the light fixture families using the IES shape definition.
2.  Highlight the light source definition, open Element Properties.
3.  Remove the IES definition from the Photometric Web File.

 

Once loaded back into the project the scene should render as expected.

Running on the Edge

I like to run along the edge and when it comes to technology, I don't mind being on my own.  Sometimes, though that leads me into trouble.  A little bit of background...

I am currently using a Macbook Pro 17inch, and running Bootcamp and Parallels Desktop. 

I am running Windows 7.  You may have heard that running Windows 7 and Revit is not a supported environment. 

As a Mac user, I upgraded along with many others to the new Snow Leopard OS, mainly for the Exchange Support since email seems to be my life. 

I am also a Parallels Desktopuser.  I like running in Parallels mainly because my new Magic Mouse works (no Windows drivers yet for the Mouse so I cannot use the scroll functions when running in Bootcamp), and I can do a few more things on the Mac side.

Before I talk about the problem I ran into, I do not recommend running in a unsupported environment.  I do not need to produce construction documents, if I did, I would be running in a Supported Environment.

Everything in my setup was running great up, until last night.  I decided to add one more thing to the list.  We support running Parallels Desktop Version 4 with a VM of XP or Vista and Revit on a Mac using Leopard (not Snow Leopard), but last night I downloaded and installed the newest version of Parallels, Version 5.  I was hopefully that because Parallels supports Windows 7 with Version 5 that things might run a little bit faster now. Hey, it was working with Windows 7 before, why not.   

After upgrading, which wasn't difficult, and updating my copy of Parallels Tools that is running on my Bootcamp partition, I started checking email and going about my business as I normally do.  Everything was fine, and I was liking the new version of Parallels, until I started Revit.  

   

Well, that did not look good.  No access to the Ribbon and no access to the application menu.  I was sure that there was some variable of all these different unsupported Environments that was causing the problem, especially because it was working fine before with Parallels 4.  

I started digging around inside of Windows 7 trying to see if that was the problem.  I disabled the Aero theme and a few other things, but had no luck resolving the problem.  

I started playing around with Parallels settings and then I remembered an old troubleshooting tip.

For problems with graphics, often Hardware Acceleration is key to the problem. 

I can only imagine what hardware acceleration the new version of Parallels was doing differently, but I figured that was a good place to start.  I shutdown the VM, and opened up the Configuration options for Parallels and turned off hardware acceleration.  

 
 
Restarted the VM and Bingo, problem solved.

So, long story short, even if you are running on a bleeding edge, don't forget your basic troubleshooting tips.  It just may get you running again.

AutoCAD Structural Detailing 2010 64-bit

I haven't posted in a while as I've been on vacation for the last two weeks for my younger sister's wedding here in Charleston. It was great spending time with family and friends from across the country and hiding from my computer for a while. :)

At the end of last week the 64 bit version of AutoCAD Structural Detailing 2010 released for Subscription customers with the AutoCAD Revit Structure Suite 2010. This release allows the Structural Detailing application to be installed on 64 bit Operating Systems, and can be obtained through the Subscription Center. More information about the application can be found at the AutoCAD Structural Detailing product page on Autodesk.com.

Material Takeoff Area Schedule

By default when calculating material takeoff area totals in Revit, you may notice the faces for all sides of the object are scheduled for the total area.

Using a door panel for this example, take a 3’-0” x 7’-0” panel extrusion.  The overall size of the door panel has an area of 21 SF.

If you schedule the door panel however, it will show a default “Material: Area” of 45 SF [or 45.3 SF without any rounding].

What is happening is that each face of the door panel extrusion [front, back, left, right, top & bottom] is being included in the surface area since the material appears on each face.

This takes 21 SF x 2 for the front & back + 1.16 SF X 2 for the left & right + .5 SF X 2 for the top & bottom for a total of 45.3 SF rounded down to 45 SF by default.

To achieve a more specific number for scheduling, we can create a new parameter for “Material: Thickness” and use it in a calculated value column with the approach below:

1.  Since “Volume” is calculated, first create a project parameter for materials called "Thickness".  Set type to “Length”.

2.  Next add a “Calculated Value” column in the schedule to divide the “Material: Volume” parameter by the “Material: Thickness” parameter [which would be entered manually for each material in the project] once you add that parameter to the schedule.  Calculated value column should be set to “Area”.

3.  The “Calculated Value” column will display a more specific number for scheduling.

The Calculated Value formula would be: Material: Volume / Material: Thickness

Video Example [no sound]

Revit 2010 Subscription Advantage Pack

The Subscription Advantage Pack is available for the Revit 2010 products.  Go to the Subscription Center or within your product to download them if you are a subscription customer.

Also, watch my videos on the Subscription Advantage Pack for more information about the in Product and extensions that are included in the Subscription Advantage Pack.

In Product Functionality:

Extensions:

Troubleshooting Startup Delays

I’ve had a few scenarios over the last few weeks isolating what may be causing Revit 2010 to launch slower than expected.  I wanted to pass along the best approach to troubleshoot this, as well as 3 common areas to verify on the workstation.

To best isolate what may be going on, open the latest journal file.  For each action in the journal file, a time\date stamp is recorded.  These time stamps will best explain where the delay may be occurring.  For example:

 

Look for long time changes between actions.  If you come across one, you can isolate exactly where the delay is occurring.

The 3 most common causes of startup delays typically are as follows:

1.  License Connection

Check the line directly before and after the “License Mode” and “Expiration” in the journal file.  The 2 time stamps should be close together. 

 

If there is a substantial delay, try steps # 1-4 and # 6 from the technical solution below:

Revit network license troubleshooting

2.  ProteinMaterial Library on a Network Location

The recommendation is to have the read-only render appearance library location on the local workstation drive.  You can avoid startup delays by keeping the path to the default location in Options > Rendering > Render Appearance Library Location > “C:\Program Files\Autodesk Revit Architecture 2010\Data\Rendering\assetlibrary_base.fbx”.  You can see this information in the first journal image referencing “Protein”.

3.  Recent Files List

Revit can potentially experience a startup delay when files are referenced in the Revit.ini Recent File list that may have moved.  For example a server may have changed locations or have been renamed.  To simply test this you can open the Revit.ini file on the workstation located in "C:\Program Files\Autodesk Revit Architecture 2010\Program", make a backup of the file, and then locate the following line:

[Recent File List]

To test, remove all of the entries beneath the “[Recent File List]” to “[Recent Workset List]” leaving a blank line so it appears as follows:

[Recent File List]

[Recent Workset List]

Launch Revit 2010 to see if the startup time has improved.

UI Mapping Tool

Update:  Looks like the problem is fixed (I think).  Now you can download a ZIP file and extract it to get the CHM file with the tool  - Thanks, Harlan

In order to help users transition from the 2009 user interface to the 2010 user interface, I am pleased to annouce a new UI Mapping tool to help make the transition a little easier.  There are some other tools like this that have been created already by others, this tool was created by Autodesk. 

Download Revit_Architecture_UI_Mapping_Tool

Extract the zip file and open the CHM file included.  The tool also includes a instructional video.  The tool maps 2009 commands to their new location in the 2010 release.

Hope you like it. 

Some quick videos

As part of a small pilot project, I have created a few quick video solutions oi the Revit Architecture Knowledge base.  If you have a few minutes give them a look and let me know what you think. 

Check them out on the Hot Issue page for Revit Architecture.

Let me know what you think!