In Rhino8 extendsrf does not create a bad object but shrinks the surface. That is just plain wrong and very arrogant of the developers to impose a that on the user. If the user wants their surface shrunk they can do it themselves or if any command does shrink a surface, it should be only as an option.
on my ExtendSrf button. The reason I have been using extendsrf_old for years is that it does not shrink the surface.
I don’t understand how a legacy function that is intended to preserve old behavior can get broken but extendsrf_old now makes bad objects.
Anyway there is now no workaround in Rhino9 to avoid having surfaces shrunk other than the old school method of untrimming the surface, extending and then retrimming.
@jim Perhaps you should change the title to “Rhino WIP ExtendSrfA_Old Bug” and update your first post so the problem will be obvious to someone from McNeel.
For reference, automatic shrinking with ExtendSrf started in V6.
Thanks, I was not aware of that one - I will try it and see.
I would have thought ExtendSrf_old was the V5 legacy code since I have been using extendsrf_old in V6 for years ever since the undesirable changes to extendsrf starting in V6.
I’ve done some investigation up to sept 2024, but even then ExtendSrf_old behavior is different in Rhino 7, so whatever broke that command for this case has been broken for long.
Just to be clear. Rhino has not been shrinking extended surfaces since 2007. My copy of Rhino5 released in 2017 does not shrink the underlying surface. I’m pretty sure it was working for a while in Rhino6 after that. The number of times extendsrf has been broken then fixed then broken again in the last 20 years is more than anybody can count.
Rhino 6 for Windows was released in February 2016. Rhino 6 for Mac was released in July 2017.
My current version of Rhino 6 for Windows shrinks the underlying surface. My version of Rhino 5 does not shrink the underlying surface. As I previously posted it appears that shrinking the underlying surface began in Rhino 6.