Send and receive geometry (.GH -> .GH) ?

Replies to This Discussion

Permalink Reply by David Rutten on October 6, 2013 at 3:55am

It's possible I think, but quite complicated.

You need a Geometry Cache component in both files, one which is baking and one which is receiving. Then the 3dm file has to be accessed by both machines using worksessions. But it still requires several mouse clicks to transfer the data, even when you're all set up.

Note, I haven't actually tested this.

--

David Rutten

david@mcneel.com

Tirol, Austria

Permalink Reply by David Rutten on October 6, 2013 at 4:01am

Well it works, but it's pretty damn annoying.

Using WCF it should be possible to set up something like this with VB/C# components, but my experience is that WCF has a lot of problems sending and receiving data through clamped dow systems...

--

David Rutten

david@mcneel.com

Tirol, Austria

Permalink Reply by Xavier AM on April 6, 2017 at 8:24am

Hello David, 

I am setting up a WCF component to communicate with Grasshopper from the outside world (another .NET software), as you suggested in this old post :

http://www.grasshopper3d.com/forum/topics/how-can-i-use-grasshoper-...

So far I managed to create a service passing values from the outside to a dedicated component inside an opened definition, and I am quite proud of it :-). But I am wondering what are the problems you are mentionning  here (clamped dow systems?). Would you mind sharing your experience or readings about it?

Thanks for your time!

Cheers

 

Permalink Reply by Daniel Hambleton on October 6, 2013 at 7:34am

Try Ortoo.

Currently it only works for mesh geometry...

Permalink Reply by Thomas Perkov on October 6, 2013 at 8:09am

Hi David and Daniel

Thanks for the answers! :-)

I think I can solve my problem using 'reference clusters'.

I didn't know the geometry cache component and the functions in ortoo existed. I can use the geometry cache component in another part of my project. I would definitely try ortoo and specific the ortoo browser later this week! In need to send surfaces and not meshes in this project.

Permalink Reply by dominic on October 6, 2013 at 8:23am

"You need a Geometry Cache component in both files, one which is baking and one which is receiving"

This sounds like it would be very useful.... in a 'pull' in addition to a 'push' mode.

Would it be possible to version the updated 'baked' Geometry Cache... so that the 'receiving' Geometry Cache in the external file and compare its version to the subscribed 'baked-in-another-file' version and reload the GC as required? This would turn the GC into a smarter version of Rhino's Linked Blocks.