Again, why was this definition breaking change undocumented and we had to hammer devs on the forum to find out why our definitions suddenly freeze after 8.11?
1 Like
The automatic conversion GH can do for some data types remains very confusing for new users. This is another example of that. Plugging SubD into a component that expects a mesh and getting back the underlying control mesh is a teachable moment - the user will not do it again and will be vary of automatic conversion, it enables efficient workflows and is overall very consistent. The new way, with a randomly set subdivision value will cause freezes, crashes and confusion.
I think you should have kept the bug. Many tutorials have already been recorded and published using the old methods. Now, we’re in a position where we have to instruct everyone to switch from mesh to control polygon, which means rewriting numerous scripts. This is disappointing and adds a lot of unnecessary work.
Edit: The ‘Mesh from SubD’ component is literally doing the same thing. This change is unnecessary
At least there should be a way to keep the old component labeled as ‘OLD’ and let it behave the same as the old method, instead of completely changing it. This way, when people try to open their old scripts, it won’t break in Grasshopper
1 Like
Thanks everyone for the feedback on the issue. We agree with all of the points made here and are planning to bring this up in our next big meeting to discuss the options.
1 Like
Well this was an exciting morning finding my beautifully smooth SubD electric guitar body magically transformed into something more resembling an iceberg! (After more than 10 minutes of compute time compared to the usual 2 minutes.)
After reading this thread I was able to unravel back through my definition and find the one key place where I needed to insert a SubD Control Polygon component.
All better now 
1 Like
Hi, it’s been a while since this change was first introduced, since then I and my work colleagues stoped updating Rhino and kind of got stucked in SR 10. checking around on some recent release notes I find this for SR13 " Grasshopper: Components: “Mesh From SubD” now returns control polygon for D=0 (RH-65870)" does it mean that this particular change was reverted ? is it expected to work as it use to do on SR10 and older? will it be changed again in the future for some reason ? I just want to know how safe is to update regarding this change breaking a ton of existing critical definitions.
and I guess I’m refering in particular to the coment from Daniel Piker at the end saying “I confirm this component now returns the control polygon for D=0.
I think some users will still be unhappy about the change in the automatic conversion (directly connecting a subd to a mesh parameter, not using the MeshFromSubD component), but I guess that’s a separate issue.”
According to RH-65870 D 0 is what will be returned.