Update to Switchback with Revit 2013

I’ve posted a couple times now about the Switchback feature in Navisworks and how it works with Revit.  Well, there is an update to the functionality for the 2013 release in a good way!

When you now use Switchback with Revit 2013, the camera view that you are using in Navisworks 2013 is now created in Revit…literally.  When in Revit, you’ll be directed to a new 3D View called “Navisworks”.  The nice thing is you don’t have to create this view, it happens automatically.  So if you rename or remove the “Navisworks” 3D View and use Switchback again, you’re going to get another “Navisworks” 3D View in Revit.  This is much, much better that what we got in 2012 where the camera didn’t change much in Revit, or maybe just went to a plan view.

Another change is that the object that you’ve selected in Navisworks 2013 to run Switchback with will now actually be selected in Revit 2013 and show the Properties!  Revit 2012 almost had it, but you had to do a few things to make the properties actually show even though the object was “selected”.

One thing though with the object selection potion of this…your results are going to vary depending on what you have your “Selection Resolution” set to.  When I first tried it, I had the “Selection Resolution” set to “Last Object” and the object selection in Revit wasn’t showing.  So I went back and tried the other options for “Selection Resolution” and the one that you want to use is “First Object”.  By using this “Resolution”, the Revit object will be highlighted and the properties of the object will be available.

Here’s a little video showing the new functionality of the Switchback feature for the 2013 products…

Navisworks and Revit 2013 Switchback

One thing to note for those using Revit 2012 and Navisworks 2013…you have the ability to use Navisworks Switchback 2013 in Revit 2012, but the functionality of the Switchback will be the 2012 functionality.

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!

Selection Tree and Revit Objects

This is something that I get asked quite a bit…when I load in a Revit file into Navisworks, why do things like Columns or Doors (as examples) always show the Type Name twice?

If you’re not sure what I’m talking about, here’s a little screen shot…

As you can see, the W10x49 has a “sub component” also called W10x49.  What you are really seeing here is the Element and the Type (respectively).  To help explain this a little further, here’s each one selected and the associated “Element” properties…

 

As you can see in the image on the left, the Properties for the first item selected displays the Instance Properties of the Revit object.  On the right image, you can see the next item in the list is selected, which is now displaying the Type Properties.

So when you see Revit objects with what seem to be duplicate names, you are actually seeing the Instance and the Type.  One thing to note, this isn’t the same for all Revit objects.  Take Walls for instance, Navisworks only lists out the Instance and the actual geometry (as shown in the top image).

From what I can tell, this helps separate out the Properties and the number of tabs that are displayed.  But, there is an issue with having all of these properties broken out like this, specifically the Element ID!  This ties back to the Switchback post…if you try and use Switchback with the Type selected, it won’t find the object.  And, that’s not all…it also affects your Clash Detection reports!  More to come on that subject soon….

Navisworks 2012 Switchback with Revit Video

Way back in July, I posted about a new feature for Navisworks and Revit 2012 being able to now use Switchback.  Well, I finally got around to creating the video that I said I was going to.   It’s amazing how time flies when you’re busy!

The video below shows the interaction of Switchback with Navisworks and Revit.  I didn’t put voice to the video, but did input some “pop-ups” with some explanations.

As you can see, there are some interesting things happening in this first iteration of Switchback with Revit.  Hopefully the 2013 versions have a much better integration.

Navisworks Switchback to Revit

New in Navisworks 2012 (Simulate and Manage) is the ability to utilize the Switchback feature!  This has been accessible/available to those working with AutoCAD for a while now, but it’s a nice addition to those working with Revit.  I’ve received a few questions about working with Revit Switchback and whether or not you have to export the NWC from the central file or local files?  And if local, how does it know what local file to get and how is it going to get a local that’s on someone else’s computer!?

Ok, well, you don’t have to export from the central and it doesn’t matter what local file you export your NWC from.  The nice thing about Revit Switchback is that is goes strictly by the ID number of the Revit objects…so it doesn’t care what (local) file it’s from.  And as far as what file it will try and open, well, it will look initially for the file the NWC was produced from.  But, not to panic, you will be prompted saying that it can’t find the file and allows you to browse for a new file….your own local file.

The key part about Revit Switchback from the Revit side is that you already have the file open and you’ve initiated Switchback in Revit. 

How do you do this?  Great question, glad you asked!

In Revit, go to the Add-Ins tab and External Tools.  There, you’ll find Navisworks Switchback.

Once you’ve selected Navisworks Switchback, you can now utilize Switchback in Navisworks with Revit.  The nice thing, is that you only have to do this once per Revit session.  So if you have Revit open all day, you only have to initiate the Switchback in Revit once.

I have to say though….as much as I like this, there is some work to be done with this feature.  It’s the first iteration, so I expected there to be some little things to work-around, but I guess I also expected this to work similar to AutoCAD and it doesn’t.  I’m creating a little video explaining some of the things that I’ve found that need work, including some of the things I’ve found to get around some of the issues.  Stay Tuned!