Rhino 9 Wish List

That’s a great idea. I’ve been also thinking about it for many years.

In general, having some sort of “parallel” layer system(s) would be great just for the sake of project and object organization! On many occasions, it is not really sufficient to organize your project in a single tree and browse it efficiently. It can be mimicked via user defined key-values but it is not very clear and you need to know what you are looking for. Also not very clear for less advanced users.

2 Likes

Hi Scott, I was trying to add this text to the FEATURE WISHLIST on the forum, but it came up with an error message…no matter how I try to add. As a replay or a separate topic. I reformatted it…

Then the title was too short, then too long…but still couldn;t post it…Frustrating.

Please, could you add this for me?

wish: “Array hole along curve” command

@Gijs just to be clear this is in the works for the future or not?

if not i leave this as a wish here

RH-88495 is fixed in Rhino WIP

1 Like

A post was split to a new topic: Rhino 9 Wish List - Grasshopper

I’d like to see Parasolid features as well. For holes, chamfers, fillets, etc. I like the was Plasticity 3D does this! Also, xNurbs please.

Patch in wip 9 looks like xnurbs

it’s 100% not, but it solves similar set of problems.

I see what you did there :balance_scale: lol

Is it the inner works that is different? from the text to speech demo videos it looks similar

So much new stuff I feel like I am falling behind :melting_face:

it’s all code that our dev team wrote. No xnurbs code was used in any way.

I’d have to defer to @menno for the specifics.

1 Like

Just joking :rofl:

Since you are here and available: do you think a “Array hole along curve” command would be useful?

Gijs went through my electric heating iron video bits to see what I could improve I got some very useful input this was one I could use to speed up and change my workflow

You guys probably get thousands of requests but is this something in the works or considered at mcneel already?

start a new thread for this and we’ll get it on the list.

1 Like

Rhino is getting better and better for use in architectural projects. Improving layer and class management would be another huge step in this direction. I would love to see this implemented in the future. Rhino would then be an even stronger contender against the usual CAD programs used in architecture.

3 Likes

Wish for Rhino 9:

When enabling PrintDispay in Model View, you can choose a background color (most likely white).

This would be really helpful when drawing architectural plans.For pure drawing/modeling I like the grey background, but when checking lineweights/linetypes it would be great if it could switch to a white/paper background. When activated, the colour for selected items has to change from a barely visible yellow to some other colour.

Feature Request: Ctrl+Shift Sub-Object Selection for Hatch Boundaries

Please enable Ctrl+Shift sub-object selection for hatch boundaries, so edges/segments of a hatch’s boundary can be picked and edited directly with the gumball—just like curves, polysurfaces, meshes, and SubD components.

Why this matters:

  1. Workflow parity. Hatch editing would align with intuitive 3D modeling workflows (SubD, polysurfaces, curves).
  2. Drafting speed. Right now, drafting is often a two-step operation: first move/reshape the model geometry with sub-object edits, then repeat similar adjustments on the hatches. For floor plans and iterative layout work, this double pass slows things down.
  3. UI/UX consistency. Treating hatch boundaries like other editable sub-objects would make Rhino’s selection model more consistent.

Current state & workaround
At the moment, hatch boundaries can’t be Ctrl+Shift sub-selected. To edit a hatch’s outline you have to turn control points on (F10 / PointsOn) and drag grips, or edit the source curves with History enabled so the hatch updates is impractical on larger projects. > Edit 2D hatches

Prior discussions & tracking
Earlier thread: Selecting subobject of a hatch boundary — logged as RH-72807; Wim’s reply there notes this is “not going to happen.” (for RH8) > Selecting subobject of a hatch boundary

Could the McNeel team clarify why Ctrl+Shift sub-object selection for hatch boundaries isn’t possible (per RH-72807), and whether an alternative—e.g., a temporary “Edit Boundary” mode or an editable proxy that re-hatches on commit—could address today’s two-step drafting (move geometry first, then fix hatches)?

Hi jsbzh -

RH-72807 Annotation: Hatch: Sub-object select hatch edge
From the developer:

Not possible. The only subobjects hatches have are the entire curve loops.

Note that the developer didn’t close that issue with “Won’t Fix”. It is still open and on the “Future” list. The feature obviously requires a bigger rewrite of code.

Well… Moving points is probably faster.
-wim

1 Like

Could we please have the ability to constrain text to stay above the dimension line? Maybe @mary can bump this. See this thread from 2023: Flip Dimension text - #2 by mary

Hi Ryan -

I’m confused by your image. You have a dimension on the left side that reads from bottom to top. You have added a dimension to the right marked “want”. That dimension reads from top to bottom. Typically, you don’t want to have to rotate the drawing or your head when reading drawings, and the reading direction should be the same for all dimensions.

The “constrain text to stay above the dimension line” part of your question is on the list:
RH-53011 Dimension Text: Vertical control of dimension text.
That is not something that is on the table for Rhino 9.
-wim

@wim I just drew a square to illustrate that I can achieve what I need on the left but not on the right. I wouldn’t use both at the same time. Sometimes I need dims to be on the right side of the object and I never ever want the text to be under the dimension line. This feels like a no-brainer.

1 Like

I also would like a tickbox option to force the numerical value be opposite of the object that’s measured.


Two other important requests for V9:

  1. This one was requested numerous times for years (since Rhino 6 was the latest version), and my super huge hope is that it will be finally added to Rhino 9, because it’s annoying to write ti manually countless of times daily.

  1. Add a “Flip” button (like the one used in “Loft”) for the “Blend surface” tool. Currently, the lack of that particular option forces the user to cancel the command and redo the picking of all input surface edges all over again. Manually flipping the handle ends returns the following error message in the Command line:
"Shape ends are out of order
BlendSrf failed to make a surface."

Having that option should improve the workflow, because it will let the users window-select the input surface edges and then flip the direction if necessary. Window selection for “Blend surface” is very useful for tiny edges (including when using the “Chain edges” mode) as the user will not be forced to zoom-in the camera too close to be able to pick an edge that appears too small on the screen.

2 Likes