Client-side AO (animation overrider): own implementation, collar/script compatible, notecard import #496
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream#496
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Many users miss Firestorm's built-in AO. Build our own client-side AO. It replaces default animations from the viewer, so it costs no script time, needs no worn object, and works in no-script regions. It must cooperate with collars, poseballs and scripted animations.
Requirements
AO sets from an inventory folder, with one or more animations per state:
Stands cycle randomly or in order on a timer, and you can switch to the next stand by hand.
Import of existing AO notecards (ZHAO-II / Oracul formats, which most AO products ship with), so people keep using the AOs they own. Also compatible with Firestorm's
#AOinventory layout, so Firestorm users' AO sets work.Sit override as an option, switched off automatically on poseballs and furniture with their own animations.
Works with collars and scripts:
llOwnerSaypatterns, and the viewer reacting to animation-priority takeover.UI/UX better than Firestorm's: a compact on-screen control (on/off, next stand, set picker), a full editor floater, a toolbar button and chat commands. Clear feedback when it's paused, and why.
RLV respected, and no conflict with a scripted AO HUD the user is wearing (detect it and offer to pause).
Rules
Use Firestorm's behaviour as a compatibility reference only (released versions). Write our own implementation; no Firestorm code, XUI or art.
Related: #428 (LSL bridge), #463.