I’ve been with Rhino since mid-v4. I keep spending too much time trying to get v8 to just do basic operations. and, NO, I don’t want to post an example. At least half my time is spent trying to do a work around to make something work. There is something in the code that is causing random errors. FIX IT.
Now others can spend their time talking about how great it is—as for me—my time is spent working with this mess.
8 Likes
Hi Joe -
We don’t mind a post about how much Rhino sucks, but please note that there’s absolutely nothing in your post that we can act upon.
Perhaps you could start with the SystemInfo?
-wim
4 Likes
Wim i can relate to the guy Joe. I know it is not the most pleasant thing to hear such feedback but it is indeed reality. Instead of adding to the pile indefinitely we could hear from the company some plan for the future and what areas have priority to be fixed etc. Lately i have been following the forum and there are complaints all over the place and despite your best efforts to report (and fix ad hoc) and reproduce the issues the core problem resides somewhere else. Simply its unsustainable to have more bugs coming than being fixed.
@Grizzel Could you at least be a bit specific and outline in bullets what are the most pressing issues?
See Rhino 8 release - too early? - #41 by PowerShape
I would pick some good ones from the above thread.
“Most of the bugs were like:
You buy a car at the car dealer. Looks good. You buy it.
After the literal first curve the car tilt to one side! You dismount and find a wheel is missing!
You go back to the dealer and say:
“Hey one wheel is missing!”
and the dealer goes:
“Oh you wanted four of those? Thanks for the feedback, I’m opening a youtrack ticket for this.””
My point: fewer features but rock solid and fully developed features are better than new unreliable features piling up without fixing previous issues
7 Likes
We don’t mind a post about how much Rhino sucks, but please note that there’s absolutely nothing in your post that we can act upon.
We do mind how much Rhino sucks, as our livelihoods depend on it. And so far, R8 sucks a lot. It is exceptionally frustrating to work with, esp. on Mac, as it is much faster but much less stable with a quirky interface. I am bringing my Blender skill up quickly.
Even if we do post things to act upon (see below) the improvements are late, if at all, and software at this level of development should not have been released. I posted many R8 bugs, but what for? They were mostly not acted upon or acknowledged, and after a while it felt like working for McNeel for free. It is not our job to find bugs in your software. There is no ack of the users contribution, and many of my reports were ignored. See the long list of bugs in the posts here:
.
1 Like
For the record, I did get a response on that thread, but apparently that is not a bug, it was (badly) coded/designed that way.
1 Like
I stand corrected. But most of the items in the list were bugs that appeared with R8.
I also appreciate that rewriting the code base is no small task, but all the more reason to have been cautious with the release.
1 Like
Yep!
1 Like
I also have some problems. Can you help fix it? 
//Rolf
I too agree with OP. V8 is far too buggy and to be usable at work and frankly too unfinished to be pleasant to use at all. I’ve reverted to Rhino V7 for now.
You could act upon these (and I’m experiencing ALL of them even in the latest SR and I’ve arranged them in importance from top to bottom… the top two are definitely showstoppers for me):
I’ve already reported a few which were fixed which I didn’t include above, but is this the worst Rhino release yet in terms of software quality? It’s only my second upgrade, but to me it feels like the level of finish has taken quite a nosedive. That, and newly introduced tools having UX which feel very underdeveloped (though granted, that was basically the same in V7)…
1 Like