I have been trying to create a membrane simulation in Kangaroo which worked first few times I ran the simulation but then suddenly started to fly away and I can’t find the issue what has changed or why it does so..
Has anyone got some tips? I attached the image of the definition.
no, I haven’t tried it but will give it a try as well!
in the forum here
i was suggested to extract the anchor points from the last geometry that I am going to plug in the simulation. It seems to work now well, but I will check out also your suggestion it’s always good to have a couple of options to work with
Hi Marija,
There are examples of how to do tensile structures like this in Kangaroo2 here:
Probably the one ‘SimpleTensile.gh’ is most useful.
I’d really recommend trying the new Kangaroo - it solves a lot of problems from Kangaroo1 with stability and the timer, and it makes it easier to do things like this where you change the position of the anchors.
My simulation doesn’t fly away, but if I try to control edge cable tensions discreetly (through a value given as the curve names), then the mesh doesn’t converge.
Turns out, the soap film component seems super-unstable as it’s exactly the same problem if I disconnect the curve length target.
Using the “Edgelengths” component instead of “Soap film”, I’m able to reach the equilibrium I’m looking for.
The SoapFilm goal has no in-plane stiffness, so it always needs to be combined with something else to keep the vertices from drifting too far. One way would be to anchor the vertices in X and Y, another would be to use TangentialSmoothing: 250408_Form-Finding_modified.gh (94.5 KB)
A little more info here:
EdgeLengths is generally simpler and easier to use, SoapFilm is more just for when you want to find a true minimal surface.
Where can I find this kind of information other that struggling, posting on the forum and getting answers from you ?
I know you are very reactive and helpful, but what’s wrong with the good old concept of online documentation for a software ?
Is it strictly compulsory for Grasshopper plugins to comply with the general lack of proper documentation GH is known for ?
It looks like that example file contained a component from an older version - I thought I’d fixed all these, but apparently missed some. It is fixed now: