UDT - especially FlowAlongSrf and CageEdit are quiet powerful - and a strong Rhino-Feature - and in combination with SubD they allow fantastic workflows.
It s time for more love to this functionality:
ExtractPt should work without turning _pointsOn
ExtractControlpolygon should work
ExtractIsoSurface (UV, VW, WU) … new command ?
ChangeDegree (U,V,W) should work for controls
InsertKnot should work for controls
ResetControl would be nice - return the control object / cage to the start possition
Edit CageEdit Parameters - allow to switch from Accurate to Fast back and forth, set “Loose” option later - would be nice to have those as properties in the property panel
Allow objects to be added to a deformed control - create a cage, deform it in empty state, add captive object to deformed cage
Expose Functionality to RhinoCommon and Grasshopper
Create Cage - the input for Degree / CV-Count is a bit clunky
tolerance setting for edges (default = document tolerance) and (inner) surfaces (10x document tolerance should be visually enough for most cases)
… more to come…
Background: i currently work for a medtec project and come across all those limitations …
We are working on some tech to allow for more flexibility with CageEdit shapes. It is not really ready for primetime, but I would love any models we can use to test it. Do you have examples what the cages should look like?
@scottd, can you shed any light on the tech you are referring to, and will it be available for Rhino 9? The thread you posted is interesting with simplified cages being used to deform shoe lasts. Something like this more polished and native to Rhino would be fantastic.
I was thinking of just using an approximate shoe last shaped SubD as the control object, but then realized SubD can’t be used as the control. Any chance that could come in Rhino 9?
Any chance this will be available directly in Rhino for V9 (rather than only via grasshopper)? And maybe part of Rhinocommon? Or maybe the underlying code is open?
I think this might be the RHinocommon call in Rhino 9:
It’s Rhino.Geometry.Morphs.MeshCageMorph — a SpaceMorph subclass, added in Rhino 9.0
The constructor takes a reference mesh (the cage in its original state) and a target mesh (the deformed cage):
public MeshCageMorph(Mesh referenceMesh, Mesh targetMesh)
Because it derives from Rhino.Geometry.SpaceMorph, you get the usual morph surface:
using Rhino.Geometry;
using Rhino.Geometry.Morphs;
var morph = new MeshCageMorph(referenceMesh, targetMesh);
if (morph.IsValid)
{
// Inherited from SpaceMorph:
morph.Tolerance = doc.ModelAbsoluteTolerance;
morph.QuickPreview = false;
morph.PreserveStructure = false;
morph.Morph(someGeometry); // morphs a GeometryBase in place
Point3d p = morph.MorphPoint(pt); // morphs a single point
}
In the WIP there is also a hidden Rhino command called MeshCageEdit (because it is hidden it doesn’t auto-complete so you need to type the whole name).
It should prompt you to pick some geometry to morph, then a reference and target mesh, plus options for PreserveStructure and Tolerance(which only matters when the contents include NURBS geometry). It is history enabled, so you can then edit the target cage and have the contents update.
We weren’t entirely happy with the UI on this (ideally it would work more like the regular Cage Edit), which is why it is hidden, but we’d still love to hear your thoughts on it.
MeshCageEdit command worked good for me, just tested. Some people might not think to turn history on, or maybe it get’s turned off at some point from other operations, so it would be nice if the command wasn’t dependent on history to work as intended. For me, I’m more interested in the Rhinocommon bit.
Thanks!