I’m just learning cage editing in Rhino, and it seems crazy powerful (it’s called “lattice deform” in most other software, which is why I didn’t find it previously).
But I’m missing something when it comes to the workflow:
Create some surfaces
Create a curve
CageEdit
Select all surfaces
Select the curve
All is now well and you can move the curve control points and watch the surfaces deform in real-time.
Super neat.
But:
Do something else
Now CageEdit again
Select the same surfaces
Select the same curve
Now, instead of being able to deform the surfaces in real-time, they instantly get pulled to the curve.
Why is this?
How can I avoid this? I want the first behavior also the second time I run CageEdit on the objects.
ReleaseFromCage doesn’t matter and neither does HistoryPurge on the curve.
Hello - I believe there was a bug in reusing control objects - but I thought that had been fixed - hmm - I see what you describe. Exploding the cage-from-curve back to a curve, before the second use, will sort it out. As an aside - if you are caging surfaces, you may want to set PreserveStructure=Yes. Cage, stop and then cage again is not the same as one application of cage - if the structure is densified by cage editing and then the whole process started over, then the input is the dense object, the original simpler object is lost. One application of CageEdit always looks back at a hidden copy of the original input object to deform from that, it does not re-deform the output as a new input when you move a cage point, if you see what I mean.
Thank you for the information about hot Cage Edit works!
I only tried HistoryPurge and not Explode. It works as expected after doing that, but I’m glad it was a bug because if the issue you created could be fixed, the workflow would be streamlined!