Hi Guys,
I am building a set of Grasshopper definitions to be able to generate simple Building elevations from their footprints.
Currently I got a base setup.
I am trying to make a glass wall with recess areas. Basically I divide curves and then create a perpendicular lines.
But for some reason it does not work on curves and circles ? What I am doing wrong?
Cheers
BuildingShapes_01.3dm (3.8 MB) Type_01.gh (24.4 KB)
I also have a problem with ends. I have a left over lines which I don’t what to use. I used cull pattern to remove them, but in some cases I still have them?
Hi,
Hard to say, beacause you forgot to internalize the curves.
But maybe this helps you a bit :
Type_01_re.gh (24.2 KB)
He posted a Rhino file containing the curves.
I haven’t tried to fully debug/optimize your code but after messing around a little, I found that setting the ‘W’ (Wrap) input to Cull Index to false (inverting the default), alignment was as expected:
There may be more things like this…
P.S. This (below) might not be exactly what you want, but it’s easier to understand? And modify if necessary. The purple group is a different way to align the planes. Shift List with ‘W’ (Wrap) set to false ignores the first plane, as I think you were doing before? You can connect it to Partition instead of PRot.
I used Partition and Prune Tree to handle that problem.
Irrelevant code has been removed and curves are internalized, no need for Rhino file:
Skipped that, my bad.
Thank you Joseph for reminding me that Prune Tree exist !
I thought it would be cool if the “balconies” (or windows?) were evenly spaced on each side so spent some time wrestling with data trees to come up with this:
It’s tricky… Inputs (besides the perimeter curves) are:
Two Evaluate functions are used to calculate the “gap” for each edge. It sorta fails (not really) on the circle, since the gap at the seam is twice as wide as the gap between balconies, but otherwise looks pretty good. 
Morning Joseph,
Thank you it is amazing. It will keep me going for a while and I will post the final thing.
It just recentlyI spent a week modelling almost identical buildings in SketchUp manually.
And I thought I can just create a family of building types so I can use only a footprint to build a massing with simple elevation.
For glass I thought to use three offset planes each of them will have different texture:
Is there a way to assign and map textures to surfaces in Grasshopper. So when baked they have a material applied?
When it is rendered it looks very good.
Please see attached images for reference.
Hey Guys,
Does Graft doesn’t work with contours EX ? I had 9 branches, but after slicing the model it (contours EX) gives me something strange ?
I’m sure there are many ways, perhaps more in R6 than R5. The only method I’ve used is to assign a different material to each layer and bake my geometry accordingly. I cobbled together two Python components from bits found here and there, probably far from optimal but they worked well for me.
bake has inputs for ‘geo’ (geometry), ‘layer’ (name of layer with “::” between sublayers) and ‘active’ which triggers it.
DelAll uses the same layer names to delete all geometry on those layers.
This is an extract from a much larger model with many layers. It was quite fascinating to delete and bake all the modified geometry in a complex model and have materials assigned, ready for rendering. The Rhino file is optional since the named layers will be created if they don’t already exist. But of course, the point is to preserve the material assignments by layer.
No model, no comment.
Cheers. Looks like I can use Human for it. Will have to look into it a bit more in terns of scale relative to floor height…
File attached :))
Type_01.gh (36.5 KB)
Found it ! Shift component helped !
I had a mental block yesterday that led to the rather absurd idea requiring Series and ‘Max’ (maximum number of windows expected on any side).
I got over it and offer the following, which gets the same results. Much simpler! (white group)
Hi Joseph,
Thank you for your help and interesting solution. I was developing and organising the model last night as well. I changed the way massing is generated to get more random heights to it.
Because of this I now have a couple of issues:
Some slabs are missing, there is something wrong with "contour " component it produces not closed curves. Which then missed from slab extrusion
I haven’t found an ease solution to how isolate lower portions of the building roofs. Currently I just select the top ones. I will have to select them before I merge them.
Your solution works, but I need too organise it so I can tel from which building footprint curve it came from so I can extrude them randomly to reflect different buildings heights.
I also need to remove parts of the “balcony” curve so it’s a zigzagging line .
I have attach my WIP files.
Cheers
BuildingShapes_01.3dm (3.8 MB) Type_011.gh (31.5 KB)
Don’t hold your breath. Understanding data trees is a never ending quest that each of us must ultimately face alone.
Cool! Thank you for the link
Unless something hurts as much as it’s supposed to, nothing gets done about it.
– John Oliver, August 4, 2019
Data trees are curious things. They require constant attention when building a model. I do this by examining the output of every component along the way, usually with text panels and when necessary (frequently!), using the ‘vuTreeList’ tool I referred you to earlier.
I looked at your code/geometry in your original post in this thread but haven’t looked at any other versions because it’s too much work. The answers below use the simplified model I posted yesterday.
First, this yellow group numbers the perimeter curves. They are the basis for all the data trees that appear along the way, so keep these numbers in mind:
The “guts” of what I added today are in the cyan group (below). Simple, right? 
Shatter uses the same segments from Explode and the ‘t’ (lower case) values from Evaluate Length to split the perimeter curve edges at the “balcony” locations, then Cull Pattern gets every other piece, effectively ignoring the parts where the balconies are located.
The first Join Curves component combines the short Line SDL bits and the line that connects them. Nothing tricky about that but notice that ‘Simplify’ is used on its output. In fact, ‘Simplify’ is used three times in this cyan group, none of them arbitrary, all are required to get the downstream data trees re-aligned. This is very important to understand. Use text panels and toggle ‘Simplify’ to understand why.
The purple group at the bottom generates 14 random integers (one for each perimeter curve) representing the number of floors for each building. But as you might guess, this presents a different problem due to the fact that curves 0, 11 and 12 aren’t separate buildings at all but intended to be “holes” in their surrounding curves (13, 4 and 9 respectively). I didn’t try to solve that problem.
Here’s what happens by first passing the perimeter curves through a Boundary component to get the holes (light blue group):
Then using the edges of those surfaces instead, no other changes! So very close to perfect except for “building #10”, whose inner “hole” edges are too short for any balconies so the model fails to handle it properly. I wonder why…?
Great! Now I know what I am going to do on weekend )) Will be working my way through your definition 
I found a way to isolate roof parts of lower buildings. I just select them before I do brep union.
BTW Rhino 6 able to apply any material in you have created in Rhino inside GH. You can also bake them. So no need for any additional tools.
