Rhino 8 Connector is finally here!

I seems that the grasshopper connector doesn’t work with the new type of Rhino model object elements like the content cache. I can only get the send to work with traditional model elements. (Using the speckle for Rhino Send from the sidebar does send any user attribute text) I get an error whenever I connect the send element to the content cache or to the new Rhino Model Object parameter.

I suppose a work around would be to use the Extend Speckle Object to write data to a speckle object and to the Rhino Geometry. You would need to make sure your script captures any existing data and merges that with the new data. If you don’t add that functionality you would lose data that was added outside of your grasshopper script. The content cache has this functionality built in with the Endure Update etc
options. Its by far more desirable to have the content cache update the Rhino model and then also send data / geometry to Speckle.



Thanks, @bfortunato. Others have indeed reported this, notably @Jonathan_Rabagliati.

The release that you are using now for Rhino8 was a base port from Rhino7 to Rhino8 with the new .NET runtime (and resolving install locations, as it turns out)

We have already logged a development ticket supporting new GH object models. Watch this space.