Need block system improvements!

It seems to me you have change the way you work.

I am not saying blocks inside Rhino don’t need a good overhaul. They certainly do, but perhaps Grasshopper or Worksessions or even switching to layers instead of blocks could be more appropriate.

Also, have tried using scripts? There are enough handy methods do edit nested blocks and the objects inside them.

What I like about scripts is that you can make the functions work exactly how you like.

Just tell me why it is impossible to edit non uniformly scaled blocks? I saw a post where one guy said that nobody touches blocks so long because in terms of codding this is “pain in da ass” as he said.
Need to say that i know at least several arch studios that want to switch to rhino but the fact that the block system is so strange keeps them working acad+sketchup workflow.
This will make rhino one step closer to be called user friendly(not only coders friendly)

Why would you scale a block non uniformly instead of creating a script that changes the data (the 3d objects) non-uniformly?!

Because this is direct modeling that is much faster, and allows to use core base rhino tools advantages.If you are talking about grasshooper, then this approach requires to keep all geometry procedural till final bake and all attributes like materials need to be defined inside grasshopper that is not the most comfortable way to work. Also not everything is that easy to define with script, sometimes it is just easier to do direct way , but to do that you will need to bake that is breaks the procedure. Maybe i just have bad experience or just lack of it . Is there any tutorials or just showreels that shows that way of work with big detailed architecture project?
And just for a second , imagine how easier lide would be if blocks in rhino would work like components in sketchup(*i belive that this is not profesional programm, but but despite it just doing super base commands that just works and this makes it much more trusted by people)!

As I said, blocks do need an overhaul, but also your way of working I think is wrong.

From my point of view you should not use blocks this way, but I’m not that kind of architect.

I agree, it would be handy to have non-uniform BlockEdit.
My understanding is that it is not enabled, because in some cases it could produce bad results. Ideally, if this is predictable, a warning would be added, or it would be allowed to work as an option, ‘at user’s risk’, but it should allow to work in basic cases. Imagine a simple scenario where your block is just a box. Non-uniform version is scaled along Z-Axis only. It should be perfectly fine to edit the non-uniform version of it.

There is some more info ‘why’ in this thread:

but I am wondering if these special cases are detectable and could be prevented, while allowing “normal” cases to just work.

One of Rhino’s strengths is the flexibility of allowing user to do almost anything, even at the cost of producing weird, bad geometry. The non-uniform block edit issue is one of the exceptions from that rule.


1 Like

I definitely would welcome editing of non uniform scaled blocks as well. And I’m not an architect.
And double clicking blocks inside blocks
And unlock not affecting objects outside the block being edited.


Yes on both of them. Is the season for V7 wishes officially open now? :wink: These are good ones.

1 Like

Isn’t that possible now with sub-object filter on?

I’m not sure what you are referring to. I think we are looking for editing nested block instances. Now double-click only lets editing top-level blocks. Unless I am missing something.

1 Like

You’re absolutely right.

No, I guess I am missing how you “ground” architects use blocks.

I’m going to approach this spirited request and conversation from a different angle!

For a long time I used SketchUp so I am familiar with some of the reasons for the request. But having more recently worked on a project with a team using Solidworks, I would propose that it would be nice to opt for two types of Block navigation/edit style based on the design application:

  • Architectural: Block editing experience closer to SketchUp components.
  • Engineering: Block tree navigation more like Solidworks/Inventor/Fusion360 - with a panel that can be permanently docked.
  • Original: I know I said two, but I don’t want to alienate anyone who likes the current Rhino3D Block Editing style.

There sure are some quirks in Rhino… like the hard lesson you learn the first time you save and exit while editing a block! I’m all for improving my ways of working, but I’m fully open to supporting the McNeel development team with experimenting on improvements in this area.

just an idea, maybe somebody can post a simple example drawing with 2 non uniform blocks on it with a example of an editing problem on it so some of us non educated people can understand, learn, and work on ideas to solve. Break it Down.


Agreed, I’m not following what they are looking for at all.

My $0.02

This is why I said.

By “ground” I do not mean anything negative, I am naval architect so I needed a way to differentiate :smiley:

Make a box, use Block command to turn it into a block.
Now double-click : you can enter the BlockEdit mode. Great. Exit the mode. Scale the block 1D in any way.
Double-click now. Can’t do it for non-uniformly scaled blocks. The argument is in many cases it should be OK, but in some, it won’t work. We’d like this to work for the cases it can.


Why would you scale the block instead of scaling the objects inside when you open it for edit?

What is the purpose of that?

Can you give a practical example, I cannot understand?

Imagine your block is a tree. You populate model with them, each of them scaled slightly randomly, in a non uniform way, for more natural look.
With that setup, you can’t double click and edit any of them, not even change block object materials that does not change model at all.
This is just one of a lot of examples of non-uniform scaled block uses.
Another one could be a simple column with different lengths, for more technical-minded folks to imagine :wink:


I understand now.

Why don’t you use Grasshopper for all this?

I think also if you have a script that will manipulate the object inside the block will also change all instances of that block.