Hello there !
I have solid rectangles trapped inside other solid rectangles, is there a way to avoid that ?
Ouhhhhh, I’ll try, thanks
@inno It kinda works but it seems that component A is just doing the same thing as component B but with more time.
Which one is better if I am just simulating flat surfaces ?
not really able to give you a good answer based on pixels 
generally speaking (as far as my understanding goes) the curve collider will detect and calculate collision, so if curve A touches curve B, they won’t cross through each other, but will keep touching /overlapping each other
Solid Point Collide, on the other side, will force some points to stay on the inside or on the outside of a given mesh: it won’t calculate the intersection, it will just force them in or push them out
1 Like
I have no idea how your script is organized 
you keep on posting pictures, which is like asking what is wrong with the smell of your stew by pshowing a video of it boiling
I see something that could be weird but could also be fine in the type of wires connected to the Solid Point Collide, but it’s just a wild guess:
Points input is getting a data tree, meaning a collection of Lists, each of wich carries one or more items
while
Solid input is getting a single List of items: the wire is thick, so there are 2+ items in there
I don’t know how your data is organized, but given the situation and assuming that Kangaroo component handles data tree the classic way, my best guess is a data tree issue
having in Points the tree:
{0}: P1, P2, P3, P4, P5, …
{1}: P1, P2, P3, P4, P5, …
{2}: P1, P2, P3, P4, P5, …
and in Solid the List:
S1, S2, S3
would mean that, for each branch {0}, {1}, {2}:
P1 can’t stay inside S1
P2, can’t stay inside S2
P3, can’t stay inside S3
P4, can’t stay inside S3
P5, can’t stay inside S3
…
Pn, can’t stay inside S3 (S3 which is the last item in List: Solids)
1 Like
