[BUG-230724] Add new LSL functions to play sounds via child prims #8336
Comments
Aliton Firehawk commented at 2021-05-09T21:40:41Z This would be an extremely useful feature, and will heavily reduce certain projects I have on their script resources. |
yasmina.zimminy commented at 2021-05-09T21:42:11Z Would be a useful feature |
JIRAUSER337086 commented at 2021-05-09T22:31:58Z This feature would help save on script resources, which is extremely important in a variety of environments in Second Life. I think it would be greatly appreciated. |
JIRAUSER337083 commented at 2021-05-10T21:26:28Z I work at Fantasy Faire, and we face many challenges relating to scripts. Any project which will be of benefit to SL at large, but our specific challenges as well, would be greatly appreciated.
|
Whirly Fizzle commented at 2021-05-11T18:23:52Z Note for Lindens: I think this suggestion is already filed internally at SL-11982 |
Whirly Fizzle commented at 2021-05-11T18:24:42Z
Yes, this is a known bug with JIRA. The Lindens are working on fixing it. |
Kyle Linden commented at 2021-05-12T17:55:57Z Hello, This is a duplicate request of BUG-227641 Thanks! |
How would you like the feature to work?
Add at least four new LSL functions: llPlayLinkSound, llTriggerLinkSound, llLoopLinkSound, and llStopLinkSound. These should operate as their non-link versions, but offset to a specified child prim.
Why is this feature important?
There are often times you need to offset a sound source from the root prim. The root might be offset to allow for better rotational handling, or might be something that handles multiple sound sources (something that governs multiple doors, for example). Currently, the way to achieve that is with secondary scripts that communicate with the primary one, one for each new sound source. This can quickly clutter what would otherwise be a one script project with half a dozen four line scripts that only play sounds off of commands from the main script.
Being able to call sounds in link prims would thus reduce the amount of total scripts (and costly script communication) for a swath of project types, but also make things cleaner, easier to understand, and more in line with the powers singular scripts typically have over root prims (with llSetLinkPrimitiveParams et al).
PS: The Feature Request form seems to be having an issue and wiped all my input. This was manually recreated.
Links
Related
Duplicates
Original Jira Fields
The text was updated successfully, but these errors were encountered: