Easy Parametric Truss (Grasshopper)
Vložit
- čas přidán 25. 07. 2024
- Simple Grasshopper script to create a parametric truss with different bracing patterns using [Relative Item] component.
The output truss geometry is Karamba-ready for analysis (or export-ready to any other analysis software).
Check back later for more content as we continue to upload. Please comment below any thoughts or constructive feedback. Keep on 'hopping!
The Grasshopper explanation of the parametric truss is simply revealing. I use this a lot for architecture. Engineering and architecture can blend together perfectly in Grasshopper 3D
Thanks a lot for your great video with a lot of tips which I was looking for.
Thanks for dropping by! Glad you found this useful. Let us know if you would like to see something more specific.
Thank you, for this great explanation :)
You're welcome Ai. Appreciate the feedback!
Thank you!
Great tutorial! Could you do another one with even more pattern styles? Or a simple guide on how to make up your own pattern styles.
this video is Gold, thanks man, it was super helpful and well explained
It would be great to see the next part, analyzing the truss with Karamba. Greetings from Barcelona!
@@sergiguiri You're inspiring me to get the next part up; and I will now. Thank you for the feedback!
@@parametricengineer7046 You're welcome! Right now I'm working on parametric trusses and force diagrams, and I've used your video to start with it. It would be amazing to see further videos from you!!!
@@sergiguiri Karamba tutorial uploaded, check it out! I'm interested in what you are doing for force diagrams as I have been developing definitions to display analysis results in a better way.
@@parametricengineer7046 Thank you!!! I'll definately check it out!! Sure, we could share a few things about graphic statics. I've been also trying to do a force diagram for the truss. We could contact by email, mine is sguirao.costas@gmail.com and maybe we can show each other a few things!
Also request you to add Karamba in the video title, so that it shows in relevant searches as well.
Karamba is tagged in the video Tag settings as well as in the description, though this video's focus is more on the geometry. There is a second part to this video specifically for the Karamba workflow. Please check it out! czcams.com/video/sZXfT9aXhcg/video.html
GCC countries could be slightly annoying when it comes to meetings or recordings haha, great work no doubt!!
Lol, need a better studio or watch my recording times!
I tried putting it into Karamba3D, You will see that the chords are not connected to the vertical members. I had to do allot of further manipulation to get the chord into separate segments. Great video, please upload more!
Hello Kgosi, please check out the video at 12:36 where we create the chords using [Relative Item]. We take the grid of points, and then join one point to the next adjacent point (within each branch, within each chord line). In this way, the chords are segmented, and as we are using the same grid points for the verticals and diagonals (just a different mask for the [Relative Item] node) all the line members should node up perfectly in Karamba. Hope this helps but let me know if not, I'd love to work through the issue with you.
@Kgosi we've uploaded a basic Karamba set-up video.
czcams.com/video/sZXfT9aXhcg/video.html
Let me know if this helps you. Any issues, let me know and we can try to respond.
21:00
Hey,
Could somebody please help me? All the combinations are doing the vertical lines, except the combination {+0} {+1}, because it does nothing.
Thank you for your answers in advance!
Hi. I believe you are dealing with the Relative Item component. The offset mask is in the form: {branch offset} (item offset) but you have to be careful with the brackets. Curly { brackets } for branch offset and curved ( brackets ) for item offset. So to get vertical lines use: {+1} (+0). For diagonals use: {+1} (+1), etc.
Also, the Tree input should be simplified... to make your offset notation easier. You don't have to but your offset notation should then match, so may look like: {0;0;+1} (+2) to match the data structure of the incoming tree.
@@parametricengineer7046 thank you very much for the help! Sure I put all the numbers into curly brackets! Now it's working properly. :)