Rhino 8 Development

I fully agree with you, the reason I said mcNeel won’t copy 1:1 is because that’s what they never do (in many cases I’d say unfortunately).

1 Like

a couple of things to start with:

  • Instead of having to enter a ‘radius’ (which after you have entered it, you no longer can see) I would like to see how much influence is active on the object I am transforming, preferably with some sort of visual overlay.
  • The way it is implemented now is not working well because I have to run SoftTransform, change radius, make sure I Enable it (a lot of handling) And then when it is enabled I have to remember it’s on, but there is nowhere where you can see this. Next I make the transform, notice that the radius is not what I want, I have to cancel/undo the transform, go back to the SoftTransform command, click radius, change radius, enter, redo the transform, notice it is still slightly off… etc…
  • Falloff in radius is nice as an option, but we should also be able to influence a certain number of controlpoints from the moved control point(s).
  • Type of falloff (linear, radial, image based)
  • Falloff ease in/out

Furthermor right now the SoftTransform is so tedious that I end up not using the command at all.


this seems appropriate for a program famous for grasshopper to have that:P

If you select a sub-object (Ctrl+Shift+Click) before running the SoftTransform command, the SoftTransform will display a sphere of influence. The sphere of influence is shown in the following screenshot. You can change its radius with a mouse, or by typing a number in the command prompt.

I hope that the sphere of influence will evolve into clickable widget (like gumball), and that its shape will provide a clue about current shape option.

Yes. This is real problem, but it has elegant solution. Instead of adding clutter to the Rhino interface (e.g. status bar), the sphere of influence (show above) can be the clue that the SoftTransform command has been enabled. The SoftTransform command has no effect on Rhino objects - its sole purpose is editing/changing Rhino sub-objects. If the SoftTransform command has been enabled when you select the sub-object, the sphere of influence should be automatically displayed to give you the clue that the SoftTransform command has been enabled. If the SoftTransform command has not been enabled, the sphere of influence should not be displayed.

The SoftTransform command has four kinds of falloff: smooth, linear, round, and sharp. The falloff is changed with shape option. I have no clue how these falloffs work because the SoftTransform command still does not have any documentation.

By the way, bad documentation is not just Rhino problem - nobody cares about documentation. :face_with_symbols_over_mouth: :face_with_symbols_over_mouth: :face_with_symbols_over_mouth: During the Second World War German army was the best army in the world because it was the only army that had good documentation. For example, German tank manuals were illustrated with good drawings. Other countries had horrible tank manuals.

1 Like

+1. I don’t make this mistake any more but did to begin with. No idea why a message box isn’t used like with OneView. Or for it to just be in the bottom. It seems like it very logically belongs there, and from there you would pull out the options to edit. Maybe it needs to ‘earn’ that kind of privileged screen space though.


I couldn’t disagree more as I’ve found it useful no end, but, horses for courses and good to hear a different view. Just wish it could work with Nurbs objects (SoftMove / SoftEditSrf I find are hard to use by comparison).

I’m glad you asked:


Hi All,
I would like to start saying thanks to Rhino and its developers for being what it is: a powerful software backed by a strong and active community. No way to go for yearly updates / subscription fees like the others do.

I work in the marine industry, where Rhino is a sort of “unofficial” standard. Many offices/shipyards have Catia/Solidworks/Nx but, at the end, use Rhino a lot for their quick and dirty modeling stuff.

As you move from 3D to 2D the magic of Rhino stops: Section or Make2D views are generated and copied to “Old Way” layouts in Autocad/AutoClone/…
This is bad because there is no dynamic update, meaning a lot of manual/boring and potentially source of error job need to be done.

If Rhino would have more robust Drafting capabilities and a Good Vector Output it could be the choice to manage the full cycle, from 3D modeling to production drawings.
Avoiding import/export geometry to other software would be a huge benefit.
There is already a thread about this, as mentioned by @ryan.odom : Layout & Drafting: What’s the plan?

Apart from the point above, here a quick list of what I think is missing in Rhino, in no particular order.
I will cover individual points with better description/examples:

3D Modeling

  • Chamfer by ratio / angle

  • Silhouette for garbled surfaces

  • Clipping Plane attached to CPlane (similar to Spaceclaim)

Assembly / Big project management

  • Blocks!!

  • Multi File opening inside same session??

Plugin / Tools Collections integration

Layout, Drafting and Annotations

  • Level managed by layout only, not global display in model (-> Safe Layout plugin)

  • Good Vector Output!

  • 2D Views / Sections Synced (or cached) to 3D model

  • Automatic generation of projected views / sections / details / etc.

  • Advanced clipping

  • SectionTools integration and improvement

  • Structure Grid <-> Sections / Views

  • Make 2D improvement - Dynamic Update

  • Layout tools

  • Excel Support

  • Layout detail of any shape

  • Print Preview as default or more easily On/Off

  • Easier management / screen preview of Line Weights/Styles. Scaled to actual view (no need to zoom in)

File versioning, support / integration with other Software

  • PDM?

  • GrabCad integration / Plugin

  • Step 242 Import / Export.

  • Direct Copy/Paste with SpaceClaim (actually works copying from Rhino 5 to Spaceclaim)

  • Dropbox (recurrent tmp file error when working with large files)

GUI - Operation - Miscellaneus

  • Popup Menu improvement -> New Radial Menu??

  • Sync of Preferences/Shortcuts/Plugins between multiple PC’s (i.e Workstation + Laptop / Home + Office, etc…) useful also for backup / migration to new computer.

  • Package file, to export custom display modes and other settings/plugin to an archive for sharing design file

  • Smart (Solid Modeler Style) Structure Tree of Parts/Assemblies/Blocks and Elements (->SpaceClaim)

  • Highlight Layer/Part on structure Tree when I hover over an object

  • Highlight element when I hover over its layer


It was introduced in Rhino 6 as solid white hatch.

Yes, you are right! I’ ve seen this already in some post but it’s actually in Rhino help here.
I consider it anyway more like a workaround than a real command.
Not so straightforward if there are many details in your layout.
Thanks anyway for the hint!

It is a workaround and is not a true implementation of non-rectangular details.

I wonder can the Rhino 8 be just Rhino 7 with NO NEW features, but almost bug free with refined and optimized commands? This grow and expand mantra is getting contra productive in many ways.


That would be a hard sell from marketing stanpoint but I would happily pay double the upgrade price for that.


You may be tired of this kind of comment but I would be happy with V5 (and plugins) + how V7 uses GPU.
If I have to be specific

  • Most VSR Features

  • Create Symmetry / Align to symmetry plane ( I use it all the time) we have reflect and symmetry now that are related to these features, but they don’t solve the same problem completely.

  • Trim convert/ VSR Split Surface (Killer tool)

  • Control point modeling ( changes degree quickly, extrapolate, smooth, move row, points, fallof and retopo snap, among others). We have some of this features but all scattered in different places that make the workflow terribly slower.
    Some in Move UVN, some in the gumball, extend, others choosing the drag mode…

  • Rebuild curves and surfaces with curvature, arc lengths or original distribution.

  • Global Matching Analysis ( we have now something in V7, but it’s not mature enough)

There are some other tools to mention, I could make a quick video if needed.

I would remove some tools from rhino that had no development for decades and give a low quality result like surface from network, and patch and integrate XNurbs.
I promised myself to stop buying plugins that replace important tools, and may cause problems in the future.

  • SubD, Naturally I would love a toolset that matches the level of T-Splines tools with some features from Modo. Like: Merge points by tolerance, match subd to nurbs, retopo modeling, Increase/decrees selection.

  • package GH definitions A little dream would be, a way to make grasshopper magic more accessible to people that don’t want to learn it. I use to work with scripts created by experts from this community and although GH is an enormous step forward as language to code with a visual interface, this is not what I want to focus on at the moment. But I think that there might be a way to integrate definitions with just the elements to be selected and for example some sliders.

  • Resume Mesh2 mesher that would benefit my next wish.

  • Better tools for unwrapping and editing the UVeditor.

  • Copy paste from V7 to V5

  • Some Direct polysurface editing (like synchronous technology, fusion, creo, spaceclaim…) What we have works for simple architecture, but it brakes with just a single hole in a cylinder wall.


Excellent points by @laborda here. I agree with all of it, the most puzzling of all for me is the solid editing of simple prismatic stuff.

SolidEditing is a part of Rhino continues to be completely broken. Even for the simplest of things like planar surfaces and extrusion-type surfaces. Even VC barely-funded and silly iPad modeling-playground apps have solved this.

1.I just tested this problem:

still here:

  1. this one reported by me in 2016:

…still broken:

The worse part of this? Rhino doesn’t even have a designed and programmed feedback mechanism routine that at least says: “Sorry I just turned some of your degree-1 and degree-2 surfaces into higher degree and much higher density surfaces. Also your planar surfaces are not longer planar”



Dear McNeel developers, thank you for creating that great piece of software that Rhino is!
My wish: may it prosper and grow and become capable of doing more and more of the work the other apps in our architectural office are still used for (AutoCAD for oldschool 2D plan-drawing - ugh!, Revit when new projects enter the actual construction phase, Adobe stuff for layouting/graphics (I’d prefer Affinity)).
Rhino sits somewhat in the middle and is used for design studies, competitions, rendering, and juggling CAD data of all sorts. Together with VisualArq it can do a little / a lot of pretty much everything - but that overlap could become bigger. It’s not perfect, but still it’s a joy to work with it (much more than with what Autode$k feeds us).
However, here’s my greedy wishlist for R8/9/10… (bigger things first):

  • User Interface (meaning everything outside the viewports - toolbars, panels):
    Rework it over time using the same GUI library as Grasshopper (Windows forms, right?). No more glitches with re-arranged/jittery toolbars.
    All UI colors customizable (dark theme)
    Save/load UI layouts (Cinema4D does this right)
    Context-sensitive keyboard shortcuts (example: CTRL-A over a viewport: select all objects, CTRL-A over the layer panel: select all Layers)

  • Layouts (much has been suggested):
    Correct z-sorting / draw order support for everything that can be placed on a layout, including overlapping Details, hatches, surfaces, annotations… stuff inside Details…
    Make2D placeable on a layout, as an updateable, dynamic block, supporting hatches

  • Parametric modelling:
    Better history - one that does not break so easily, is editable in some GH-like graphic panel, and where the commands’ parameters still can be accessed (E.g. why is there a control point-like handle on an Extrusion, but no way to set it numerically later on, and why does the history have to break moving it?)

  • Blocks (yay!):
    Get rid of those nasty recursive deletion problems!
    Support for lights
    Dockable, non-modal BlockManager
    Dynamic Blocks, powered by Grasshopper (see VisualArq Elements)
    BlockEdit: Set Base Point plus orientation
    Add a command to create a new, unique block from an existing one without exploding/reblocking.

  • BoxEdit:
    Immediate and correct update when something is selected
    Support for components - When something shows a Gumball, BoxEdit should support editing it!

  • Grasshopper:
    Update for the GH panel in the main UI - or maybe ditch it and replace it with dynamic GH blocks that have their parameters exposed in the Properties panel.

  • Layer panel:
    Solo layer icon or keyshort (maybe ALT-LMB). Multiple layers can be solo-ed, and their original state is remembered.
    Better drag&drop support, just like in the R7 Named Views and Layer States panels - up/down arrows should become obsolete.

  • Viewport safe frame:
    Always the full size of the safe frame (showing the render resolution aspect ratio) should be visible in a VP - those left/right arrows that are shown when the frame is cut off don’t make any sense!
    We work with Enscape3D a lot - it’s a brilliant renderer, but the way it is synced with the Rhino viewport is really stupid. This could improve if Rhino had better support for that safe frame.

  • Gumball
    Numeric 2D-scale
    Could Groups remember their Gumball location?

  • R7 Color panel update
    Color wheel AND sliders shown together

Thank you!!


It would be very useful, if Rhino could get an Object Manager (Outliner) like it was developed as an experimental plugin for Rhino4 some years ago.

I often work with large Rhino files with thousands of objects on many layers. It’s very hard to look for an object that is hidden, when you don’t know on which layer (some are turned “off”, some are turned “on”) it is placed. Seeing which objects are members of a group or block is another missing feature that an object manager could enable.
This object manager could also be very handy to organize the file structure by dragging and dropping parts or groups from one layer to another.


That is the most important feature that needs added for me.

Here I must concur. I would gladly pay double the price if the software was fast, responsible, bug-free and optimized. Ultimately, the time spent on hardly responsive files, layouts, bugs and finding workaround is most likely costing even more… But I will try to remain an optimist.


My list:

  • The ability to mirror detail views in paperspace to easily create things like reflected ceiling plans
  • Asset library
  • Automatic leader lines for dimensions that are too small to have the numbers sit on the dimension line
  • Ability to output any display mode as a vector or hybrid of vector and raster.

I’ve switched from using Sketchup to Rhino fulltime and these have been the things I’ve been missing the most.


+1 to that. Total nightmare at the moment still I find.