Is it a waste of time to report Rhino bugs?

Sometimes I experience not getting answers (not common though). I try to bump them every now and then but it doesn’t always work. Or maybe things get written down internally but I have no clue about it. I’ll take the opportunity to bring up a few topics I remembered without replies from anybody at McNeel:

Some of these might have been solved already, some might have never been noticed. Who knows?
There’s also things being brought up & get a reply but then just seem to get forgotten…

1 Like

Yep! I have several posts that did not even get the “someone from McNeel edited the post” Notification.

Replied to most of them.

1 Like

Kelvin filed this bug 6 years ago:
The bug has not been fixed yet.

I have reported these bugs 3 days ago: Rhino 6.9 - big problems with big monitors
No response from McNeel&Ass yet. I guess I have to wait 6 years before complaining about it.

Oh… I wish that was true some times…


In my experience it is not a waste of time. Sure - some stuff has lower priority and some stuff never gets fixed, but a lot of stuff does get fixed. When I encountered bugs with Autocad, I wrote to tech support and I never ever got an answer, people’s experiences differ. I dare to say McNeel is one of the CAD devs with the strongest ties to the community and user base. First thing I do when I encounter a bug I write directly to tech support, a lot of times it is my own stupidity and ignorance that causes what I think are “bugs” and probably waste Mcneel’s time. Just sharing my experience. I’ve been using Rhino before version 1, over 20 years of Rhino I can definitely say a lot of bugs have been fixed and I’m quite happy to have contributed to bug reporting. It made Rhino better.


So should one report bugs by writing to tech support instead of here on Discourse?

Same stuff, I guess, but I use tech when working on confidential things. It doesn’t go through the forum.

Either way is fine. We are pretty active on the forum, and most reports I think get handled in a way or other.

The good part of reporting here on the forum is when there are other users with the same problem. They might search for solutions and end up in the (your) thread with the report and likely YT link. That grows our shared knowledge.

Yeah I get that and appreciate that as well. But there’s also reports not being seen (or perhaps being ignored?) on discourse, as shown above. I don’t know if this is the case but if sending it to tech support makes sure it’s being seen and noted it might be worth sending it straight there instead?

1 Like

Yes, I checked just yesterday that I have a lot of threads with zero replies. I must have annoyed McNeel employees so much they have muted me :stuck_out_tongue_winking_eye:

I know @piac certainly has done so.

You are mistaken. We do not “mute” forum posters.

I would suggest that comments you make that are not responded to may be generally ignored for different reasons.

If you are offering suggestions for changes and have supported your ideas in a constructive way, other like-minded readers will likely comment, and gain support. We use these as an informal way to gauge the usefulness of suggestions. If no one else supports you, that tells us that it’s not a wide-spread issue.

If your comments are written in an angry tone and are not supported with examples and reasons for the problems they solve, then don’t be surprised if they are generally ignored.

Hell, then all new functionalities are going to be just for land architects and civil engineers, since most of the users (especially here on the forum) are such.

Angry tone, me? A misconception I would say. I use a lot of irony, sarcasm and jokes. Too bad I’m being understood wrong.

One of my questions (threads) is What are phantom objects?
Why would that be ignored? It is not explained in the api documentation, and yet it is used there.

I just checked I have over 30 threads with no reply, if I add them here I’ll flood the thread.


This particular one will never be supported by non naval architects simply because they don’t even know what block coefficient is:

Does that mean it should be ignored?

Naval architects were the target core industrial designers when Rhino was developed. That said, I have no idea what a “block coefficient” is. My background is civil engineering and land surveying.
Perhaps provide a visible example of what you’re after, and describe the problem is would solve for you work-flow.

As far as short, efficient forum messaging is concerned, you can not control the tone people “hear” when they read it. Sarcasm, subtlety, and irony will generally be heard negatively. That said, I’m sure you know that.

As to the specific scripting post you made, I don’t know. I don’t do any scripting so I have removed that category from my feed.
I assume you tried searching the forum archives for comments?

I know that, and I am surprised why this is missing from there.

This kind of proves my point.

Suggestions should be added to the list not ignored just because they are not understood.

And Block coefficient is an essential thing for ship design no additional info or sketches should be required to be understood (by the developers who have developed a command called ‘hydrostatics’)

This is also acceptable answer:

I’m the only person at McNeel with formal Naval Architecture training and worked as an NA for a number of years. Other people in the company rely on me to help better understand what formulas like block coefficient mean and why it may be important.

Sorry, but I probably dropped the ball on this and didn’t file a report. The issue is that I try to help as much as possible on support, but I also need to type on and improve Rhino. These things just get past us once in a while. I would still recommend discourse for the medium to make suggestions instead of direct emails.

1 Like