Geometry Cache Broken?

Is Geometry Cache Broken? I thought I could use Geom Cache to bake some geometry, then edit it in Rhino, and then retrieve the edited geometry and continue using the new geometry in GH.

I must be doing something dump. I thought I used to be able to do this.

Thanks in advance for any help you can offer. See attached file.

Stan

Attachments:

GeomCacheTest.gh, 3 KB

Replies to This Discussion

Permalink Reply by David Rutten on April 19, 2012 at 2:05am

It's not broken, but Geometry Cache has different behaviour depending on how it is connected.

If it is not connected at all, a warning is displayed.
If it is only connected at the left side, you can bake your geometry.
If it is only connected at the right side, you can reference geometry from the Rhino document.
If it is connected at both sides, it acts just like a regular parameter.

This information is also available in the Tooltip of the Cache object. If you disconnect your panel, it should work as expected.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Stan Carroll on August 8, 2012 at 9:11am

Hi All,

I am not sure if I am doing something wrong. I can not get the geometry to bake in Rhino. I thought the component was designed to allow me to bake the geometry in Rhino, than allow me to manipulate it within Rhino, then reload the new manipulated geometry back into the GH definition and continue my definition.

I continue to get an error that indicates I have NOT given it a unique name. It does NOT allow me to bake it to Rhino geometry so I am unable to manipulate within Rhino. However, for some reason I am still able to re load it back into GH definition.

Thanks for any sage advice you can offer.

Attachments:

GeomCashWontBake.gh, 2 KB

Permalink Reply by phillip on August 8, 2012 at 9:45am

Hi,

just opened your file - baked to rhino - transformed - reloaded back into gh.

No errors, no messages.

Strange, here everything works exactly how its supposed to.

Permalink Reply by Stan Carroll on August 8, 2012 at 9:49am

Are you using version 0.9.006? and Rhino5?

Thanks for trying it.

Stan

Permalink Reply by phillip on August 8, 2012 at 9:57am

Yes, I am.

Gh 0.9.0006 & Rh 5.0 (5.1.20801.1108)

64bit.

Latest built on both.

Permalink Reply by Stan Carroll on August 8, 2012 at 10:19am

That is exactly what I am using. Hmmm?

Thanks again.

Permalink Reply by Stan Carroll on August 8, 2012 at 11:02am

I have isolated the error.

If I make the wire connection BEFORE I input the Unique Name, it will never bake. However, if I make the wire connection AFTER I input the Unique Name, it will bake. That seems strange but that is a repeatable error.

Phillip,

Thanks again for your assistance.

Permalink Reply by Stan Carroll on August 8, 2012 at 11:39am

This component appears to be very picky about exactly what order the connections are made. If the process is done in any other order, I get errors.

You must first drop the geometry cache on to the canvas. Then give it a unique name BEFORE making the connection to its predecessor. After the predecessor connection is made then click on the bake button to create the geometry in Rhino. Then make a copy the geometry cache component and disconnect the copy from the predecessor and connect the component to the successor component.

I am not sure why it takes such a specific method to get this to work. Is it just me or is it that specific for all?

Permalink Reply by Stan Carroll on August 9, 2012 at 12:22pm

OK here is an additional nuance. When I bake from the Geometry Cache it automatically bakes to the Default layer even though I have another layer current. I worked for a long time thinking it was not baking because I had the Default layer turned off so I was not seeing the geometry being baked to the default layer.

It seems like it the geometry cache should bake the geometry to the current layer or at least offer the bake layer dialogue sometimes offered during conventional baking.

Stan

RSS