which I want to develop with diagrids or other surface transformations.
My problem is that I can't evaluate the surface in anyway (I assume the u,v system for evaluating surfaces can't be applied to this non -rectilinear surface). BRep components return a 'null surface' message.
What basic principal am I missing? Can anyone advise me how I can handle this geometry? It is important that I be able to retain control of the edges of this surface as they are show above, as well as evaluate and modify the surface itself.
Thanks for any help.
Best Regards, Matthew…
face to drape on geometry below.
Image 2: Image from http://madeincalifornia.blogspot.com.au/2008/12/gridpointssurface02.html
Can u please help out. Cheers, Jono…
but very useful !
But I want more !
How can I swap just the U or V direction separately ?
So this is my wish :
This may be very simple , but it's too hard for me to write code myself . Who can help ?
…
extrusion along the line.
Q1: after i keep trying, i found out that some of the points join twice with others (eg: A to B , A to D) how to make sure the just join one time?
Is my method of orientating the polygon correct? since i would like to put attraction points that influencing the size of it just on the outside.
sorry for my bad English, hope that u guys understand what I am trying to say.
file is attached so that its more clear.…
onto a plane using Point Oriented in grasshopper and get a resultant plane with origin point (-152.78838, -1065.812137, 1436.310291). If I perform the same operation in ghpython with Point.At the resultant point is -153.792951019493, -1065.84279597442, 1436.31029129594). The x/y/z vectors defining the plane are identical. The difference seems small (.03mm), but once curves are drawn on the planes, it is the difference between CurveCurveIntersection working at a normal tolerance (.01) and only working at a really slack tolerance (.2).
So, I have two options. One is to understand what is tripping me, and the other is to find another method to orient a point to a plane using u/v/w parameters. Any ideas?
Thanks so much, Kendra
…
isation.
It is however limited to be changed only by U and V values.My goal is to change the direction of the entire grid on a given surface and keep it flexibel with for instance sliders.
The diamond panels shouldn't point into a straight direction over a given surface, but be oriented in a skewed direction. However, they should remain in their original UV-based panel form and stick to the base surface (or better said form the set surface).
Any ideas how I can accomplish this?…
5.0 model containing 6 surfaces (patches).
The function of the attached GH-script is to generate Normal lines at the centroids of the input surfaces from Rhino. The input surfaces have all the same direction, here "upwards" according to the "Dir" command in Rhino.
As a "normal" user, I was expecting that the generated Normal lines in GH have the same orientation/direction as their corresponding input surfaces. However, NOT all generated normals are equally oriented as their input surface. WHY ?
I got out that the U- and V-directions of the input surface play a role here, but from a "normal" user -perhaps naive- viewpoint, I was expecting coincident results between Rhino and GH.
Can I expect a modification in the "Evaluate Surface" component or shall I look for another solution?…
Do U know some overall effective way just to keep the cornerpoints, and remove the other (for me disturbing) points?
Please see attached some ways, which are not working well :-(
1, "Polyline collaps" component --> getting strange result
2, "Reduce" component --> in the most of the case it works, but not always
3, "Rebuild curve" component --> it is just generating polyline automatically (not between my corner points)
4, "Simplify curves" component --> not really working by me
If you have some god suggestion, I am glad to see your comments.
Thanks for your feedback.
Cheers
Zoltán
…