Disgusting line end bleeding

I see this here as well - https://mcneel.myjetbrains.com/youtrack/issue/RH-49776

thanks,

-Pascal

It was a fluke indeed.
Some time after a file is open, some dialogs just go blank.

15 years of using Rhino gives me the impression that silly bugs being are being sqwished and coming back after some time in an endless cycle, but there is very little in terms of real innovation or even catching up with modern CAD technology.

All I get when I stress this out is “Well why don’t you just get a refund and stop nagging already ?”.
Typical response by entitled folks from an employee-owned company sleeping on its laurels.

Un-acceptable from a consumer’s perspective. Specially one who has allowed you to sell so many licences during these 15 years.

1 Like

Yes, well it is also the case that, like married couples, some customers and their software suppliers evolve in different directions over time. At a certain point one must decide if the relationship is worth preserving, despite how much has been invested in the past by both parties.

Also, like couples, one partner’s judgement of the capacities and progress of the other partner is not always objective.

1 Like

In other words “Well why don’t you just get a refund and stop nagging already ?”

No, not at all. Simply that an evaluation must be made, and if it is decided that the relationship is worth preserving, that there will be efforts and concessions (read things that “just have to be lived with”) that need to be made on both sides. Or if they simply can’t be lived with, a separation is probably the best option.

Unlike a couple in a one-to-one relationship, the relation of a software company to its customers is one-to-many, which complicates matters. It’s not always possible to satisfy all partners.

Because Grasshopper.

Here at least it seems to happen in the perspective view I posted, at certain camera angles. It happens on the vertical lines as well when I rotate the camera around the object.
But it also happens in orthogonal views (less noticable because the lines jump only a pixel instead of angled like in the perspective

  • GPU tesselation makes no difference
  • windows 10, RHino 6.11.18331.19171, Quadro M4000, 4K screen

Just checked this on the mac 6.12.18331.12056 and 6.12.18338.15016 beta and here happens the same (Macbook Pro 15" with Radeon Pro 450)

Thanks.
Pascal was able to reproduce the problem and added a bug report.

Looks like after all there has been some innovation that makes Rhino useful and relevant for you.


Bugs will always be there as the software evolves and properly reporting and helping to identify them is your best best to have them fixed. At times it is frustrating but continued heavy criticism of the entire software and the company each time you report may be unnecessary.

2 Likes

Jarek, Grasshopper was developped in the beginning in secret by David ; he wasn’t even hired for this.
It’s a blessing for McNeel, because it’s the only thing that makes Rhino relevant today for me and -I suspect-for a lot of people too.

As for the bugs… Man ! How long have you been on this boat ? They just keep patching it up and it starts leaking elsewhere, and repatch the same old stuff over and over again.
Damn, this is so frustrating, and all the while, requests of old remain ignored.

Quite the opposite is true. It is about time users shook the coco tree, specially after 7 years of waiting for a lame Rhino 6.
It is because I want Rhino to survive that I say things as they are, hoping that McNeel will wake up.

1 Like

True, but you have to give everyone there credit for recognizing its potential, supporting and developing it to this point and beyond… But I agree, GH must have been and still is a huge popularity and relevance booster.

17 years.

I have mixed luck with some of the bugs and requests, but in general many of them, I have been finding and reporting, are being fixed over time. I know it is tedious and frustrating to spend time to document the bugs, provide the examples and step-by-step instructions, but in many cases I realty think the devs. can’t reproduce or understand the problem. So I found the time invested in communicating problems well spend for the problems and additional features to be done.

As long as we stay productive - I’m with you on this one!

–jarek

2 Likes

RH-49776 is fixed in the latest Service Release Candidate

Yay !

See you on the next one.

Good point Mitch, but it’s even more complicated than than. Software are people too. I see my (one of the many) relationship to Rhino also a a one-to-many since there are so many people doing work at McNeel.

Then I also date other softwares too so there’s a bit of a messy many-to-many and so-many-more thing going on.

A proper digital soap opera

1 Like

This isn’t true. Grasshopper development was carried out from the beginning at our office in Finland, and was never “secret”. Sure - the very earliest part of the research was done without everyone being involved, but that is normal for research projects. But I certainly knew about it from day one.

“Explicit History” was shown to Bob within a month or so of the first line of code being written, and after that it was all systems go at McNeel to get it finished.

I hired David with the idea of figuring out how to deliver computational geometry to architects. It worked out pretty well I think.

I have been in a “relationship” with Rhino since the release of Rhino 3, and have spent a lot of my time reporting and documenting bugs, posting wishes, etc…
Heck ! I was even 2nd most prolific poster after Mitch at some point, widely regarded as the insulting French man of the forum bunch (I really tried to change, but I have to accept I am just a despicable human being).

Before David was hired by McNeel, I got him recruited as an intern in the engineering office where I worked, so I know at least one McNeelian personally.
Yet, for exchanging so much with many of the Rhino people, I forged myself a mental picture of the various personalities, and feel like I actually know them.
I must say that I appreciate all of those people, and admire them for their kindness and professionalism, specially in the face of a rude louse like me.

BUT … there has to be something wrong going on at McNeel.
Rhino had a fantastic head start by bringing Nurbs technology into a familiar user interface, and could have effectively replaced the CAD for which it was a mere plugin because it brought in so much more.
In fact, it remained content to be the eternal underdog, with no apparent will to innovate or even integrate industry-standard features.
Is it a consequence of the conservative “no licensing of exterior code” policy ?
Is it by not hiring and trusting more young prodigies like David ?
Poor leadership ?
I don’t know, but the result is an ever-growing frustration and exasperation when contemplating the endless merry-go-round of petty bug-fixing and deafness to (very) long time enhancement requests.

There, I said it.

I don’t think there’s anything wrong at McNeel, but I’m willing to discuss it with you in person if you’d like.

Do you live in Toulouse, or have you moved since then?

Andy

Nothing could make me more happy.

I’m in Albi now.

CAD therapy…:wink: