Next-Gen Connectors Beta: Changelog, Supported Workflows and FAQ

[Jedd (Jedd Morgan)]

I recommend updating to version 2.23.17 or newer.

Slightly older versions may work, but It’s a little hard for me to declare a minimum version since we’re only routinely testing against the versions on our managed deployments (often the latest few versions)

[m.turner]

Thanks @Jedd, we’re seeing an error the civil3d 3.1.7 connector and server version 2.23.5 which might be related. I’ll get the server updated and check again.

Extract of the error message for your info

"type":"UserInputError","message":"Variable \"$filter\" got invalid value { search: null, includeImplicitAccess: true, personalOnly: false }; Field \"personalOnly\" is not defined by type \"UserProjectsFilter\".","stack":"GraphQLError: Field \"personalOnly\" is not defined by type \"UserProjectsFilter\".\n at coerceInputValueImpl (/speckle-server/node_modules/graphql/utilities/coerceInputValue.js:134:11

[Jedd (Jedd Morgan)]

Yep, any time you see a bad input message like this, it’s likely a change a server update is required.

I’ll make @oguzhan aware incase this was not intentional, but I suspect with the recent big changes to workspaces, it would be a lot of effort to maintain backwards compatibility with older servers.

Do let me know if you see issues post update.
I would also suggest going straight to the latest 2.24.X version instead of the version number I quoted, I suspect v3 connectors may still have issues with 2.23.x.

[oguzhan (Oğuzhan Koral)]

@majidaldo,

Error message you see makes sense to me because includeImplicitAccess are quite new flag that it is must to checked in connectors.

We are moving quite fast on both web and connectors side. Web team keep adding new graphqls to make some features available in connectors. But we are slightly settling on these changes. I would suggest keep your server version up-to-date as much as possible these days. This won’t be always like this. We will freeze things after 1st of June to not break self-deployed servers.

[dogukan]

Next-Gen Blender Connector hits Beta! What’s cooking?

• Integrated Auth Flow
  Now you can sign in or add new accounts directly inside Blender - streamlining your workflow.

• Integration of Workspaces
  Navigate through your Workspaces easily with our integrated UI. Simple and efficient!

  

• Magic Material Memory
  Our connector remembers your render materials. Update your model and previously assigned materials will automatically apply to the right objects.

  

• Conversion Upgrades
  We’ve improved our conversion logic with added support for vertex normals and instance proxies.

You can get it from Connectors | Speckle and give it a go. Your feedback shapes what’s next, looking forward to it.

[zoomer]

Great !
Looks very promising.
(Hope I get this version installed and activated and showing a Speckle Tab in Blender)

[clrkng (Claire Kuang)]

@Community

Speckle 3.2.0 is released!

We’ve got a big update with this one:

Next-Gen Grasshopper Connector (Alpha) is ready for test runs after a couple months of hard work from myself, @dimitrie , @oguzhan , and our dearly departed @AlanRynne .

• Install is bundled with the Rhino Connector: just update to 3.2.0.
• Docs and Sample Files are included! They will be in Speckle Sample Files in your GH special components folder after install.
• All new components created for data wrangling, design coordination, and presentation in the viewer - so take a look at those docs!

Additional 3.2.0 release updates:

• You can now publish Text objects in Rhino and Autocad along with your model, for presentation in the viewer
• A few Revit bug fixes, including no longer duplicating some blocks on load and getting correct material colors into Revit.
• A cool new rebar setting in Revit that allows you to toggle between publishing your rebar as mesh objects or centerlines.

[j.beneitez (Jorge Beneitez)]

Great stuff!
Is it still Windows only?

[eestrado (Erron Estrado)]

Great work! Nice to see this released. However, is it really not planned to include the Revit (and other) schema objects in Next-Gen as I see from your FAQ post? This was a huge benefit of Speckle in my opinion and has saved a lot of time and effort in interoperability especially for geometry that is more complex. Any chance this will be part of the final version? it would be shame to be stuck using the legacy versions.

[clrkng (Claire Kuang)]

@eestrado The main reason the schema objects were not included in the alpha release of Next-Gen Grasshopper is because we are not currently supporting native element creation in Revit, from any source.
This is understandably an important workflow for some on our legacy connectors, so I have a few questions about what you’re looking to do:

1. Is getting a directshape with solids, an assigned category, and materials applied enough for your workflow? (This we can do relatively easily)
2. If you’re looking for Grasshopper.Inside.Revit style interop, how frequently were you sending models with the schema objects, and why not Grasshopper.Inside.Revit?

[eestrado (Erron Estrado)]

Hi Claire, a direct shape with category and materials may be fine for early stages but when we get to higher level of detail modeling, native objects are needed.

For example, I’m working on a project now with lots of curved structural framing. The geometry is created in Grasshopper which I then send to Speckle as Revit schema objects to be transformed to native elements in Revit so that the BIM modeller can go further with fine adjustments and adding details. It would be a pain and very time-consuming to remodel the elements in Revit if the geometry I sent was only direct shapes.

Grasshopper.Inside.Revit is nice but with Speckle the workflows are decoupled meaning I can send data whenever I have changes and the modeller can receive whenever they are ready to implement them. They don’t need to know Rhino or have it installed. Plus, the project leader can always easily view the Speckle model in the viewer. And we also have the benefit of Speckle’s version control.

Hope this helps.

[clrkng (Claire Kuang)]

Ok, understood.
Which schemas were you relying on specifically? If we were to re-introduce Revit native interop, we’d start with a limited set of element types, and want to prioritize accordingly

[eestrado (Erron Estrado)]

On the projects I work on I mostly use the RevitBeam, RevitColumn, and RevitFloor components. As well as, RevitLevel, RevitLevel by name, and Parameter. Thanks!

[karim-daw (Karim)]

I second the above request on native elements for v3. For us the basic Wall, Floor, Column, Family Instance (via rhino block) would be amazing. And if im being greedy would love all of the below mappings yall had for v2

[willallen88 (William Allen)]

Hi Speckle team,

Is it possible get the V3 connectors from ‘Manager for speckle’? I cant install the exe’s right now because i don’t have admin rights on this machine. I imagine this might be a problem for quite a few of us working in security tight businesses.

Best

Will

[adamhathcock]

HI @willallen88

The installers for V3 should be allowed without admin rights. Are you certain this is the blocker? IT departments can lock things down further by EXE and whatnot.

Please check and let us know.

Thanks,
Adam

[clrkng (Claire Kuang)]

Small update: the 3.2.2 release just went out, and includes:

Revit

• Speckle for Revit 2026 is released!
• Fixed loading of some nurbs curves that were previously failing
• DirectShape names are set on load
• removed duplication of some wall sweeps on load
• fixed issue with receiving materials properly

Rhino

• Publishing objects located very far away from the origin now works as expected

Grasshopper

• Deconstruct works on Speckle Properties, giving you easy access to prop values
• Right-click option to create empty properties added to Create Properties, allowing you to remove props from objects.

AutoCAD

• Some bugs with sending Hatch objects with curve, circle, and ellipse loops now solved.

Civil3d

• You can now publish pressure parts, with their geometry and properties