I have a surface, which is a roof with some cut outs, I need to add trusses, for which i am trying to divide the surface. If i choose DivideSurface component, it is choosing an inclined direction to divide the surface in U and V direction. as shown below in Blue and Red lines.
The question is, is there an option to choose the direction in which the surface can be divided. for example, i need the surface to be divided as shown below in Blue and Red Lines.
The answer is yes - more than one option. However, looking at your second image with the âdesiredâ result: is your grid intended to be âcurvedâ or âradiatingâ or are you just trying to change the direciton of the the division lines?
In the meantime, I include a couple of examples here: Internalised_File.gh (481.5 KB)
If just intend to specify division direction, you can use contour:
If youâre trying to use a guide curve you can use something like this as a starting study method:
Note:
Start and end points for the guide spline are internalized so they can be moved manually, while the midpoint is just the average surface point - nonetheless all these point locations can also easily be re-established both on the surface itself or on its bounding rectangleâŠDepends on what you want.
Hah, those are both rather bizarre methods. The trouble with the first method using MD Slider is that the vertical angle of the contour reference plane changes so the distance between contour lines also changes, independent of the âDistanceâ slider. In other words, the distance between intersections is unpredictable and canât be set. To some extent, that is also true for the second method.
To me, precision is more important than speed. To that end, I added the white group to adjust the position of the X and Y planes, added separate âDistXâ and âDistYâ sliders to set the distance between planes on each axis and added âXâ and âYâ axis labels (purple group).
I feel you, Joseph - itâs okay. I like playing with geometry. I could have provided something strict as well. Please donât think others arenât capable of coming up with your level of solutions. I deal with enough âprecisionâ at work and I always crave going back to play. Itâs fun. Precision keeps you constrained and limited. I wouldnât mind if @Raqueeb_Ali changed their mind and chose you as the correct solution - your work is great and superior
Thanks @Joseph_Oster , Actually, this gives me more flexibility to divide at different intervals for both directions, which I need to control the number of divisions in both direction depending on the spans. But as in curves, I am not able to locate points associated with each cut plane as a group of points/Curves, Intend to use each cut plane as a Truss for this roof (move the same curve below, divide them and connect the points to form truss members) something like below image.
No biggie - itâs possible to associate after the MCX.
Thanks for clarifications - your questions arenât trivial - and thatâs precisely what I meant by choosing a playful approach - usually new GH users donât necessarily explain the whole goal, so you canât solve for all things when providing help, especially if the person is in the initial stages. But thatâs the beauty of this forum! Joseph can now take over!
Just keep in mind that if the goal is to make the trusses in the real world, our solutions are kind of pointless!
Until I realized the effect of the holes in the roof on the data tree structure, so added the Untrim plane intersections (gray group). Itâs possible to take this one step further and get a âtrimmedâ roof without holes⊠but Iâm not sure it would be much better.
I decided it would be good to show the points on the edge of this surface. Then found in that process that the intersection curves were no longer splitting the surface as expected. Missing surface fragments:
The labeled points correspond to the âPoint Listâ text panel (gray group). There is an anomaly due to the surface shape; at the top left, there are two red points (0,1) and then a gap in the surface followed by three orange points (0,1,2). But thatâs easy to correlate with the text panel list.
Again, for fun, to help, not to compete with Joseph.
In the attached, Iâve done a second pass to address point order per each of the contour directions d1 and d2. This, without being exactly sure on what order you should have, though thatâs an easy change, so feel free to specify later. Nonetheless, number tags are there.
Again, d1 and d2 for contour directions, each with their distance so theyâre not the same as before:
Lastly, the only thing {intentionally} not addressed is cleanup at surface holes - I simply donât know if youâre after that or not, just like I donât know the overall âdepthâ of this project and many other things
Many thanks @Joseph_Oster for all the support, really appreciate the help. This looks a bit advance to me, I will understand these operations node by node and let you know. Thanks again.
I hid the planes point list as it was distracting, but itâs still there.
P.S. Oh dear, I inadvertently bypassed the Data Dam, slowing down response to rotation and adjustment of planes. Fixed it in version 'Feb16eeâ. Sorry about that!
This post is completely inappropriate. 
