How does one make an array of holes a block instance?

Hi, V5
I do need a ring of holes, I am very aware that anything that is repeated in Rhino causes major slowdown.
Tis file of mine sees anything pasted from it take 15 secs to appear in a new file, ditto anything pasted in, and takes a while to save. Dare not slow it down any more.

I see someone doing a perforated plate with hundreds of holes, I feel for him !

Crosses wont do as the holes need to be see through as other items run through them.

How does one make the hole a block instance ?

Steve

Hi Steve -

The answers to your question in 2014 still stand:

-wim

Hi,
I had hoped that as that was V4 days, things would have moved on by now.
So what if one needs loads of holes, are we faced with rhino slo mo and meltdown, as I was able to instead use crosses, but there are times the appearance is needing actual holes.
Someone did ask for a block holes, what came of it ?

Steve

Steve -

It’s not the invisible voids that you want to see - you’ll have to create a display mesh for the positive volume. At that point, with lots of holes, things will slow down.
-wim

Possibly due to the presence of large bitmap images in the file(s) - known bug/limitation in V5 and V6 which will not be fixed.

Possibly because the file is pretty large?

Explode the block instance into real geometry and make your holes. If you need multiples of the same item with the holes, re-make the item into a block afterwards and make copies of the block instances where needed. Blocks only help reduce file size and allow for instancing of similar objects, they do not make the display faster - in fact they might actually make it significantly slower in older versions of Rhino.

Hi @Helvetosaur . I am eager to hear how based on your experience, or your client’s: how does Rhino 7 perform in this regard? Or Rhino 6, if not 7?
Thank you.

I only know what I read here (if my memory serves me well) - that there seemed to be a number of threads here concerning significant display slowdowns with lots of blocks in earlier versions, some of which has been addressed in V7. Maybe my memory is faulty, I personally have no experience with this.

1 Like

Thank you for the reply Mitch.
I can attest to the same behavior on Rhino 5 and 6. I haven’t checked on 7.

Hi @djordje

From a different thread somewhere (possibly on the LBT forum), I noticed that you are running an ancient version of Rhino 6. If updating to the current version would help, I can’t tell. You’d have to test or provide a specific file.
-wim

Using block instances for holes only makes sense if the shape and the hole pattern is regular somehow.
BlockHoles_V5.3dm (1.2 MB)

Another way would be to “fake” the holes with transparent textures

Hi @wim ,
I am running on Rhino 6 SR30.
image

For some strange reason Rhino never informed me about the release of SR31 and SR32.
I can update to SR32, but in my opinion the issue with blocks slowdown has been around since Rhino 5, throughout the whole Rhino 6. I will see if I can come up with some custom example, as I can’t share the actual .3dm model.

Hi @djordje -

Just to make sure… the current stable release of Rhino 6 is 6.34.

Thanks!
-wim

1 Like