Thanks for adding the new Bake Content component. Unfortunately the update feature doesn’t work here. I see the object which should be baked just for a very short moment and it disappears.
I’m not so sure about the Mode choice between Insert and Update inside a two right click menu. Maybe this could be just one right click like in the User Text component?
In the long run, it would be great if these entries could be set by a single right click and ‘i’ or ‘u’…
When an existing Bake Content component is copy / pasted inside a Grasshopper definition, the stored tracking for the Update mode is copied too.
I think this is problematic and I’m looking forward to a better solution to keep track of duplicates.
bake_content_copy_paste_problem.gh (9.9 KB)
@AndyPayne I’ve been using the bake content component on a few projects and some things start to make sense. The problems mentioned above have vanished.
Recently I saw a warning message that the content in branch 18;0 could not be replaced. Does the bake content component listen to the tree structure?
This example is for a scenario where I specify a number of points for the selected branch. The bake content component unfortunately ignores the branch path and baking replaces the points no matter in which branch / box they are.
23_06_16_bake_branch_aware.gh (21.1 KB)
My first attempt workaround is to check if the points are inside the box in the selected branch. It works but I’d prefer a solutions that compares branch paths.
23_06_16_bake_branch_aware_culled.gh (21.0 KB)
Next attempt with paths stored as user values:
When baking the points of the first branch, no other points exist and just the first branch points are baked with the path {0} stored as a user value. Switching to the second branch, the points from the first branch are referenced and they get paths assigned according to their user value. The referenced points data tree is split and the geometry of the negative data set gets a new user value.
Each box gets a user value with the point count which can be referenced again. Metahopper can be used to set a slider value to the saved value.
23_06_16_bake_branch_aware_update.gh (32.9 KB)
The only downside is that baking always bakes all objects. I’m not sure but maybe this could be avoided by replacing objects in their respective paths only?
I see this as similar to baking two branches with two different ‘Bake Names’ which would require a splitting the separately controlled branches at the end…
When the number of points is know for all branches, this can be done with one bake component. I also have more than two inputs and I don’t want to have 10 inputs for 50 branches = 500 sliders…
I can see the benefit of branch aware but not sure how that would be possible, it seems like it would require a branch Guid that would not change if simplified and be smart enough to know not to bake things that haven’t changed.
It was simple with EleFront since the bake name could be set per branch.
Was branch aware baking added @martinsiegrist ? I haven’t had a chance to check yet
I don’t know what they changed but the file above works. The goal of the definition is to bake two cubes and store the number of points as a user text on each cube. Then bake points into a cube with two sliders, one selecting the cube, the other for the number of points. The points get a user attribute ‘branch’ 0 or 1. All objects named. It’s a stripped example…
I see, thanks for the explanation!
