Tobias Rosenberger

Let's take this string patch that rob once provided in another forum thread:

When this patch is opened, the string starts bouncing, after some time it finds its quiet position (see screenshot)..

Is there a simple way to open this patch, and the string is not moving, but already in its quiet position?

My workaround in such cases has been to make my phys objects invisible and init them earlier as needed or to send the final position matrix values in advance while kinematic is enabled. But that always applies some not so intuitive patching, especially if there are hinges as well...

Another always struggle for me:
Let's take this string patch that rob once provided in another forum thread:

When this patch is opened, the string starts bouncing, after some time it finds its quiet position (see screenshot)..
Is there a simple way to open this patch, and the string is not moving, but already in its quiet position?
My workaround in such cases has been to make my phys objects invisible and init them earlier as needed or to send the final position matrix values in advance while kinematic is enabled. But that always applies some not so intuitive patching, especially if there are hinges as well...


physics-please-stand-still-when-you-get-initialized

the reason it bounces is because the position of the hinge is different from the position of the attached body, causing the "string" to snap into place and swing around. if you want to remove this you must either set the initial position of the hinge (@position2) to equal the initial position of it's attached body.

again, thanks so much, now it works great(storing once matrix of final quiet position, then use it with loadbang in the patch!)

in attached patch i use a gridshape @matrixoutput 1 to generate the position array for jit.phys.multiple. But as soon as i don't send anymore, some parts are starting to drift away even if gravity and force are all set to 0 (Untoggle the big toggle). Anybody can say why?

it looks like there are duplicated vertices coming out of gl.gridshape matrixout. you can see this by setting the @damping attribute of phys.multiple to 1, prior to closing the matrix gate. you will have to filter out that duplicated vertex somehow. easiest is probably jit.submatrix @dim 19 19

Physics: Please stand still when you get initialized