algorithmic modeling for Rhino
Well, I'm still too foggy in my brain from all the snot (excuser le mot), I should be in bed... But I think the direction should be okay, otherwise it wouldn't be the closest point, right? Forget my edit from before. I'm off!
hahah
Well, when the closest point is very close to an edge, the normal direction must be perpendicular to one face, with plane (pt, Vect) does not happen.
personally I think its not necessary as its not always needed. That's why the evaluate component exists. If anything uvP makes more sense to be part of that component.
The breps have UV coordinates? I mean, without being those of their separate surfaces.
Well, it is not necessary but neither superfluous, as had the def. I thought... why not add the normal plane (or uv's) to the component for a future version?
I used this component this week and my wish at the time was to identify which surface of the BRep the point was related to so that I could then do things with that surface based on which point it was closest to.
NB: In my mind this makes complete sense :S
Here's a script to output the normal vector of the BRep at its closest point - this should be sufficient to retrieve the plane.
Yeah, this is a strange behavior of RhinoCommon's own "Brep Closest Point" function. I've modified the script to get around it. Hopefully this is closer to what you need.
Thanks Andrew, I will store in my panel components ;)
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by