Wishes for Rhino WIP

Maybe it’s just me, but I don’t see a huge leap forward in V6. If what we have today is close to the finished product, I don’t know how I would justify updating 60+ seats across all of our facilities. We don’t use Grasshopper so that’s not a factor. And the new Sub-D modeling won’t be something we need. I have T-splines and never use it.

So for me, I’m hoping V6 is still way out there, and the WOW!! factor is still coming.

Just being honest.


1 Like

And the new Sub-D modeling won’t be something we need

How’s that looking by the way? Good enough to replace T-Splines?

I guess I agree :stuck_out_tongue: - waiting for more WOW…

Then again, I do use Grasshopper all the time and I haven’t been able to get the company to add that to the list of approved software - so I’m looking forward to having that embedded.

Also looking forward to Cycles. I have Maxwell, Brazil, … on my personal PC with my personal Rhino license but to have capabilities inside Rhino on a work PC will be good.

Objectively, I suppose Rhino 6 will be a big step ahead with a rewrite of the display engine and rewrites to accommodate Rhino for Mac.

As for Sub-D, I understand that won’t be in RH6.

I would love to see a “healer” that would fix those tiny annoyances that keep a polysurface from being closed. I find we often have to use other products to do this. This alone would be the WOW factor I’m hoping for. This is important to us because we also do additive manufacturing where closed polysurfaces are required. We currently require Solidworks to “heal” our Rhino models via the IGES translator.

I would love to see some of the class-a tools that the old VSR plug-in had (Autodesk shape modeling now).

I have no doubt the changes behind the scenes are extensive. And I understand that not everyone uses Rhino for the same reasons, so there will always be someone not satisfied with the direction it’s going.

So, personally, I’m hoping the release of V6 is still way out there. If it was tomorrow, I couldn’t justify the cost of updating the entire company. I would update one license so that I can participate in the next WIP cycle and hope for the best next time.

Maybe we just drew the short straw for this version. It was bound to happen eventually! :slightly_smiling:


This should be of some interest…

Performance on large models is definitely something of interest to us. I’ll have to check out the March 1 release to see how it looks. Maybe at the end of the day, it will be performance gains and not new features that will justify the update.

Thanks for the link,


@DanBayn, @John_Brock - Please keep discussions about Rhino WIP inside Serengeti. I appreciate everyone helping get people from Rhino for Windows into Serengeti, but please keep the content here.

oops, sorry.

Yes, I think that this would be the biggest WOW-factor for me…



Have you ever tried “testRemoveNakedMicroLoops”? It works for some types of tiny annoyances.

That’s now called RemoveNakedMicroEdges, I think, and is no longer a test command.

My main concern is the plugins that are being left behind, rather than the new stuff being added to V6. That aspect will make the decision very difficult for me when it comes to making the jump to V6, as things currently stand. It’s also why I’m not using Serengeti releases for my day to day work.

1 Like

Ah right, I recall the discussion to move it from a test command now. Looks like it called “RemoveAllNakedMicroEdges”

Are these plugins only 32 bit? Or is there another issue?

It’s things like RhinoWorks (now defunct), T-splines, VSR Shape (that are now owned by competitors) & Scan & Solve that are useful to me in V5, that either definitely won’t be available (RhinoWorks) for V6 or are very unlikely to be (VSR & T-splines). To the best of my knowledge there’s been no clear statement of intent coming from the respective developers.

We’ve already been told that plugins compiled for V5 won’t be able to run on V6.

1 Like

Yes, I always give that a try, and I have seen it work in quite a few cases, but not all.

I will have to remember to remove the “test” from the beginning as I move forward.



Please send along files with cases that don’t work.

Will do. I’ll try to come up with something tomorrow.



Hi Brian,

Here is one.

And the file:

micro edges.3dm (3.1 MB)

The RemoveAllNakedMicroEdges command did find and repair quite a few, but missed these 2.

Also, I used JoinEdge on a number of edges of this model. In V5 the JoinEdge command comes with a lot of disclaimers in the help file. Has there been any upgrades in V6? It seemed to do a pretty good job, but I don’t often use this command as a method of creating a “water tight” model.

Hope this is helpful.


I think, for myself, a way to ask what I would want in V6 is to ask - what do I have to go outside Rhino for?

First, layouts are better in V5 but still quite a bit screwy when compared to AutoCAD. So I do most of my technical output in AutoCAD. I’d like to see Rhino get in control of that whole area - decouple text / leader / dimension annotation, etc. Simplify it, make it more logical, make it more stable.

Second, Rhino has accepted the doubtful premise that rendering output should prioritize the Keyshot / V-Ray / Maxwell photo real model. So we have Neon and Flamingo and Rhino Renderer and Brazil, and so on (all of which do more or less the same thing). But the fact is, 90% of my renderings take place during the development phase of projects. My clients don’t expect and don’t want to pay for high quality photo real renderings during the conceptual stage. But they do expect textures, surfaces, etc. So that means exporting to SketchUp. SU can export clean, textured images with no struggling with lights, GI calculations, backgrounds, etc. Rhino can’t.

My two cents at this time.

1 Like