Mesh won't relax

Hello dear all!

I searched a lot on this topic, did find several tutorials and working processes, but somehow my project won't work.

For a universitary project we are designing a tent, which is supposed to be a Burning Man pavillon. We build the tent's geometry in rhino, build a mesh in rhino and tried to relax it with Kangaroo - but the mesh remains as origin.

Maybe some of you have any suggestions on how to proceed? We guessed already that our input mesh might be not correct.

Attachments:

Replies to This Discussion

Permalink Reply by Benedikt Glampe on February 2, 2016 at 2:06am

they are kind of limited, that's true :P

Permalink Reply by peter fotiadis on February 2, 2016 at 2:14am

Imagine McNeil acquiring TSplines (too late AutoDesk did that) and men with the caliber of David/Daniel doing "some" stuff on that matter.

Permalink Reply by peter fotiadis on February 2, 2016 at 3:12am

On the other hand ... although on first sight this appears not related with tensile membranes ... give it a spin and big things may follow later on (i.e. bypassing meshes especially having "arrays" of membranes in mind > kinda the notorious Haj Terminal [Jeddah] by SOM etc etc).

Using 099 K1.

Attachments:

Bend_a_3dgrid_V1B.gh, 170 KB

Permalink Reply by peter fotiadis on February 3, 2016 at 8:51am

Found 20 minutes ... in fact 50.

Good news: things are rolling: it's 100 times faster than the Patch way (case: cones).

Bad news: Starling, WB are gone > all the mesh job is done by code

Ugly news: some intelligence more is required.

Shown the cone (in 3 modes) option.

Permalink Reply by Hyungsoo Kim on January 31, 2016 at 1:02pm

Better way to relaxation is to add "Side Edge Cables" and "Top Ridge Cables" to your simulation.

Attachments:

160131BMtent_reV2.3dm, 781 KB
160131BMtent_reV2.gh, 18 KB

Permalink Reply by Benedikt Glampe on February 1, 2016 at 7:39am

Hyungsoo thank you very much for your two revisions - these were very helpful indeed.What is the aim of integrating a third cable component before applying Kangaroo on the mesh (the third beside side and top ridge cables)?

Permalink Reply by Hyungsoo Kim on February 1, 2016 at 8:57am

Hi. Benedikt.

In my first revision, I just wanted to show you anchor point positions should be placed on your initial mesh. and the result was standard shrinkage of mesh by "Hooke's law".

And in the second one, I added two more "springs fr lines" in order to stabilize the net. You had already placed three compression posts, and cable anchors around th net periphery.

so, I applied additional spring stiffness to the selected ridges, and side edges. I can't give you details but, maybe Peter will. Best.

Permalink Reply by Benedikt Glampe on February 1, 2016 at 9:49am

thank you very very much!

Permalink Reply by Benedikt Glampe on February 1, 2016 at 9:55am

by the way how do you export these great screenshots? do you make separate ones and just combine them or is there another GH plug-in?

Permalink Reply by Benedikt Glampe on February 1, 2016 at 9:59am

Is there a chance to avoid the inner anchor points being connected so that I can create a hole in the mesh or does the hole has to be cutted out of the resulting relaxed mesh?

I created lines from the naked edges of the interior 6-corner-polygon to show the cutted hole.

Attachments:

hole.PNG, 233 KB

Permalink Reply by peter fotiadis on February 2, 2016 at 12:23am

As I said this "configuration" attempted it won't work in real-life.

For holes (cones in plain English: inverse [cables to ground] or classic [cables FROM top of masts]) you'll need to Patch the outer loops VS the cone profiles and then create a mesh out of the resulting Nurbs (or wait for the demo promised) and then feed this to K1/K2.

Permalink Reply by peter fotiadis on February 2, 2016 at 1:22am

This MAY help you (Patch is already done > A VERY tricky thing for the inexperienced, mind) to get the gist of the cones, the anchors and all these freaky things, he he,

Using the 099 K1 (as I said behaves "better" in some occasions).

Load Rhino file first.

Attachments: