Is there a reason the SubD From Mesh components toggles for crease options respond to the numbers 1 and 2 instead of 0 and 1? This breaks the convention that seems to hold across almost every other component with an input that’s looking for a binary choice. It’s easy to work around, but shouldn’t it be the same as everything else?
I have not yet found a situation in which I can join meshes, convert them to subD using SubD from Mesh and create something where the “Co” (corners) input does anything at all. Can someone explain to me how this would work or show an example?
Thanks for the suggestions. Yes, restoring some inputs for capping on the component can happen. I like the idea of the crease/smooth options.
I think a ‘Cap holes’ component for general SubDs, not just MultiPipes could be nice to have too.
Absolutely would be great to have a general cap holes component. One thing on my long to do list is to learn enough C# to just be able to script what you guys call “one liners” to call commands available in rhinocommon, and to start using it to make basic subD components that do rhino commands. Haven’t gotten there yet, so the best I could come up with is a thing that caps four-vertex holes.
Regarding writing one-liner scripts to call existing functions that don’t already have a component - it’s a very handy thing to learn. I think the largest obstacle at first is probably getting used to setting up the inputs, and finding the right function in the API. I tried to give a short description of the process here: