Hello,
I am currently trying to send output from my ShapeDiver configurator to Speckle. I am doing so with the Speckle V2 connector for Grasshopper.
The problem I am encountering is that whenever I trigger a new run of the ShapeDiver configurator, no dat is sent to Speckle. However, when I test the file locally, I do see that data is being sent to Speckle.
What could be the cause for this?
Is there a reason why you are still using the V2 connector? We are now supporting the next-gen version, and I would strongly recommend switching to it for security and stability reasons. You can see a tutorial about it here: https://youtu.be/Son87CXLqkM?si=hF8_kEHeWvzLa6zO
Hi Mathieu,
So far we were using the V2 connector since the V3 was not supported yet. Hence, we had some scripts running on ShapeDiver with the V2 connector. We still need to port those over the new connector but that takes some time. Unfortunately, it appears that since the release of the V3 connector on ShapeDiver that the V2 connector doesn’t work anymore outright.
When looking into the logs of the script on ShapeDiver the V2 connector nodes are giving a lot of errors.
In the meantime I am trying out the V3 connector basd on the tutorial. However, when uploading to ShapeDiver it mentions that I am using a newer version (3.8) then 3.6. So I also need to see where I can download the specific 3.6 version first.
Btw, is there a timeline when the installed Speckle connector on the shared backend will be updated to V3.8? So far, I haven’t been able to download V3.6 anywhere.
We will update Speckle to version 3.8 in the next few days.
In the meanwhile, the best solution would be to access version 3.6, but it seems that older version of the next-gen connector have not been made available to download yet. We are in contact with the Speckle team to improve this process in the future.
In parallel, I will evaluate the issues you are experiencing with the v2 connector, since it should still be working as before. If you can share an example of a minimal definition that fails using the v2 connector, it would help me investigate this issue.
@Jeroen_Groeneveld I got a reply from the Speckle team, here is a link to a page where you can download older version of the connector: https://releases.speckle.systems/
Let me know if that solves your issue!
rect_speckle2.gh (11.4 KB) @mathieu1
I have included a simple script with Speckle 2 in it. Again, Just running it locally on your pc would work. A red rectangle will appear in Speckle. However, when run from ShapeDiver, it does not appear in Speckle.
I could not reproduce this speckle V2 problem yet, I will investigate further. In the meanwhile, let me know if upgrading to v3 using the above link works for you.
I will be testing the V3.6 connector beginning of next week. I will get back to you with the results.
I have tried using the v3.6 connector and I was able to send data to Speckle via ShapeDiver. However, the “Send“ node of Speckle is connected to a boolean toggle in order to indicate whether the data should be send to Speckle. When I upload the script to ShapeDiver, the boolean toggle does not appear in the inputs pane?
As far as my memory goes booleans are normally supported, right? I have included the new copy of the file.
rect.gh (13.5 KB)
Ok, I will try this. No big deal to put an output there!
Speaking of which, for the use case I am envisioning I would need to retrieve a link to the Speckle version which contains the result of the computation.
Using the Speckle V2 connector, a link was returned that would lead to the specific version that was uploaded. Unfortunately, with the V3 connector this appears not to be the case anymore. Do you know of anyone at Speckle that could have a look at this?
More specific: the output of the V3 connector does not contain a commit ID. Maybe this can be added in a future version of the connector or maybe someone from Speckle knows other workarounds?
Screenshots of both connectors:
This is indeed a difference in the next-gen connector. Note that the publish component always creates a new version, and that the link of the model you are using as input can then be used directly to visualize the new published version. However, if you want to store and retrieve a specific, older version, this is something to ask to the Speckle team (you could try on their forum).
