Currently, I’m working on Clayoo 2.6 as plug-in to the Rhino 6. If I upgrade to Rhino 7, will Clayoo work?
If you’re using Clayoo for SubD, Rhino 7 does SubD way better anyway.
T-SPLINES still better
Sub-D now better
subd is better than t-spline, but need more function, e.g. array symmetry, multi-symmetry
There are a few missing functions that I hope will be high on the agenda during early R8 WIP development. Array symmetry and multi-symmetry seem like they’re jobs better suited to grasshopper, but I guess there’s no reason for them not to be available in Rhino.
The features Clayoo has that Rhino SubD lacks that I think are the most important to add are:
- Knife (there are easy but slow workarounds for this in Rhino right now, though)
- WYSIWYG preview, with sliders for adjusting the number of segments across and along when executing many SubD creation commands
- I prefer Clayoo’s implementation of lofting and extruding degree 1 curves (Clayoo’s subdivisions across option splits each segment individually. This fits with “build in box mode” thinking)
With all of that said, Rhino SubD is still much, much better than Clayoo already for a number of reasons, the most dramatic being that Clayoo doesn’t play well with rhino osnaps, which is incredibly frustrating. I think it’s very unlikely, given how good native SubD is, that Clayoo will continue to exist for much longer. For sculpting, I expect zbrush - rhino workflows will continue to be much more popular, too.
Clayoo was a useful bridge for me, as I got back into using rhino professionally about a month after Autodesk nuked t-splines, but if I was TDM, I couldn’t see a rationale for continuing to develop it. I hope they at least offer legacy support for a while. I’ve found a workflow for converting Clayoo subD objects to Rhino SubD objects, but it’s somewhat tedious and seems to require a fair amount of manual repair on more complex objects.