Brian, I completely understand the non-sense of the flaw logic behind this. At the risk of being call dramatic this makes working in SubD + Meshes + Curves + Nurbs a completely broken promise.
I’m telling you and your team that this is absolutely silly and extremely counter-productive, and I’m not OK with a response of: “I lobbied for this but the people who do not work designing and modeling for a living don’t think it’s a good idea”. So I’m going to continue to bitch about this one until someone can have some common sense here.
Let me just clarify that for the time being I don’t even expect SubD in Rhino to be good for design and modeling, I know that will take a lot of work. And I’m fine being patient with that.
For now I just want to Rhino to be useful to at least to do some basic edits and visualization of models created in a professional SubD tool. Right now between this silly “this mesh is not a mesh” stuff, not being able to smooth only what I want (do you know what happens when you press tab to an entire production car model?!), having a gumball re-setting itself after each move, not being able to copy-paste, _AlignVertices not working in SubD, …etc, etc, etc, it’s really hard to work efficiently.
Please help your team realize that they are getting in our way, constantly, with the impact that their vacuum-formed decisions have in our work.