Clash Report and Incorrect Revit ID Numbers

This problem sucks, there just isn’t any good way to put it….

If you’ve been using Navisworks with Revit files, you may or may not have run across this depending on how you use the Clash Reports (exported reports).  When you look at the Clash Report, there is a separate column for the Item ID, which for Revit is the Element ID.  You can use that ID number to search for the Element that is being called out in the Clash. (similar to what I discussed in this post about Revit Interferences)  At first glance, it looks great.  I can grab that ID number, go to Revit and quickly find the item in the Clash, especially if you don’t have the Navisworks model (versus possibly using Switchback if you had the Navisworks model). 

But, there is a problem when it comes to some objects.  Some objects, like Columns, Beams, Diffusers (to name a few) don’t actually report the proper Revit Element ID!!  Yeah, not so good!  From what I can tell, it’s actually calling out the Element Type ID Number and not the Element Instance ID Number.  (See this post about the props of a Revit element and what is considered Instance vs Type)  Some of you may be thinking, well can’t I just use the ID number to find the object in Revit….sorry, no you can’t.  Revit wants the Instance ID number so it can actually find and select the corresponding Instance Element.

Oh, I should mention a way to get the proper number.  Well, there actually is a couple. One being to use DWF’s from Revit instead of NWC’s.  The DWF will put the Element ID number as a suffix to the Name of the object in Navisworks.  But for many, that would require a complete change in process of getting files.  The other way, would be to have the Navisworks model open with the corresponding Clash Test and Results.  When you select a clash, the bottom pane in the Clash window will show you what objects are clashing.  If you select the Element Name, use the Select button, you can then look at the Properties to get the proper Element ID number.

I’ve reported the issue to Autodesk Support, which was escalated to the Development Team.  Hopefully (keep anything and everything you can crossed) that they can solve this issue in the next release of Navisworks!

Navisworks 2012 Deployments with Service Pack 1

With the latest Service Pack/Update 1 for Navisworks 2012, there have been some questions on how to add this to Navisworks 2012 deployments.  When you go to modify an existing Navisworks 2012 deployment (or even create a new one), the option to “download” the service pack isn’t available…the only option you have is to append or merge the .msp file(s).  Typically, this is okay but not for Service Pack 1 for Navisworks 2012.

Service Pack 1 actually has multiple .msp files buried inside the exe you download.  Which again, for appending/merging into a deployment is typically okay to do.  But, Navisworks SP1 also includes a few odbx.msp files that are not supported by the append/merge method as they cannot be added to the deployment image through the installer framework.

Because of this, you cannot modify an existing deployment of Navisworks 2012 to add in the full contents of Service Pack 1 OR even create a new deployment for Navisworks 2012 to include the full contents of SP1.

The only way to have Navisworks 2012 installed with all of the contents of SP1 is to install SP1 separately after Navisworks has already been installed.  For me, this means just run the exe you’ve downloaded to install the SP on each computer.

Using Project 2010 Schedules in Navisworks 2012

Something we just ran across was a customer looking to use Microsoft Project 2010 files inside of Navisworks 2012 for Timeliner.  When you go to add a Data Source in Navisworks 2012, it says you can only use Microsoft Project 2003-2007.  It’s actually lying….you can bring in a Project 2010 file into Navisworks 2012.

Clashes Not Showing Color in Navisworks 2012

I’ve run across a little issue with Navisworks 2012 where the clashes sometimes will not show the actual color of the Clash Status…i.e. Red for new, Orange for Active, etc.  The issue seems to be with the Lighting for the Render Style.  If the Render Style is set to Full Lights, clashes show up solid gray like this…

In order to fix this, all you need to do is change the Render Style to utilize Scene Lights (or Head Light or No Lights) and then the clashes will show up properly…

This is a defect and Autodesk Support is saying that the Development Team is aware of the issue.  Now we’ll just have to keep our fingers and toes crossed that a fix is released soon.  Once a fix has been released, I’ll post an update.

Navisworks Doesn’t Start or Launch

We’ve had a few instances of folks contacting support over the past few weeks saying that when they go to launch Navisworks (Review, Simulate or Manage), nothing happens.  No splash screen, nothing.
It has seemed to fall into one of two issues…

1. Lastsession.xml
2. Corrupt CascadeInfo.cas

For the Lastsession.xml, follow these steps…

• Close Navisworks
• Locate Lastsession.xml
• (XP default location) C:\Documents and Settings\**username**\Application Data\Autodesk Navisworks **product** 2010
• (Vista default location) C:\Users\**username**\AppData\Roaming\Autodesk Navisworks **product** 2010
• Delete the LastSession.xml
• Try and open Navisworks

For the corrupt CascaseInfo.cas, see this link…
http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=13894457&linkID=9241177
From what I’ve seen/heard, either one of these will usually fix Navisworks from not starting.