K2 anchor points move.gh (19.3 KB)
Plugin: Weaverbird.
I thought if I add enough strength to the anchor points, they would not move, but here no matter how much strength is added, they still move.
1 Like
It looks like the vertices output from Weaverbird are using the double precision Point3d
(https://developer.rhino3d.com/api/rhinocommon/rhino.geometry.collections.meshvertexlist/point3dat)
which does not give exactly the same points as those from the standard mesh vertices component, or other components using many of the standard RhinoCommon methods for getting points from meshes which use Point3f (here’s a thread that goes into it a bit).
(https://developer.rhino3d.com/api/rhinocommon/rhino.geometry.collections.meshvertexlist/item#)
At this scale the difference is bigger than the default tolerance on the Solver component, so they get treated as separate particles. Changing the tolerance on the solver from 0.0001 to 0.001 lets them combine.
3 Likes
Thank you very much! I know the author of the weaverbird is working in McNeal, I wonder if he has spare time to update the Weaverbird’s components. This is one of the perfect plugins for mesh operation in GH.
It’s actually Weaverbird which is using the more up to date Point3d method here.
There are many functions in Rhino and Grasshopper that still use single precision vertices though, so these small differences still show up.