Edit me

Multi-avatar SYNC poses (loops with shared timing, such as cuddles and dances) drift between viewers over time. The most common cause: a viewer culls and re-acquires an avatar (camera zoom, region crossing, draw-distance change). On re-acquisition the viewer restarts the looped animation locally at t=0, while other viewers keep their original timeline.

QuickySitter exposes a single LinkMsg that any in-prim script can send to force every sitter slot to re-phase its main pose loop in the same Sim frame.

The trigger

Num Direction msg id Meaning
90271 hudproxy / any in-prim source → all [QS]sitA slots "" "" “Every SYNC-pose sitter, do one Stop+Start cycle on your main anim now.”

That’s the entire integration. Sending the LinkMsg is one line:

llMessageLinked(LINK_SET, 90271, "", "");

Handled by current [QS]sitA (release 1.25; scripts carry per-script versions between releases, uniform only at a release stamp).

Safe to broadcast

[QS]sitA applies the trigger only when it makes sense: a SYNC pose is playing (no P: prefix), a sitter is seated, and animation permission is held. Anything else (an empty sitter, a solo P: pose, a permission-pending window) is silently ignored. Broadcasting 90271 is therefore always harmless.

When and how often to send is entirely the sender’s decision. QuickyHUD’s SYNC button is one such sender. [QS]boot is another: it runs the AUTOSYNC ticker (driven by the QPP_CFG:AUTOSYNC setting, 60 / 120 / 180 s) and fires 90271 on each tick, so re-phasing keeps happening even with the HUD detached. Any other in-prim script can send it too.

See also