Product update ·

Navisworks file imports and more

Navisworks file imports (.nwd and .nwc)

You can now upload .nwd and .nwc files directly into Speckle, either through the file upload in the Speckle web app, or by syncing them from your Autodesk Construction Cloud (ACC) account. No connector, no desktop application open in the background.

Getting a Navisworks model into Speckle used to require installing and configuring the Navisworks connector. That's no longer a requirement.

What gets converted

The file importer has feature parity with the Navisworks connector, so:

  • Mesh geometry is published
  • Materials are converted and applied to objects
  • Properties are attached, so your model data comes through alongside the geometry

A couple of things to be aware of: linework geometry is not supported at this time, and .nwf files (which reference external files rather than containing geometry directly) are not supported yet.

What you can do with it

Once your Navisworks model is in Speckle, you can use it across any of Speckle's workflows. Exchange it with other applications, build dashboards and get insights (including with Speckle Intelligence), or present and review models with your team.

Try it by uploading a .nwd or .nwc file directly in the Speckle web app, or connecting your ACC account and syncing from there.

Be the first to get Speckle updates directly in your inbox — subscribe here.

Additional Improvements

Workspaces

Features

  • Workspace SSO providers now support user session revocation via a global back-channel logout url. Read more about this here. (docs update pending from @Daniel Gak Anagrov)
  • 3rd party application developer experience has been revised with a more secure PKCE based OAuth2 token exchange flow and an improved SSO session refresh flow.

Server deployment

Features

  • Self hosters of the Speckle server enterprise edition can now use Azure’s native storage layer as the object storage provider.

Revit connector

Features

  • Analytical model categories are now included as supported Revit categories. (#1325)

Fixes

  • Rooms were excluded from sends when volume calculation was disabled in the project (a common setting on large models). The fix switches the unplaced-room check from volume to upperLimit, which is more reliable. (#1334)
  • Sequential path prefix stripping regression introduced in v3.17.0 has been patched in v3.17.1. (#1328)

Grasshopper connector

Features

  • Nested properties now use dot notation (e.g., Instance Parameter.Text.Phase 1) across the Create Properties, Speckle Properties Passthrough, and Query Properties nodes — matching how the Property Selector node already worked. (#1313)
  • The Filter Objects node has a new Property Value input. Filter by key, by value, or a specific key-value pair at once — no more manual list culling. (#1319)
  • A mix of SpeckleDataObjects, SpeckleGeometry, and Collections can now be piped into the same send component. The Create Collection node is optional for simple scripts. (#1332)

Fixes

  • Expand Properties was silently dropping values when objects in a list had different property schemas. It now scans all volatile data on the first iteration to build a union of all unique keys, and maps outputs by name rather than index. (#1322)
  • Duplicate ID crashes and missing Revit geometry when receiving models. A prior change accidentally broke deduplication and swallowed Revit proxy geometry — both are now fixed. (#1324)
  • Dynamic components no longer drop wires when inputs change. (#1326)

Navisworks connector

Fixes

  • Some elements from selection sets were missing in Speckle because different items were occasionally given the same internal ID. We’ve fixed this by switching to path-based identifiers, ensuring every element is uniquely and reliably tracked. (#1310)

All connectors

Features

  • New account binding authentication flow across all .NET connectors. (#1339)