This command work here using the 5.0.2 build that was released yesterday. The command even auto-completes when entered into the command window.
Oh myā¦I think I found part of the problem.
Iām running an old Beta version. Itās 5.0 Wenatchee from 2014.
Thatās crazy. Iām actually using a new Mac Pro, and I had no idea that there was such an old Beta. For years, Iāve run and tested the older beta versions, and they always āself-destructedā and prompted me to the next version, each time. But this old copy just opens up.
So, Iām guessing this could explain a number of things, right? Looks like I need to buy the new version!
That would be the first thing to sort out, yesā¦ =)
this one purges the block definitions-
ExplodeBlocksToLayers.py (2.8 KB)
-Pascal
So, Iām likely dead in the water with what I have, and need to buy the final (?) commercial release? Is that what 5.0.2 build is, from Daleās link above? No more betas.
Can you use the evaluation version for now?
http://www.rhino3d.com/download/rhino-for-mac/5/evaluation
-Pascal
Okay. Iām up and running with the 5.0.2 Evaluation.
I can also now get the ārunpythonscriptā command to initiate. Howeverā¦when I try the scripts you provided, I get a lengthy error message, and nothing still happens to the objects or layers.
Is it possible that this has more to do with the STEP file I imported, than anything else?
Are you allowed to select the object?
It worked here on the macā¦ better give me the error message.
-Pascal
Would it be possible for me to email you a test project? Iāve imported a smaller STEP file, so itās a small, less complicated project. However, it still displays the core issues Iām having with seemingly any of the STEP files that I try to process.
Thank you. I just did so.
There are no block instances in that file- it appears theyāve already been exploded. Send me the step file please.
-Pascal
I just sent you the original STEP.
But thatās really strange, as I just opened the Rhino file I sent you, and by clicking on the object, it says āone block instance added to selectionā. And from there, if I āexplodeā it reveals more block instances.
It worked here- open the step file, run the script, select the object, poof- lots and lots of nested layers under Defaultā¦ Dunno if the names are super useful though.
-Pascal
I have no idea. I just sent you a screen grab of what happens when I do the following:
- Start Rhino
- Open STEP file
- ārunpythonscriptā command and select your script
- select block instance object
- hit āenterā
- what you see in the screen grabā¦
I see- that looks like itās choking in the RhinoscriptSyntax part - but I do not get that here. Iāll investigate. Meantime, I will upload the layerized rhino file in case it is useful.
-Pascal
Thank you very much! I really appreciate the continued assistance. And yes, please do send the Rhino file back. While itās just a single part to test this STEP issue, it would be extremely helpful for me to see at least the end result of how it should look, once your script works its magic!
Hi Pascal,
have you update the script?
It would useful also to me.
Thank you
Ivan
No, it creates the first level then I get this message
Thanks
Ivan