Geometry Cache Not Able To Retrieve GUIDS?

Im anewbie to the Cache component in GH 0.8.11

One advantage would appear to be to retrieve chunks of previously volatile geometry, defined as a cache and subsequently baked using the cache component, and access the GUIDS of these new objects.

However, this does not seem possible see attached.

Am I missing something?

Cahce.png

Replies to This Discussion

Permalink Reply by David Rutten on June 28, 2011 at 1:04pm

Hi Duck,

there's an option in the Cache object menu called "Maintain references" that allows you to retrieve the geometry with guids or without. If references are maintained, the loaded geometry 'knows' whence it came and will be subject to auto-updates, if not (the default) geometry is imported as 'dumb' data.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Steve Lewis on June 28, 2011 at 1:22pm

Cheers, that works. I forgot to re-click the bake or load geometry icon after changing to maintain references settings!

Permalink Reply by Steve Lewis on June 28, 2011 at 1:44pm

David

would it be possible for an option where if we are feeding in exisiting referenced persistent geometry, we dont have to rebake to a new referenced geometry to be able to subsequently load and access a user defiend geometry cache. i.e. i dont want two sets of the same geometry with different GUIDS.

Having said that, isnt that why we have Groups? Can we access a group component by its name created within GH?

Permalink Reply by David Rutten on June 28, 2011 at 2:49pm

I don't get it. Why would you bake already referenced geometry?

Groups in Grasshopper are fairly limited in their application. They are only really useful if you want to transform a bunch of objects together. You can always achieve this anyway by carefully crafting the transform data, but groups just make it easier.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Steve Lewis on June 28, 2011 at 4:14pm

For filtering. Say if serveral Breps represent the slabs of a building in a model - persistent data. I want to easily select those breps, i.e. group or cache them to a geometry cache component, and use them for reference furtherdown stream as needed for inputs to other components. Say if i have a slab A set, or a slab B set. Referencing this as separate geomertic Slab/Slab B caches makes work easier. I dont really want to have to create extra objects in my model for this.

RSS