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.
"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.
Daniel Hambleton
Try Ortoo.
Currently it only works for mesh geometry...
Oct 6, 2013
Thomas Perkov
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.
Oct 6, 2013
dominic
"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.
Oct 6, 2013