I’ve finally upgraded to the Gen 3 connectors for Rhino/Grasshopper and I’m trying them out now. The structure of the Speckle Data Object made me wonder whether it was possible to modify the geometry of an SDO before sending it back up. I tried several permutations of this by doing something obvious like scaling all of the meshes by 50%.
No matter which permutation I used, it looked like it worked; previewing the output data showed the modified meshes rather than the originals. But when I published the model, the geometry remained unchanged.
Is this workflow possible? If so, what am I doing wrong?
Hey @johnfechtel , it should be possible to modify just geometry on a data object, but there may be a bug in the publish node - I’ll investigate and let you know when there’s a fix
Hi Claire, thanks for checking on the geometry modification. I’ve also attempted to merge properties using the same workflow, but without success. I wonder if it is an issue with the way I’m approaching the setup? Or perhaps a more systemic issue with modifying existing Speckle objects?
Hi Björn, I apologize for the late response. From what I can tell I’m taking the same steps you are and with the same components, but here is the rest of the relevant part of the script:
I haven’t been able to reproduce this - the changes are reflecting as intended. Maybe to take a step back for me to get the whole picture, are you receiving a model from a Speckle project, mutating the mesh and trying to send the modified geometry back to the original model? What happens if you publish to a different or new Speckle model in your project?
Thanks for the patience on this. We were able to reproduce; the issue was only only load → edit → publish workflows. v3.8.2 which we’ve just released includes a fix for this. You can now mutate geometries of your SpeckleDataObject as expected
Upgrade to the latest version, give it a spin and let us know!
