Grasshopper Rhino - Bake - Content Cache

The idea behind ‘Branch Names’ is you can use it to isolate the full set of objects and its blocks, materials, linetypes, hatch patterns. Everything is nested under a Prefixed name. A cache becomes a “nested” sub-model inside your main model.

This way there are no conflicts with the names, in this example I push a block called ‘Column’ but on different options, if you don’t Branch Names the block is redefined and both options share the same block.

Same happens on objects names so you can differentiate between Column 1, 2, 3, … from ‘Option A’ and ‘Option B’.

An other way to use it may be by team name, by user name, or by discipline, this way there will be no conflicting names between teams, users or disciplines working on the same file.

It’s up to the user what the cache name means on its workflow but the feature is there to help avoid name conflicts.

I think that, to make this more flexible, the user should be able to pick which types he wants to branch, and be able to disable the name branching on objects, or maybe on anything but blocks and layers, or whatever he decides or need on its workflow.
Right now is all or nothing. :pray:

7 Likes