Yes. Definitely. Generally this gets said after the person just keeps haranguing on the same issues after they have been explained as best as they can be. At a certain point, in looking at the sum total of a particular person’s posts, the reader gets the impression that the person is not at all happy with Rhino. So then the offer gets reiterated. From me and other people. And I will continue to do so if the occasion arises. If you look at the number of times that that particular suggestion has been offered in relation to the number of posts it’s probably around 0.01%.
Yes, there are issues which are waiting to be fixed for a long time. On both platforms. There always will be. There are even some regressions from the previous versions. Stuff happens. The priority of what needs to be fixed/implemented first is always the stick point. Everyone wants their own particular issue fixed NOW!
So what does one do when people insist that this or that or the other thing is crap and that they have been waiting for it for X number of years and it still hasn’t been fixed - and it’s clear from a development standpoint that that particular problem is a can of worms to get into, that it cannot get fixed tomorrow without moving other stuff off-track? Apart from apologizing for the problem and trying to explain why it can’t be fixed tomorrow? And when that answer is not accepted?
I believe that I have said this before, but working with a software package is like being in a relationship. Sometimes you grow together and sometimes you grow apart. When the annoyances/disputes get to be too much to tolerate, or if you find another person better suited to your needs, it’s time to separate.
There are a certain number here, from a certain number of people. This is similar to the Windows side IMO. But I do not believe it is a majority in either case.
And the point is? Rhino V6 for Windows took six. And some people are still not happy with the release version - what can I say? That’s just the development speed - at least we have the WIPs/Betas to use during that time.
Just to clarify - yep, I am a Rhino reseller (but it is not my full-time job nor my primary source of income), and yes, I do try to offer some insights here from a reseller’s point of view and the fact that I know fairly well how the McNeel system works. Most of my posts/responses here are those of a long-time Rhino user and teacher. And yes, a Rhino/McNeel fan - have been since day one - and will continue to be. So yes, I will admit a certain bias towards the software and the people I really do love.