Scripting Attachments

ObiParticleAttachment is a component used to attach Obi particles to a target object in the scene. It works with all Obi actors (cloth, ropes, etc). There's two different ways an attachment can work:

Static: Particles behave kinematically, as if parented to the target object.
Dynamic: Particles interact with the target object dynamically, via force exchange. This allows for two-way coupling with rigidbodies.

You can add attachments at runtime too. This is how you create an attachment:

var attachment = actor.AddComponent<ObiParticleAttachment>();
attachment.target = targetTransform;
attachment.particleGroup = particleGroup;

You can also change the particle group and/or target at runtime. As soon as you change either the particle group or the target, the attachment will rebind itself: all particles in the particle group will be attached at their current positions relative to the target transform. If you wish to attach the particles at some position other than their current position, use the particles API to set their positions before creating/modifying the attachment.

Particle groups are small scriptable objects that contain a list of particle indices. They can either be created at runtime:

var group = ScriptableObject.CreateInstance<ObiParticleGroup>();
group.particleIndices.Add(particleIndex); // index of the particle in the actor
attachment.particleGroup = group;

or retrieved from the actor's blueprint:

attachment.particleGroup = actor.blueprint.groups[0];

The blueprint's groups array will contain as many particle groups you have created in the blueprint editor, or in the case of ropes/rods, as many control points the blueprint has.

You can enable/disable attachments at runtime just like you do with any other component in unity:

attachment.enabled = true; //enable the attachment
attachment.enabled = false; // disable the attachment

Note that setting the target to null on an enabled dynamic attachment will cause the attachment to lose its reference to the target object, which makes it impossible for the attachment to remove the pin constraints if you later disable the attachment. Always disable the attachment before setting its target to null.