(PAR) Generate a Lattice that Doesn't Crash the Computer

Columnas-Arboles_CantLattice.3dm (8.4 MB)

I’ve been trying for eight hours to generate a lattice through these columns-in-the-form-of-trees so that the things can actually hold up a building above them. Basically, I want a skeleton within them of steel, and then I’m going to put a skin of chrome around them. And I can’t make the lattice for the steel skeleton.

I’ve tried Interlattice, Weaverbird, Parakeet, I’ve tried following along with YouTube videos of a Voronoi method, I’ve tried doing each tree seperately, I’ve tried multipiping a lattice to then Boolean Intersection with the objects.

I’ve been able to generate one ugly skeleton for one tree, that wasn’t able to repeat for the other trees. Other than that, I just freeze the computer with most tries. I’m at the point now that I’m just, please, reaching out to the Internet to ask someone to do it for me. You can keep the cool looking trees for your projects in trade (as could anybody else who sees this thread) - they would be fine for landscaping if they didn’t need to be structural.

Please. Please and thank you. And tell me how to do it for myself next time.

1 Like

Seems related.

Maybe You need to draw your vision. Your file only contains these mesh shells.

It should look like this:

Here’s a Rhino 7 Version:
Columnas-Arboles_CantLattice_Rh7.3dm (8.1 MB)

Also the seemingly related Topic to which you linked is not the same because that’s about flowing a pattern along the surface, whereas I’m trying to generate a lattice throughout the interior of the SubD objects.

Hello
I really don’t understand. It seems you want trees and you have a file with some trees. But you ask for lattice. Lattice is most of time a repetitive pattern/structure. Please use some search engine to figure out what are lattices, tree, Voronoi diagram they are all different.

I have trees. These trees are columns. Therefore, they require a skeleton inside them, because sometimes they go horizontal, other times vertical. A lattice structure inside them, would be a suitable skeleton. If you have another alternative, maybe I-Beams, that would function the same, turning these trees into something that can support concrete loads ontop of them, then please offer those alternatives up. I appreciate your Wikipedia link about what is a Voronoi, and I apologise if I didn’t explain myself enough for you to understand that I want to build a lattice INSIDE the trees (that is, beneath the bark, in the void underneath the closed surface), but it’s not relevant to the discussion. I want to build a lattice, that is a repeating structure, whether Voronoi or Star or Cross or Whatever (so long as it’s strong enough to give these tree-columns structure), not in the shape of a rectangular prism, not in the shape of an ovoid, but in the shape of this network of trees.


Perhaps if we can see how much weight is borne upon the column-trees, we can understand why I need to give them a lattice inside them.

I was hoping that I wouldn’t have to draw the lattices by hand the way that I drew the trees by hand. If a lattice cannot be constructed within these trees without crashing the computer, then perhaps there are some suggestions, please for making these structurally stable that would be faster than drawing a lattice.

I looked at the Statue of Liberty for an example to copy. Maybe that’s the way to go?

1 Like

Lattice seems to be used mostly in 3d printed parts and in some cast. So for your structure that has wide variation between minimum radius to max size it means a very large numbers of cells so it means a generation of a big big mesh for something that surely can’t be made.
Lattice could have a meaning for small parts.

I thing you need to add some specifications

I think you’re mostly right.

Lattices | Dezeen Lattice is used in Architecture, so a big mesh can be made. The issue, more precisely, I believe, is the ratio of the lattice that would be required to be structural to the radius of the columns/beams (sometimes a branch is a column, sometimes a beam, depending on direction). It’s not so much that one can’t make a big mesh, but rather can’t make a small mesh iterated out sufficiently to fill such a big space.

For me, my solution is going to be taking the radius at the bends, offsetting it a bit to make space for the skin (shortening it), lofting those radii, and then extruding that surface to the thickness of a thick plate of steel, so that all the force is carried vertically down the steel (like an I-Beam, but curved instead of straight). I’ll need to hand-bomb it, but that’s the price I pay for making my tree-columns more realistic.

For anyone else who has found this thread by the search feature, if my solution above is not for you, then what you might try to do is scale a copy of your model really small, then make your lattice, import that lattice into your original model and scale it back up after its already a solid (NO CURVES!! TOO MUCH PROCESSING STRAIN!).