Rhino: developing too slowly


#1

McNeel, if you want to survive in the jungle of the CAD software should do faster. The timing is an important factor in the selection and purchase of software. Five years of development would be justified if the CAD would provide innovative and advanced modeling tools.
The development is too slow: subD at an early stage (many competitors software for several years have this feature); modeling tools, the usual, always the same (apart from minor improvements here and there and the welcome news of the shelling). Too focused on marginal factors and soon turned to modeling and editing of surfaces, such as: rendering, grasshopper, various views not needed, and so on.

Also MOI runs faster, whereas software is a younger and less mature, will not have the same number of Rhino tools, but is able to model all with simplicity and discreet power, as Rhino… and coast 1/5 about!

Each new version: the same bug to be fixed, the same problems, minor adjustments and additions, but nothing revolutionary.
From a point of view of marketing: why you should buy the new version of Rhino? What possesses innovative than 5 Rhino? A few more options could justify its purchase?
I ask all of you without any controversy…


#2

McNeel made almost no progress in the field of geometric modeling kernels because they are small, employee owned company. They simply do not have the resources to work faster. If Autodesk purchases McNeel, they will have plenty of resources, but they prefer to remain employee owned company. (In my opinion T-splines are better than subdivision surfaces.)


#3

At the end count the numbers, the results. The work done by the developers is admirable, but with each release will highlight the usual bug, the usual problems, there are no fixed points, it all seems precarious, unstable, indefinite (it is my impression).
Forget the big, such as Autodesk, Dassault, Siemens …, you can not make any comparison!


#4

If Autodesk were to purchase McNeel, Rhino would be dead for all intents and purposes. Therefore, your “plenty of resources” argument doesn’t hold any water, as there won’t be any Rhino (as we know it) to put resources into…


#5

Hello,

In my opinion Rhino reminds me of a messy tool bag, there are useful tools in there, you just need to spend time searching for them. I don’t see anything in V6 that would have me give up the V5 plugins I use (e.g. VSR). MoI3D is a different animal with an optimized workflow when compared to Rhino, however I don’t think it is encumbered by the same baggage as Rhino.

An Autodesk acquisition does have a downside, cloud may seem OK until you understand that their liability for your information being lost or stolen is $100. I see that your information is encrypted in transit, but once it resides on the server there is no mention that I can find of it being secured at that point. That in itself is reason for not using any cloud solution, someone hacks them and encrypts that data they hold customers IP for ransom.


(David Cockey) #6

Previous thread on a similar topic for those who wish to jump ahead: Robert McNeel & Associates are in decline


#7

In my opinion the only messy part of Rhino is its help file - it has lots of errors and omissions.


(Wim Dekeyser) #8

and of course you are reporting all these cases?


#9

If Autodesk bought out McNeel this would become a Fusion 360 forum. Rhino would be scavenged for it’s strong points and killed off. Isn’t that the very definition of “Fusion”? They named that product very appropriately.


#10

Yeah, radioactivity included… :radioactive:


#11

I was surprised at the Autodesk booth at IMTS back in September. It was all about CAM. They’re really making a shift in their marketing strategy since they swallowed up Delcam.


#12

I think Autodesk is like a car manufacturer who is trying to become the only one selling stuff on wheels.


#13

AutoDesk is at the Dark side of the force and a major part of the Axis of Evil :wink:


#14

I don’t mind at all that Rhino is developed slowly. Yes, there are features I’d like to see added as soon as possible, sub-d now that T-Splines is no more, and improvements to the core surfacing tools. However, I can still do what I need to with Rhino as is. It may not be the quickest or easiest but it gets the job done.

Of course I’d like to see improvements but if you consider the affordable cost (without annual paid updates), stability, and excellent support, then Rhino’s slow development doesn’t seem such a bad thing.


#15

For about one year I was posting Rhino help file bugs and omissions. Margaret Becker was tired of it and said that she had no time to fix all the bugs. When the first version of Bongo 2.0 help file was released, I sent her (via Marika Almgren) ten-page long report about bugs and omissions in the help file. This was the basis of major re-write of the help file. I was driven out of Flamingo forum because I reported all its bugs.


#16

Yeah… you’ll be nobody’s friend if you keep on pointing out their flaws and weaknesses… :smiley:
I stopped using Penguin, Bongo and Flamingo all together due to this, it was no return of investment in it. But Rhino is a software I could not live without, and V5 is probably the most stable software I have ever beaten the heck out of. It is a workhorse. Reliable, predicable and rock solid.


#17

In my opinion, in addition to the slow pace of development, Rhino has lost sight of its main function: "free form surface modeler."
Add a few small options to existing commands (always the same) it has little significance. The command patch, for example, is always the same, lacking! The fillet is always the same. The UDT are equal to those of Rhino 4. The editing of surfaces? always lacking and limited, but small improvements!
The only true revolutionary command was the “shelling”. All other things have been revised and adjusted.
If you are unable to work optimally with Rhino 5 why upgrade to Rhino 6?
Solve some fillet and have a good rendering engine or grasshopper does not justify a possible upgrade. Too little! In addition, you can no longer use nor VSR nor T-Splines.

I think Rhino is having some difficulty. Development strategies should be reviewed in the logic of the above.
Enough with rendering and various views: Rhino is not V-Ray!
Enough with Grasshopper: who will use it? some architect …? We would like to see the modeling tools and editing state of the art! (little provocation).


#18

You need to realize that part of why Rhino is so successful now is that it is so much more than a surface modeler now and ‘some architects’ are a big part of the user base. McNeel development is responding to many users’ needs and they are being very smart about it.

As @MisterB and @Holo said, I too prefer way more a solid stable tool with slower and more thorough development than a set of shiny new features every year that are not well tested, buggy and poorly implemented.
I like the small improvements - on a daily basis these small tweaks and McNeel ability to listen and implement them makes Rhino very reliable to work with. Of course I too always wish for more and we will see it coming, but this development pace as a trade-off for solid, stable product is something I am more than happy to live with.

–jarek


#19

We are a minority. I have not seen any software review that mentions bugs. When I wrote software review myself, it was accepted for publication, but rejected in the last moment because I sent private letter to one of the software vendors and criticized its bugs. The same software vendor was posting advertisements in the same computer magazine. (money talks)


(Lukasz Domagala) #20

Rhino gets better and better with each version. GH + RH is a beast of a tool and I have no words to express how much I am grateful for this. With that combo I’m in heaven…My bread and butter work was taking me about 3h…now it’s 5 seconds. Have so much more time for research and getting to know Rhino on the much deeper lever than I used to. For the last 6 months or so I solely use R6 WIP with an exception of rendering which still needs to be done in R5…Why? R6 already opened up many methods previously unavailable and I simply couldn’t go back to R5 because of these "minor adjustments and additions"
Fusion etc might be cool and funky…but where the real work needs to be done…Rhino all the way.