Bug: MatchSrf Fails to Maintain Isocurve Direction (CP Flow)

[Lagom]

Now it’s 12 years old. Will it get to college?

[Rhino_Bulgaria (Bobi)]

This one of the biggest flaws across all the existing surfacing tools of Rhino. No idea why the developers underestimate its importance for so many years…

[sach]

This needs to be addressed, desperately.

[Lagom]

In the year 2525, if man is still alive…

[sach]

Indeed’!

[sgreenawalt (Sky G)]

I’m well aware it’s 12, I gave it a proper 12 year old’s birthday party…

[David53 (David)]

In some time, a few of these YouTracks may get special 20th anniversary editions. Perhaps they will be signed?

[AlanMattano (Soaring Stars lab)]

@Gijs

’ve adjusted the title of this post (CP Flow) and added it to the mentioned YT

Worked On By: None

Not all “features” are improvements.

Rhino is like a parachute maker saying, “No one complained,” as proof of success. Maybe they couldn’t.

Fixing a bug is often like adding a new feature
Tools like MatchSrf need consistency and predictable behavior.

I miss Pascal. Viva Pascal Viva!!