The Spline Paths operator can be used to convert particle trajectories, bindings and relationships into splines.
Multiple operators within the same flow can send particles to the same tySplines object, but you should not send particles from multiple flow objects into the same tySplines object, or else the resulting splines will not display correctly.
Trajectories: particle positions will be sent to the tySplines object at each step of the simulation, as trajectory data.
Siblings: particle sibling data will be sent to the tySplines object.
Connect to parent: when enabled, the youngest child of a set of siblings will be connected to the parent.
Parent: when enabled, particles will be connected to their parent (if they have one).
Target: when enabled, particles will be connected to their target (if they have one).
Neighbors: particle neighbor proximity data will be sent to the tySplines object.
Particle bindings: particle binding data will be sent to the tySplines object.
PhysX bindings: PhysX binding data will be sent to the tySplines object.
Torn/broken bindings: controls whether data for torn/broken bindings will be included.
ID enable: controls whether only bindings matching a certain ID will be included.
ID: the ID to match.
Equal: bindings will be considered a match if they have the same ID.
Not Equal: bindings will be considered a match if they do not have the same ID.
“Enable on substeps” can usually be left disabled. It is only necessary when particles are moving so fast that they require extra substep samples for things like motion blur. Enabling this setting will increase the amount of RAM required to store tySpline data, relative to the number of substeps required for the simulation.