I am nesting a number of blocks into other blocks. In some cases the ‘child’ block is featured in various other ‘parent’ blocks. When I insert the ‘parents’ into the top level file (grand parent) I recieve the conflict name message which is fine but what is annoying whilst I have given Rhino the instruction to use the block whenever I reopen the grandparent file it immediately highlights a name conflict and not maintain my original instruction.
Lets say I have one bolt (that is blocked and linked) and its nested in 100 individual blocks (parent) and those 100 blocks are linked into the grand parent file I will recieve the conflict message 100 times and thats quite time consuming.
Just as an add on it would be great if Rhino presented a full list and three coloumns where one can toggle the option and in the case Im raising would allow a batch option.
Hey @IanB how are the blocks linked between base, parent and grandparent?
You will probably get conflicts if your blocks are embedded or embedded and linked because there’s an actual copy of the blocks in the file that conflicts with the newest block changes coming. If you choose to link your blocks instead, you should be able to choose to update them via the block manager and avoid conflicts altogether. In saying that, keep in mind that link blocks don’t exist in the Rhino file, so pay attention to keep the linked blocks and the target rhino file together, or if you know that the block state is “final” you can change the blocks back to embedded so that they stay in the file. This is also important if you’re using block files that may change overtime but you need the current state of the block to exist as they were in your model.
Nested block management can be messy in Rhino so I would avoid deeply nested blocks if possible.