Notice: This user guide is based on the legacy connector.
We recommend using our new connectors instead, as they are easier to use and actively maintained. This legacy documentation may not be up to date.
Legacy Speckle supports versions:

​
Getting started

To install the Navisworks Connector and add your Speckle account, proceed by following the instructions in Speckle Manager. Once installed, you can find the Navisworks Connector in the ribbon menu under the Speckle tab like so:
speckle-ribbon-navisworks

​
Selection filters

To help you select which elements will be to sent to Speckle, we’ve built various filters into our Navisworks Connector. Once a filter is set, just click Send and all objects passing the filter will be sent to your Speckle project. Please Note: Elements are only sent if they are visible.
navisworks-selection-filters
On opening a stream card, any selected objects by default become the elements destined for send. This can be reset.
navisworks-setselection

​
Saved view filter

The view filter works similarly to the category one, and lets you include all elements visible in one or more views.
navisworks-savedview-filter
This will only be visible if your model has saved views with Hide/Required selected.
navisworks-valid-savedview

​
Selection set filter

The selection set filter lets you select one or more selection sets or saved searches from the current model. This will only be visible if your model has selection sets or saved searches.
navisworks-selectionset-filter

​
Receive modes

Receiving geometry into Navisworks is not currently supported. However, you can receive data into a Revit or Rhino model and then open the model in Navisworks.

​
Current limitations

Navisworks produces a lot of data, and the Speckle Navisworks Connector is still in its early stages. As such, there are a few limitations to be aware of:
  • Sends may not complete first time around. If this happens, try again.
  • Only a single view can be sent at a time.
  • One-click send is not supported. You must select a filter first.

​
Levels and collections

Where a Navisworks model has levels differentiated these will be found in the Speckle commits as a collection as any other type of collection. There is no coallescing of levels performed across collections. This is because Navisworks does not have a strong concept of levels. Essentially the hierachy of the Speckle data will match the hierachy of the selected elements. When sending from Navisworks, Speckle will convert all embedded BIM properties alongside metadata generated in the conversion from native formats to Navisworks. This includes file paths, element ids, element types, etc. The BIMness of objects is stored in the properties property of the object. This is a dictionary of key-value pairs, where the key is the name of the parameter and the value is the value of the parameter. There is no concept beyond Object+Data in the data sent.
All the parameters are stored using their User Display Names.
To easily explore on object’s data and parameters, our Speckle Web App interface can be of great help. As well as any other applications that lets you explore the object metadata (eg Grasshopper, Dynamo, Unity, etc).
web-bim-data

​
Advanced settings

The Advanced Settings page allows you to customize the way Speckle behaves “per-stream”.
navisworks-advanced-settings

​
Reference point

Allows the user to specify which reference point should be used when sending data. Available options are:
  • Model Origin (the default option)
  • The Project Base coordinate
  • The Bounding Box origin
The XY Coordinate inputs are valid for defining the Project Base coordinate option.

​
Coordinate Units

Allows the user to specify the units of the coordinates sent to Speckle.

​
Include View

Allows the user to specify whether the current active view should be included in the data sent to Speckle.