VisualARQ Bake component bug -> layers

VisualARQ
, ,
1

Hi @enric and @fsalla

I saved this component from some topic here, I think @enric is the author.
Now that I need to put it into proper use, I realised that there’s still a bug in it concerning layers.

  1. If a layer does not exists prior activation, the component will create the layer, but the baked object will go to active layer instead.
  2. If the defined layer is a sub-layer, then the object will go to active layer regardless if the sub-layer exists or not. So sub-layers do not work at all.

Could you iron out the kinks here?

kuva
kuva2146×796 117 KB

VA_bake.gh (17.7 KB)

2

Hi @Toni_Osterlund you are right, that VisualARQ Bake component doesn’t create a new layer when you bake objects.

However, since now the VisualARQ objects work fine with the Content Cache component, we will put the efforts to make the VisualARQ objects compatible with the Model Object component, so you can assign the Layer and other attributes directly from there.

1 Like
3

Hi, @fsalla thank you for the explanation. And appreciate you looking into this.

Could you show a minimal example of Content Cache baking with VARQ objects (name + Layer)?
I’m just migrating to Rh8 and briefly tested it, but I could not wrap my head around it.

4

When VA objects work well with the Model Object component, you will be able to bake it to a new layer this way:

image
image1061×452 85.2 KB

As you may know, the Content Cache has different functions, including the Bake option similar to the one you are using:

image
image530×407 15.8 KB

1 Like
5

@fsalla
Seems to run perfectly - thank you! :folded_hands:
I must’ve missed some step when I was testing with the Model Object Bake.