Referencing a slab in grasshopper and editing its geometry

VisualARQ
1

In the attached .gh file, i am referencing a slab, i deconstruct it and I try to substract a top layer’s part to replace this part with the material of the second layer. It’s a first step of wrapping slab’s layers gh system.

SLAB-WRAPPING.gh (18.7 KB)

Can anyone explain to me how we do this with context cache? I was able to pull-push-bake the geometry, but it does not replace the slab but it creates a separate copy.

2

Hi @GabrielB I’m not sure what you are trying to achieve. But the Bake action of Content Cache doesn’t replace the referenced object, but bakes a new one, (if I’m not wrong).

3

Hi @fsalla . Actually the push action of content cache, does replace the referenced object, with a name. See below:

push-content-cache

Same applies in visualarq objects, check below:

push-content-cache-va

The difference is that when it comes for visualarq objects and not rhino geometry, a new layer is being created the Grasshopper::Brep as you can see in the bottom of the GIF. This layer is not created when setting a layer for rhino geometry. This IMO should be investigated. Or maybe I am doing something wrong here. I’d like some explanation on this in order to handle this as a bug maybe.

In the above examples, I am creating the geometry from grasshopper from scratch. My topic here is about next step. When referencing a slab in grasshopper that was created from rhino workspace, if want to edit this slab the things are different.

push-content-cache-va-2

Let me explain:

I just want to edit objects that were created in the rhino workspace. I can understand that it’s an incosistent programmatically, editing the input of the definition. But with the content cache maybe somebody has investigated the content cache actions, to either purge, pull, push or bake. In this case, we maybe would pull the Geometry and go back and push the new geometry replacing the same object. I kind of believe that with rhino geometry it’s possible.

Here are the simpler than the initial .gh of the topic.

gh-testing.3dm (4.8 MB)

testing-gh.gh (24.3 KB)

4

Hi @GabrielB

This is a different situation, because you are creating the geometry in Grasshopper (not referencing it from Rhino).

The Content Cache doesn’t bake VisualARQ objects to specific Layers when they go through the Model Object component. This affects the objects referenced from Rhino, because it seems to work fine with new objects created in GH. We need to provide support for that.