Duplicate layer and block behaviour

Rhino Rhino for Windows
1

I duplicated a layer(with sublayers) with objects. Some of the objects were blocks. They do not show up in the new layer but i can see them in the original layers. Every block has a copy which says it is on the duplicated layer. It is also deleted when i delete the duplicated layer.
When i delete the original layer it is gain and when make the original layer not visible they also disappear.
How can i fix this?

Regards, René

2

Hi Rene- if the objects that are inputs to the blocks are on Layer A and you select them and make a block of them on Layer A, then duplicate Layer A to make Layer A Copy, the block instances that were on Layer A are copied over as expected, but the underlying inputs to the block, that is the objects in the block definition, which you no longer can see, are still assigned to Layer A. So layer A visibility still controls the copied instances on Layer A Copy.

Does that make sense with what you are seeing?

-pascal

3

Hi Pascal

that does make sense but it does not solve the issue. Should i explode the blocks and then copy the layer? I would rather not.

Regards

vriendelijke groet, René van Corven

atelier van corven logo paars

Atelier van Corven

Celebesstraat 1

6707 ED Wageningen

Tel: 06 26 552555

www.ateliervancorven.nl

Van: Pascal [mailto:steve@mcneel.com]
Verzonden: donderdag 15 januari 2015 18:01
Aan: info@ateliervancorven.nl
Onderwerp: [McNeel Forum] [Rhino for Windows] Duplicate layer and block behaviour

Afbeelding verwijderd door afzender.

http://discourse.mcneel.com/users/pascal pascal
January 15

Hi Rene- if the objects that are inputs to the blocks are on Layer A and you select them and make a block of them on Layer A, then duplicate Layer A to make Layer A Copy, the block instances that were on Layer A are copied over as expected, but the underlying inputs to the block, that is the objects in the block definition, which you no longer can see, are still assigned to Layer A. So layer A visibility still controls the copied instances on Layer A Copy.

Does that make sense with what you are seeing?

4

Hey Rene,
I had a similar issue with a block that I created within a file (as opposed to an externally linked file, which is normally how I work with block components). This was my work around. Surely there must be a better way, but none the less, here you go:

  1. In the BlockManager export the problem block to file using a modified name.
  2. Back in the file insert the Block file that you have just exported (hence the modified name).
  3. Call ‘ReplaceBlock’ and follow the prompts. It will have you select a target block for replacement and the block you want to replace it with. You can manually select within a viewport, or use the BlockManager.
  4. I then deleted the initial instance of the new block.

This seemed to solve my layer visibility control problems. It wasn’t too tedious, but I was only experiencing a problem with a single block instance. And like I say, there must really be a better way.

d

2 Likes