@theoutside I tried, but the command fails because, given that its topology is different, it doesn’t work, or I’m making a mistake in some step in the middle of the process.
Anyway, I solved it; soft-transform was still useful in this case.
This is the finished file. sottotacco-soft-transform.3dm (868.0 KB)
the topology has to be identical in a radial manner. (think something like a torus) Currently if the topology cannot be divided in a radially symmetrical manner the command fails without feedback. We are hoping to add a little smarts to this and some feedback. @pierrec has graciously offered to look into how this can be improved going forward.
Thanks, it would be really useful to implement and have the radial symmetry function (like in the video I showed you on ZBrush), even when the mesh or SubD topology isn’t symmetrical. Unfortunately, I often get client files where I can’t touch certain meshes or surfaces, especially if the file has already been approved. In this case, I couldn’t make the mesh symmetrical because the heel base was merging with the upper part of the heel — so I was literally stuck with the edges. The only thing I could do was remove the undercuts. I’m attaching an image of the top part of the object so you can immediately see I was tied hand and foot… otherwise, of course, the first thing I would’ve done was apply symmetry.
@brvdln Thanks for all the pictures and examples, really helpful to understand what’s blocking you in Radiate symmetries in Rhino.
I think what you are suggesting here, to implement something like the Zbrush radial symmetry function, would translate to Rhino world by making the commands themselves be applied symmetrically. That’s not the approach that SubD symmetries are taking, where the object itself is always exactly symmetrical, because it is built from one parent motif that is repeated through the symmetry operation into as many children motifs as needed.
We don’t have a way to repeat a command “symmetrically” in Rhino but I’ll write something in our bugtrack system about using ZBrush’s approach and see if someone is interested in writing that.
Still, RadiateFind is lacking a lot in its feedback and I can improve on that. Kyle wrote a feature item on that: RH-90305 radiate - find
