I have a block instance he properties of which, when it’s selected, tell me it’s ONE block instance. When selected it’s a darker highlight selection colour than usual, and the gumball doesn’t appear anywhere.
I can select it but neither delete it nor block edit it.
I can explode it and delete the resulting objects (which after exploding have the usual highlight selection colour) after which an instance – or maybe the same instance - of the block remains. It appears I can go on with this forever. The block never goes away.
Any ideas what’s happening here and how to get rid of this instance?
Thanks Dale, I know. The project’s 1.8 GB. And proprietary, so I have to strip things out before I send it anywhere. Doing anything with a file that large can take a lot of time. So I thought I’d just see if anyone had any ideas first.
But it’s gone now anyway. I guess it was some sort of ghost because after a couple of crashes (this project’s so huge that crashes are frequent) and resaves I don’t see any sign of it. I’ve seen this a couple of times before over the years. The project takes up about 20 GB of ram when it’s running, so maybe it’s a memory management issue when things get that big.
Were you just selecting the block and running the ‘explode’ command or were you running the ‘explodeblock’ command? Typically I run ‘SelBlockInstance’, ‘ExplodeBlock’, ‘delete’, ‘purge’.
I’m in the habit of not using ‘explode block’ because I almost always want to preserve the nested blocks as blocks.
Maybe it would have made a difference here. In this case I could have used it, because this particular block was a nested block which had been removed from a block.
However, to delete a block instance shouldn’t require any exploding first. Something was up. Ghosts.
1 Like
When Rhino crashes, do you submit the crash report?
– Dale