Interesting little release by Dimitar Venkov on Github a few months ago. It is essentially a Python shell for Navisworks 2016. You install by unzipping as per instructions below. You may have heard about RevitPythonShell, but obviously this one is for Navis.

To install, simply extract the zip archive in the below folder:

%APPDATA%\Autodesk Navisworks Manage 2016\Plugins

Downloads

You can read more about the features at the main page here.

  • interactive IronPython interpreter for exploring the API
    • with syntax highlighting and autocompletion (in the console only)
    • based on the IronLab project
  • batteries included! (Python standard library is bundled as a resource in the RpsRuntime.dll)
  • full access to the .NET framework and the Navis API
  • configurable “environment” variables that can be used in your scripts
  • save “external scripts” for reuse and start collecting your awesome hacks!
  • run scripts at Navisworks startup

And some example/s are in a GitHub folder:

Here is a few quick tips that I had sitting in draft post:

  • To delete lots of views quickly, select and then press Delete key. Do not try to right-click.
  • To combine multiple Clash Groups in the Clash Detective, select the groups, Ungroup (sub-clashes will be selected by default), then Re-group..
  • To delete multiple empty clash groups, drag a clash into one of them. Then, Select All the Groups and you can Explode Group
  • If you Append an NWD, the views with saved Hide/Required and Material Overrides will import “correctly” with these settings (but a Viewpoints XML cannot import these element hide and colour settings)
  •  Use Properties+ … it is simply the fastest way to test and build Search Sets

propertiesplus.png

This recent post on Dynamo Nodes shows how a simple Navisworks Search Set can be built by Dynamo running inside of Revit:
Create Navisworks Search Set XML for Element Ids | Dynamo Nodes

In the first release, this node just uses Element Ids to build a long ‘orsearch set, but this basic idea could easily be extended and adapted to more closely connect Revit to Navisworks search workflows through Dynamo.

Here is a Screencast:

Navisworks is pretty amazing at handling a huge set of properties across a large amount of elements. However, sometimes it can be hard to diagnose why a particular parameter, such as a Shared Parameter, is not displaying or grouping in a way that you might expect.

To figure out what is going on, go into Navisworks Options – Interface – Developer and tick the two boxes:
Show Internal Properties
Show Property Internal Names

Now, when you use the Properties palette you will see additional information in brackets, which essentially amounts to the Navisworks ‘internal parameter name’ for a given piece of data. Pretty cool!

Thanks for this tip goes to Jason Howden, from RTV Tools, a Platinum sponsor here at What Revit Wants.

props.png

Related forum post:
https://forums.autodesk.com/t5/navisworks-general-discussion/navisworks-manage-2015-amp-revit-project-parameter-problem/m-p/5672998#M9579