Speckle Next-Gen Connector is a disaster for me

Hi,

I do not know what happened, in the new rhino speckle plugin

  1. it lost its supports to rhino 8, the legacy model used to supports it.
  2. the rhino category mapper is gone, i do not know if this is still in testing mode?
  3. i cannot load the model into my families anymore. i used to use speckle to push the directshape to conceptual mass family, then load it to my project. if the mass is simple (sometimes its just boxes), i can use that family to assign mass floors. with those in my project, i can get GFAs easily.
  4. also, i used to convert downloaded CAD blocks to a directshape for a family, like an office chair (local directshapes other than importing CAD), now there is no way we can do this workflow anymore.
  5. sketchup connector no longer works as a solid. when i load the sketchup model to rhino or revit, they are just faces now. even though i draw a solid box.
  6. the speckle revit connector is creating so many model groups!!! it makes the revit file so heavy. i understand sometimes to have a group for context building is necessary, but if that becomes an option, that would be wonderful.
  7. for confidential project, our clients requested us to host all of our contents on local server, but all the local hosted tutorials are for the legacy model.
2 Likes

Hi @tjxme,

  1. Majority of next gen Rhino usage is 8, well it did not lost the support. Something should be happening on your end and happy to assist if you provide where it stuck exactly.
  2. True. We do not have mapper yet for next gen since our focuses described here Next-Gen Speckle Connectors are Official - June 1st, but this doesn’t mean we won’t focus on it. We have plans to support lightweight version of mapper till end of Q3.
  3. True. It is not supported yet.
  4. I guess it is same as 3.
  5. We haven’t changed sketchup to rhino workflow too much. could you elaborate more compared with legacy and next-gen? we can see the difference that you mentioned and address if we have any issue with it.
  6. We create a wrapper group of entire model for update purpose for the latter loads. This provides liability of the state across different loads.
  7. You can still hold them on local server and use legacy connectors whenever you need them. We do our best for self-hosters with also next-gen connectors. There will be more efforts for it.

Huh, too many questions/points and nice ones! Thanks for that.

I wanna highlight that next gen connectors has different focuses than legacy ones, and we do not expect them to be perfectly same, and this has been communicated in the forum many times to warn users that still uses the legacy connectors.

Let me know if I can help more.

1 Like

Hi @tjxme ,

It looks like your issue for the Rhino 8 plugin is actually a framework problem from the screenshot that @teocomi shared, and not specific to Next-Gen. See this thread for related issues: No version of Speckle connector is working in Rhino 8.1.23325 - #9 by daniel-fink

  1. Make sure you are using Rhino 8.3 or later
  2. Try a clean reinstall of the Rhino connector: Installing Connectors - Speckle Docs
  3. You can use the SetDotNetRuntime command to change your target framework in Rhino
1 Like

thanks for the quick response.
on problem 5, with the legacy mode, on sketchup if i draw a box. pulled out then use speckle to export to revit/rhino, it will be a solid geometry. now, its just a group of faces.
for problem 6, would that be an option? sometimes we only use it one time to load content from QGIS to revit, and they are in an isolated revit container file. there is not need to be in a group or update.

im actually on rhino 8.5.


when i run setdotnetruntime, what version do i use?

Also on point 7, you are right, that there is now a difference between the self-hosted and our managed version of the app.
We do not include the workspaces experience in the self hosted version.
In fact the self hosted server instance can be thought of as an individual workspace in the mainline app.

But that does not have any consequences to how you are using Speckle on a per project basis and thus it should not have any incompatibilities with the next-gen new connectors.

You can set it to NETFramework and restart Rhino.

Also, i recommend updating your rhino to version above 8.9