Next-Gen Connectors: Supported Workflows and FAQ

@Community

We’re focusing on clarifying Speckle as a product, and are currently in an open beta of our powerful and stable Next-Gen connectors. This post is your one-stop-shop to understand:

  • the official Next-Gen workflows, and which workflows have been added for each connector
  • general FAQs about how next gen works during beta
  • when you should switch to the Next-Gen connectors

We’ll keep this post updated as we continue developing over the next month(s), so check back in for the current state of each connector!

Next Gen Connector Workflows

L1 - Business Intelligence and Presentation

Publish your models with object metadata for BI and presentation in the web

When you publish models from any Next-Gen connector, by default you will be able to use this model for business intelligence insights because we are sending each object with its geometric representation as well as important metadata and properties. Explore your model properties in Power BI, Automate, or directly with our SDKS, and easily share and present your models in our powerful web viewer.

L2 - Design Coordination

Load your models in other applications for reference coordination

Any Next-Gen connector that has receive functionality can load models published from any Next-Gen connector for coordination purposes. This means you will be getting an optimized, lightweight geometrical representation of your loaded model to use as a reference in your host application.

L3 - Multiplayer Modeling

Multiplayer interop modelling in 3D

This is our high-powered interoperability workflow, where you can publish and load models with your collaborators as native objects, as if you had made them in your receiving application.

Connector FAQ

Typically, we will develop Next-Gen connectors to support workflows in the L1 → L3 order. We’re moving quickly in beta, so keep your eye on the below section for updates to what you can expect to do in each connector.

General FAQ

Are the current connectors (v2.x) and Next-Gen connectors compatible?

No, Next-Gen is intended to be a clean slate new version of authoring Speckle models. While you may be able to receive some current models with the Next-Gen connectors, do NOT expect the models to be loaded with the same properties and quality as they would be in the current connectors. For this reason, please:

  • re-publish any current Speckle models with the Next-Gen connector if you want to load them in a Next-Gen connector
  • only publish and load from a current connector ↔ current connector, or Next-Gen connector ↔ Next-Gen connector
Where do I install the Next-Gen connectors?

If you have a Speckle account on app.speckle.systems, you can install them directly here.

How do I get the latest version of the Next-Gen connector?

If there’s a new version of Next-Gen connectors available, you’ll see a little Update button when you open it up in your host application. You can always go back to app.speckle.systems to check for the latest version.

How can I remove the Next-Gen connector? It’s still there after uninstalling from Speckle Manager.

All Next-Gen connectors can be uninstalled directly in your operating system’s programs or applications manager as if you would uninstall any other application on your computer.

Can I see my Speckle Automate results in my model?

Yes! If you run an Automation on your model, you’ll get the results straight in your next gen connector UI, allowing you to highlight objects in your host application linked to each result.

I've loaded a Speckle model, where are my object properties?

Although we are extracting your object properties when you publish your models, we haven’t defined loading object properties yet. If you’d like this functionality, please explain your workflow and what you’re trying to achieve in this thread!


Revit (L2)

Business Intelligence, Coordination

  • publish Revit models with critical properties like Type and Instance Parameters and Material Quantities.
  • load any model as direct shapes for design reference

Should I Use Next Gen?

  • YES if you want faster publishing and loading, Speckle Automate results, and more structured property data
  • NO if you expect to receive native Revit objects, eg for Revit ↔ Revit or Rhino/Sketchup/Grasshopper Mapper → Revit workflows. Stay tuned for an L3 upgrade to Revit!

FAQ

Why are my Revit elements coming in as direct shapes instead of native elements?

We’re only supporting coordination workflows when receiving in Revit at the moment. We will eventually add interoperability back in, when we can do so in a very clear and controlled manner to maintain our connector quality and stability. If you’re looking for an interop receive in Revit, use our legacy connector.


Rhino (L3)

Coordination, Multiplayer

  • publish and load your L3 models with high-quality native geometry.

Should I Use Next Gen?

  • YES if you want change tracking features, better layer and object colour and material inheritance, Speckle Automate results, and faster publishing and loading
  • NO if you’re working with dimensions or text. We’ll be adding these soon!

FAQ

Where is Rhino Mapper?

This is a legacy workflow available in the current connector only. We may add this functionality back in to next gen at some point in the future.


Sketchup (L3)

Coordination, Multiplayer

  • publish and load your L3 models with high-quality native geometry

Should I Use Next-Gen?

  • YES if you want change tracking features, faster publishing, and Speckle Automate results.
  • NO if you want to quickly load a huge Revit model with many family instances. This will work in Next-Gen, but expect a longer load time (for now).

FAQ

Why does loading my large Revit model take longer in Next-Gen?

We were doing some fancy instancing in our current Revit connector which helped optimize loading models in Sketchup. We aren’t publishing any elements as instances from the next gen Revit connector currently, which is why receiving in Sketchup may be slower. Improving this is on the roadmap, so stay tuned for changes!

Where is Sketchup Mapper?

This is a legacy workflow available in the current connector only. We may add this functionality back in to next gen at some point in the future.


Navisworks (L1)

Business Intelligence

  • publish your Navisworks models with all their properties

Should I Use Next Gen?

  • YES! Next-Gen Navisworks does everything that the current connector does and is faster and more stable, and includes Speckle Automate results.

Archicad (L2)

Business Intelligence, Coordination

  • publish your Archicad models with material quantities, IFC, dimensional properties, and custom user properties.
  • load any model as object type elements (GDL objects) for design reference

Should I Use Next Gen?

  • YES, if you want faster publishing, Speckle Automate results, and more structured property data.
  • NO, if you want to receive from any source app (eg. Revit, Tekla etc.) or publish your model with any property not listed above

FAQ

Why are my Archicad properties missing?

We are currently exporting a limited number of properties from Archicad - this allows us to publish your models more efficiently. We’ll be adding filters soon to give you access to additional properties - stay tuned!


AutoCAD (L3)

Coordination, Multiplayer

  • publish and load your L3 models with high-quality native geometry.

Should I Use Next Gen?

  • YES if you want change tracking features, Speckle Automate results, better layer and object colour and material inheritance, faster publishing and loading, and better AutoCAD ↔ AutoCAD polyline conversions
  • NO if you’re working with xdata, dimensions, or text. We’ll be adding these soon!

Civil3d (L2)

Business Intelligence

  • Publish and loadyour Civil3D models with part data, property sets, and site, network, surface, corridor, and assembly properties.

Should I Use Next Gen?

  • YES if you want complete coverage of object types and properties, your corridor solids attached to your corridor subassemblies, change tracking, Speckle Automate results, and faster sends.
  • NO if you want to get your pipe networks into Revit as pipes. We’ll be adding coordination receiving soon.

Tekla (L1)

Business Intelligence

  • Publish your structural model with reports and custom user attributes

Should I Use Next Gen?

  • YES! Next-Gen Tekla does everything that the current connector does and is faster and more stable, with better structured properties and Speckle Automate results.

ETABS (L1)

Business Intelligence

  • Publish your structural model with sections, materials, and assignments

Should I Use Next Gen?

  • YES if you want fast and stable publishing with critical properties!
  • NO if you are relying on analysis results - these may be added soon.

ArcGIS (L1)

Business Intelligence

  • Publish your layers and layer features with all of their attributes

Should I Use Next-Gen?

  • YES! Next-Gen ArcGIS is much better than the current connector, and includes Speckle Automate results.

QGIS (L1)

Business Intelligence

  • Publish your layers and layer features with all of their attributes

Should I Use Next Gen?

  • YES if you want fast and stable publishing with critical properties!
15 Likes

Clarification on V2 vs. V3 Compatibility

This is already covered in the General FAQ above, but it’s clear that some have missed it, so I’m restating it here for emphasis:

V2 and V3 (Next-Gen) connectors are NOT designed to be compatible, and there are no immediate plans to make them so.

  • If you’re using V3, re-publish your models with a Next-Gen connector for best results.
  • If you’re using V2, stick to V2 workflows for consistency.
  • Cross-version workflows are unsupported—some things may work, but they are not guaranteed and not officially supported at this time.
1 Like

{41A3E0A6-056A-4901-992C-6367ABD9AA88}
@Community We’ve released a new version of our next gen connectors: 3.0.0-beta.217 :partying_face:Check out some key updates below:

:star2:NEW! Next-Gen ETABS Connector
is hot off the press, thanks to amazing work from @bjoern and @dogukan.
Publish your structural model with materials, sections, assignments, and other properties. Excited? Check out this sample model for a sneak peek: etabs/objects - Next Gen Test Models | Speckle

Revit

  • Publish linear and radial arrays in Revit
    We weren’t doing it before, but we’re doing it now: linear and radial arrays can now be published from Revit!

Rhino

  • Rhino Next-Gen Toolbar Added
    Your Rhino Next-Gen connector now comes with its own toolbar: enable it with the toolbar command. It’ll pop up like this when you do:
    {D5095764-FC38-4F65-BD9D-4EBC64FBE2E4}
  • Rhino Object user strings and names now published
    We’re now including object names and user strings when you publish Rhino models. Note: Loading names and user strings is still not supported for now.
  • “Undo” loaded models in Rhino
    It’s the small things in life - now after loading a Speckle model in Rhino, you can ctrl + z if you change your mind.

AutoCAD

  • Autocad Next-Gen Panel Added
    Your Autocad Next-Gen connector will now appear in the Speckle panel like so:
    {7671C3AF-65CB-4488-8E1C-3F006464F3DE}
14 Likes

Hey @Community,
New beta connectors have just dropped with new features here :point_right: speckle-releases

:star2: Next Gen PowerBI Connector

  • Private projects are now available. :lock:
  • It’s way faster now since we have considerably improved our data handling behind the scenes! :zap:
  • Publishing dashboard/report won’t require downloading data again and your data become offline after the first load :floppy_disk:

powerbi

Sign in via connectors

We have enabled auth logic via connectors to eliminate extra steps over Manager. It is just a single button click now.

SketchUp_LI0ZcYC8CA

Navisworks Saved Sets Send Filter

Saved sets on the model are now integrated into our send filter logic in Navisworks and support multi-selection.

navis

More connectors and features are on the way—stay tuned! :rocket:

We’d love to hear your feedback and feature requests, as we’re highly responsive in shaping our next-gen connectors. :ear:

12 Likes

@Community We’re coming in hot with two release updates, install your Next-Gen connectors here: speckle-releases


{D0E7A1DB-62F7-4FBE-80FF-4C8DA2267A58}

NEW! Next-Gen QGIS Connector
is here after a few weeks of hard work from @Kateryna !
Publish your GIS model with layer and feature attributes, and receive them in Revit, Rhino, SketchUp, AutoCAD, and Civil 3D. A sample model for you to play around with:


{399886CF-B58A-44BA-8086-0DC876F4F413}

Load any Speckle next-gen model into Civil 3D!
We’ve added receive to Civil 3D, so now you can load your models from Revit, Rhino, ArcGIS, and more as context for design coordination :blush:

8 Likes

Kudos and sincere thanks to @bjoern and @dogukan for the Etabs Connector New Update :partying_face:

My suggestion for future: Ability to publish elements’ forces and import it in Revit. :v:

2 Likes

@clrkng, can I get a bit of clarification on the next-gen ETABS connector - is it available for ETABS 22, and how would one download the next gen connector currently?

1 Like

Hey @chris.welch,

Yes, it is available for ETABS 22. You will need to load the plugin manually (I believe this is just how CSI plugins are; I may be wrong). You can do this by going to Tools > Add/Show Plugins.

You can download the Next-Gen ETABS connector and all other next-gen connectors directly from within the web application.

3 Likes

@Farzan_Bayat, what would you do with the forces data in Revit before we leap into this feature request?

1 Like

When I need to model rebars for slabs and walls, I can view the forces inside the Revit and model rebars with more confidence and avoid errors. Before adding connections to steel frame elements, I can review moment and shear force to make sure enough bolts and weld is provided for each connection. :+1:

2 Likes

Hi @Community

The Load functionality is back in the Archicad v3 connector with our latest 3.0.0-BETA.8 release

We’ve also introduced a new Filter to select elements by Element Type on Publish

What to Expect?

  • Design Coordination with all other Next-Gen Connectors
  • Load Elements as Archicad Library Part Instances
  • Each Load Operation creates a new folder in your Embedded Library with new GDL elements
  • Meshes are supported, 2D elements are not
  • Floorplans will display only Cut Lines, which are Story- and Floor Plan Cut Plane sensitive
  • Single-threaded Load Process (for now)
  • Initially could be slower than v2 with specific models, but we’re working hard to make it better in future releases
  • Archicad UI remains blocked during the Load operation

What’s Next?

  • Unblocking Archicad during the initial stages of the Load process
  • Implementing multi-threading to fully utilize your hardware and speed up element creation

Still in beta, but we thought it was worthwhile to share it with the community.
Any feedback is greatly appreciated—let us know what you think!

14 Likes

Hey, really like the look and feel of the new connectors.

I can’t seem to send a message from Rhino or Revit with the commits now though, has that feature been deprecated?

1 Like

Hey @FabSel - yes, for now. It’s not possible - a bit of a ux/ui nightmare to implement without adding yet more text fields/buttons in a way that doesn’t scare less tech savvy users (also feel free to tell us what you’d like simplified even more).

How were you using them? We’d be really curious to know more!

1 Like

Thanks for the context! We use it for multiple purposes. In our internal conversion GH scripts, we use it to communicate with each other. For example, the input for DayLight follows one naming convention, exports another, and so on. Project Models could potentially be used for this instead, and might be a better long-term solution, so this is a good push toward using that approach.

We also use it for documentation purposes. When we push something, we include what the major changes were, making it easier to follow the history of the project.

For our custom apps, we also read the file and use it to display versions alongside the date. This gives us a helpful way to filter through different iterations and provides a searchable reference, especially when dealing with a long list of versions.

2 Likes

Thanks for the context. The minor good news, albeit long-handed for now, is that the Version message can be edited in the web UI.

Accessible from the Versions view for a model.

1 Like

does this affect data queried via graphql api? (are the connectors pushing new data structures?)

Indeed. Yes and no.

The methodologies/techniques for traversing a Speckle directed non-cyclical graph are unchanged.

What has changed is that source applications are now CONSISTENT in the data structure they publish — which depending on how you have been accessing Speckle data will be a cause for additional work or pass you by completely.

We have a set of Sample Models that you could simply explore.

Headline changes, so far. (In no particular order than what I can recall)

  • Instances/Definitions from. Revit are no longer used. The data schemas still support this structure if needed for applications but removing the complication for data analysts was prioritised over payload size

  • on the topic of payload, RenderMaterial, RenderStyles and other highly repetitive properties — these are now handled as proxies. This means at the root Version object a definition of a render material is stored and associated with an array of objects for which it pertains.

  • Properties are now ALWAYS found in properties. The number one requested change is now in place. In addition these are all Key/Value Dictionaries instead of Base objects . They can be theoretically infinitely nested but typically are not very deeply

    This change is possibly breaking for applications if paths to specific Revit Parameters have been used hardcoded in a pipeline or app.

    A path to a Revit Parameter is now: properties.Parameters.Instance Parameters.Dimensional.Unconected Height.value

    I will be sharing in due course some helper methods for generically handling properties — in the meantime feel free to explore code for the Model Checker pre-made automation.

Those are the major changes, but @clrkng may have more that come to mind. This will be part of NextGen docs when dust has settled.

2 Likes