You can try to turn “read full layer path” option on in the RHatt component - this will read the full nested layers path. This way your blocks will be named something like this “parentLayer::nestedLayer”
Hi Evan - if you un-block and then drag onto the same Rhino as before, it does not work - you need a new session of Rhino. Here’s the latest that I have -
Yes it does. The thing is I didn’t had it saved from when I installed at home, and when I tried researching it at work I got an older version by accident that was running out of index or something. It took me a while to realize I had a wrong version.
Having an area for scripts on food 4 rhino would had avoided that.
Hi Pascal,
This ExplodeBlocksToLayers plugin is very useful. We recommend it to our customers often, but we have to provide instructions on how to install it. I am trying to make this easier for our customers, but you haven’t provided any attached licensing for the plugin.
If you could provide the source code, we could just include the command in our plugin, which would be ideal. Or if that isn’t an option, can we send it to our customers in an RHI file? We can certainly provide any attribution required and would not charge money. It’s just useful for our customers and we are looking for an easier way to get it into their hands.
Hi @pascal
Would it be possible to make a version of this most useful plugin where the sublayer organization (and distribution of the objects) of the block is maintained? What I mean is this: Let’s say I have a block called “Chair”, and inside are 3 objects on 3 separate layers. Organized like this
Chair (top layer)
-Back
-Seat
-Frame
I have eg. 10 of these blocks and would love to explode them and have them distributed like this:
Chair 01 (insertion layer of block)
-Back
-Seat
-Frame
and then
Chair 02 (insertion layer of block)
-Back
-Seat
-Frame
etc. for all 10 chairs.
I’m exporting massive amounts of furniture to Keyshot (hotel restaurant) and it would make life much easier to have the exploded blocks a little more organized when exploded. In the plugins current version, all objects in the block go on the same layer - it makes assigning materials in Keyshot a bit of a hazzle.
TIA, Jakob
Hi Jakob - let me check - I have not looked at what this thing does in quite a while… @Normand - this is what I get here-
Isn’t that what you are asking? Note there is a command line option to make new layers or keep insertion layers - this result is from the former, I think it’s the default in the latest. Shout if I am missing the point…
Ah - maybe the numbering on the sub layers is what is not right - is that it? It would make sense not to do that I think.
I am not sure I understand this:
What if there is more than one instance on a layer?
Hi @pascal
Either I’m doing something wrong or I’m really bad at explaining myself (or both ). I’m attaching a simple test file for reference.
I have an embedded block (buffet counters 3D). The original objects in the block are on the (sub-)layers in “Furniture blocks>buffet counters 3D”.
The instances of of the block are on the (sub-)layers “buffet counters>buffet counters 01, …02, …03 etc”. As shown on this screen grab:
What I would like, was for the block - upon explotion - to distribute the objects of the now exploded block to corresponding (and automatically created) sub-layers on the “block-insertion” layer, so that it looks like what is on this screen grab:
Ah, @pascal - I get it now! Sorry for being thick! I need to have the elements I want distributed on layers as nested blocks inside the main block, not just as layers and geometry. If I want the layers tabletop, cabinet etc., I need them to be sub-blocks inside the main block
Thanks for the help!
-Jakob
Hi Jakob - yeah - that is what the thing does now - un-nests the blocks - can you work with that?. I see that what you describe might also be useful though. I’ll cogitate…