Hello Daniel @DanielPiker thanks for this very useful addition. I have now an application for it but I have a slight problem withe the component.
My cage is an hexagon extruded. My mesh that I need to morph and my cage have points on the plane.
Yes, Iāll post an updated version of this component shortly handling these cases where the points lie exactly on faces.
Also, as part this tool, I created another SpaceMorph which works on a polygonal prism, that could be useful here.
Iāll make another example showing that spacemorph on its own.
Thanks a lot! I did not notice this newer version of MeshCageMorph.
I will experiment with this updated component.
Extracting the control mesh of the SubD, morphing that mesh and reconstructing the mesh is not neccesary anymore to keep the creases I see.
MeshCageMorph has become an indispensable tool for my work as an orthopaedic shoemaker.
Is it possible to reference multiple geometry inputs for the same reference polygon within the Morph to Mesh class? Iām thinking it could be a nice tool for randomly setting various truchet (esq) geometries.
I guess this did answer my question. Iāll have to experiment with this stuff to see for my self.
Iāll have to post a challenge related to this.
Iām wondering if this could potentially be a type of solution to a problem Iāve seen inherently throughout every one of Rhinoās transformation tools.
I think it would be sweet if Rhino could transform objects without them behaving like a loaf of bread, but rather like a shell that grows.
If I could scale an object non-uniformly, in XY and not Z, and do it in a way where wall thickness doesnāt change, and wall angle doesnāt change. Then that would be great.
Maybe some sort of advanced cage edit tool could be a step in the right directionā¦
Iām trying to imagine if a cage edit tool could adapt and conform to a shelled geometry to enable the user to transform it while having control over thickness and angle ā¦
You want parametric functionality, and unfortunately Rhino is not an inherent parametric modeler and I donāt think it ever will be unless McNeel decides they want to sell to a different market and increase the cost, significantly no doubt.
Constraints may be coming, allowing for limited parametrics. Some people are doing some amazing parametric stuff in grasshopper. Thatās great if your application benefits from the time invested in grasshopper in a specialized workflow. That typically is not conducive to a parametric workflow that can be used on every project.