Help ObiSolver.Lateupdate() bad performance

[TheMunk]

When you stitch two particles together, they will try and collapse into a point. Stitching the way you currently are is guaranteed to cause a mess.
Overlap the ropes and then stitch them, just like you'd do in real life to sew two ropes together:

Code:

   
          (o)--------(o)---------(o)
           !          !
(o)-------(o)--------(o)

The "!" are stitches, (o) are particles and ------ rope segments. Hope my shitty diagram makes some sense, let me know otherwise.
Don't forget to deactivate collisions between the stitched particles, otherwise they will try and collide with each other.

Thanks, think i got it!


Also figured out the IL2CPP performance issue apparently was because i was using "debug" compiler configuration - which normally is not an issue, but may have big implications for Obi.