Block selection on crack in BETA (6.0.17325.8311, 21/11/2017)

See for yourselves

Selecting a block highlights other instances.
Blocks in Rhino…

The problem is still here in BETA
(6.0.17339.11131, 05/12/2017)

Hello - if you have not, please send an example file to If the file is large, please send via (SaveSmall & zip)



Will not do.
This just shows how blocks are neglected by the development team.
It is appalling to find that sort of bug, specially considering how overdue Rhino V6 is.

1 Like

We’ll wait to fix this bug when someone can help us reproduce the problem. Nobody else is seeing and reporting it, yet. I’ve made my own sets of blocks and models, and can’t make Rhino do what’s in that video.

If you change your mind about helping out, it would be helpful to send any custom display mode settings, too - my guess is that they are related, somehow.

My guess is that all the people who need blocks have either moved to another CAD or completely lost hope on improvements in that area, just as I have.
Neglect of blocks is on the verge of dis-respect : there has been countless threads about very simple and practical enhancement wishes, and …nothing.
Do you expect us users to continue and waste our times helping you get your sorftware out of misery when there is nothing in return ?

1 Like

Hi @ osuire.
Your video shows something very unique happening and using it as an example would benefit both users and developers.
I have tried many “things” but can not replicate behavior like you have illustrated.
I can not live without the use of blocks, as it reads that you can’t, so it would be good to sort out any potential issue.


I have to agree with @osuire here. Blocks in Rhino are very limited and buggy, it’s always been. I really think that Blocks should have been rewritten from scratch for V6, trying to patch something that is not well designed from the beginning is nonsense.
From my experience, the issue with blocks, besides been really limited in functionality, is that you have to use Rhino in real projects to experience its limitations and bugs. Many times, you create a few blocks and everything is “ok” but then, you start experiencing odd behaviours like the one Oliver is talking about. I don’t know how many times I’ve had problems using block edit…

and where else might it be used? Seems like a very odd statement.

Sorry, but If you quote me, please quote all the sentence, because I think that’s not what I implied at all:

Of course I wasn’t trying to offend anyone, and I’ve been using Rhino for most than 10 years, so I’m not implying at all that Rhino is not production ready. What I was trying to say, is that developers might have a hard time trying to reproduce this bugs or limitations because from my experience this problems came when you work with complex files, something triggers that kind of bugs… When you open a blank file and try to reproduce the bug you might not be able to do it.

As a said in my previous reply, I think blocks are one of the weakest part of Rhino, and I think the whole concept should be resign from scratch. Please, take a look at how SketchUp or Illustrator deal with this concept, they are really good at this, and there is no need to reinvent the wheel…

Hi @jespizua.
No offence given, no offence taken.
Projects are the only place to find odd behaviors in blocks, but in my experience, it is surprising what may have happened when a block has been edited, and often leads to unwanted behavior - so any analysis has to start with the block object.
I am an Autocad, Revit and Rhino user, so we won’t start on the way SketchUp works.
All to our own client base and workflows,

1 Like

Block selection is still on crack.

Here are my settings :

Rhino 7 SR0 2018-2-21 (Rhino WIP, 7.0.18051.5145, Git hash:master @ abb89f2e7aebaa5c64d46940077507f4bdc9963b)

Windows 10.0 SR0.0 or greater (Physical RAM: 16Gb)

GeForce GTX 1070/PCIe/SSE2 (OpenGL ver:4.5.0 NVIDIA 385.28)

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On

Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: Height

Vendor Name: NVIDIA Corporation
Render version: 4.5
Shading Language: 4.50 NVIDIA
Driver Date: 8-9-2017
Driver Version:
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8 GB

C:\Program Files\Rhino WIP\Plug-ins\Commands.rhp “Commands”
C:\Program Files\Rhino WIP\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino WIP\Plug-ins\RPC.rhp “RPC”
C:\Program Files\Rhino WIP\Plug-ins\AnimationTools.rhp “AnimationTools”
C:\Program Files\Rhino WIP\Plug-ins\RhinoRender.rhp “Rhino Render”
C:\Program Files\Rhino WIP\Plug-ins\rdk_etoui.rhp “RDK_EtoUI”
C:\Program Files\Rhino WIP\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino WIP\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino WIP\Plug-ins\RhinoCycles.rhp “RhinoCycles”
C:\Program Files\Rhino WIP\Plug-ins\Toolbars\Toolbars.rhp “Toolbars”
C:\Program Files\Rhino WIP\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino WIP\Plug-ins\BlockEdit.rhp “BlockEdit”
C:\Program Files\Rhino WIP\Plug-ins\Displacement.rhp “Displacement”