secondlife / jira-archive

3 stars 0 forks source link

[BUG-215954] [Animesh] Completed non-looping animations need to automatically be removed from an Animesh object's animation list. #3458

Open sl-service-account opened 6 years ago

sl-service-account commented 6 years ago

Information

In anticipation of work to make already playing animations show to users entering a region as well as from adjacent regions and after region start, I figure it is a good time to file this due to concerns with a project I've recently undertaken.

In said project, there are multiple animations playing with varying priorities, lengths and looping/non-looping status.

It is a daunting task to keep track of short lengthed, non-looping animations just so they can be explicitly removed from the animations list when they should auto cleanup the same way non-looping animations auto cleanup from a user's animation list as seen through the viewer and llGetAnimationList().

Another problem with not removing already completed non-looping animations is the fact you cannot play said animation again until it has been removed from the list.

An additional concern comes when the fixes are made that completed, non-looping animations will show for anyone entering the region, when they should have been auto cleaned up.

Links

Related

Original Jira Fields | Field | Value | | ------------- | ------------- | | Issue | BUG-215954 | | Summary | [Animesh] Completed non-looping animations need to automatically be removed from an Animesh object's animation list. | | Type | Bug | | Priority | Unset | | Status | Accepted | | Resolution | Accepted | | Reporter | Lucia Nightfire (lucia.nightfire) | | Created at | 2018-03-25T01:24:45Z | | Updated at | 2020-05-11T15:27:56Z | ``` { 'Business Unit': ['Platform'], 'Date of First Response': '2018-03-26T11:50:54.862-0500', 'ReOpened Count': 0.0, 'Severity': 'Unset', 'System': 'SL Viewer', 'Target Viewer Version': 'viewer-development', 'What just happened?': "In anticipation of work to make already playing animations show to users entering a region as well as from adjacent regions and after region start, I figure it is a good time to file this due to concerns with a project I've recently undertaken.\r\n\r\nIn said project, there are multiple animations playing with varying priorities, lengths and looping/non-looping status.\r\n\r\nIt is a daunting task to keep track of short lengthed, non-looping animations just so they can be explicitly removed from the animations list when they should auto cleanup the same way non-looping animations auto cleanup from a user's animation list as seen through the viewer and llGetAnimationList().\r\n\r\nAnother problem with not removing already completed non-looping animations is the fact you cannot play said animation again until it has been removed from the list.\r\n\r\nAn additional concern comes when the fixes are made that completed, non-looping animations will show for anyone entering the region, when they should have been auto cleaned up.", 'What were you doing when it happened?': '?', 'What were you expecting to happen instead?': '?', } ```
sl-service-account commented 6 years ago

Vir Linden commented at 2018-03-26T16:50:55Z

Technical note: this would certainly be handy, but it would also be a fairly significant undertaking. The problem is that the simulator does not have any detailed information about the animations that are playing - basically it just knows the asset ids, which it passes along to the viewer when needed. So to add this type of loop checking, the simulator would have to fetch and parse all requested animations to figure out things like whether they are looping, then modify its behavior based on this information. Performance impact would also be uncertain if we tried to add this.

sl-service-account commented 6 years ago

Lucia Nightfire commented at 2018-03-26T20:32:07Z

I can always be added to the Long List of Things to Do™, heh.

sl-service-account commented 6 years ago

Vir Linden commented at 2018-03-27T12:13:09Z

We'll bring this in as part of the "maybe Animesh 2" list. Realistically it's only going to happen if we have some other compelling reason to add simulator-side parsing of animation data.