algorithmic modeling for Rhino
Hello again,
I have a curving surface and I divided it into 7 x 7 points.
When I check the normal of each point, I discover that the normal direction is quite erratic and not consistent in each row.
I use these methods:
object_surface.ClosestPoint(surface_point, U, V)
normal_vector = object_surface.NormalAt(U, V)
Looking at the attached image, you can see that the axis are flipping up and down in one row.
So I was wondering if the ClosestPoint and NormalAt methods are accurate, or am I doing something terrible wrong? :-)
What is the best way to get 'smooth' transitioning normals across a row of points?
Thanks again!
Fernando
Tags:
normal vector is just one vector(perpendicular to surface at uv coord), what youre showing in this picture are cartesian coordinate systems (I belive that you obtained them with normal plane component). forgive me if Iam wrong, but Iam partially colorblind so I cant see which axis is red/green :)
(Probably) plane with given z vector (normal plane) gets x and y axis by looking for world coordinate system, and so it can differ respectively to normal vector direction...
I preassume that .normalAt(u,v) works same as in surface divide component, which generates correct normal vectors (vector field ;))...
I'am also quite sure that David will add a new component which will be more flexible in planes generation (he wrote some time about it)...
"What is the best way to get 'smooth' transitioning normals across a row of points?"
IMO the best, but not perfect :
Thank you Mateusz! That was a great help, thank you for taking the time!
Fernando
I have to add/conclude that these methods are very accurate, and that the strange behavior I got was due to my script.
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
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by