Hi @Czaja I don’t understand what is the problem here. VisualARQ objects are recognized and listed inside blocks as blocks. Everything looks fine in the video.
@Czaja I get it now. It happens when you create a new block from the “Create Unique block definition”, in the Properties panel. While we revise this, can you handle it by exploding the copied block instance and creating a new block definition from it?
Yes, I can use this workaround for some time. Thanks.
Another way to break it. Definitely a corner case, but I’m reporting it as a pursuit of robustness.
First I show using the example of a Cube (VA Furniture) and a cylinder that together form a Block, that the system works. Then using an example from another thread I show that a VA Element created from a Rhino Block and enclosed together with an instance of that Rhino Block inside a single block still means that we can break the VA Element and permanently convert it to a regular Block Instance. A bit confusing, but that’s how it is.
VA nested block.3dm (132.3 KB)
1 Like