• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: SVC-2308
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Talia Tokugawa
Votes: 10
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
2. Second Life Service - SVC

Introducing some kind of local avatar sensor into the client.

Created: 06/May/08 06:11 PM   Updated: 17/Apr/09 10:18 AM
Component/s: Performance, Scripts
Affects Version/s: Mono Beta, 1.21.0 Server
Fix Version/s: None

Environment: Any.


 Description  « Hide
I just had a thought as to how to reduce script time on the entire of Second Life. (Timeless prototype, Mystic Cookie and Others are going to love me for this.)
With the Introduction of the avatar rendering costs display in the new RC, and the terrible lag that is seemingly all over Secondlife at the moment. I was thinking about things that all avatars have. I know not all avatars will have things like this but I am guessing most will. I personally rec
Most people I know will have some kind of local avatars sensor. MultiGadget, MystiTools, etc etc. All of these will be running sensors continuously. Two avatars standing next to each other will be running two sensors and getting pretty much the same results from those sensors. Which obviously will cause server lag. Additionally
think about the voice chat. That will again double up the amount of data those agents client machines require from the servers. (correct me if I am wrong but agents running voice need avatar position data from the server so that ventrillo knows the appropriate levels for the clients to playback the voice chat at.). Even without Voice and the sensor devices. The Client machines must also be getting data on the positions of the avatars for rendering purposes.
So, My suggestion. Include some kind of local avatars list, with the information on it like distance, away, busy, on voice chat, etc etc. All of this information is being sent to the client anyway.
We already have a "Speaking on Voice" list. It would just require adding a few extra sections to it. I am thinking something like the IM list where we get information on the avatars, such as mod rights and whether they can be mapped or not. So the "Local Avatars List" would look the same as that, but would have columns for Away/Busy statuses, whether the agent is using voice, and all importantly the distance from your agent to them.
With the new avatar lag tool within the release candidate I am guessing that you at Linden Labs are focusing on the lag that agents produce for Second Life as a whole. My suggestion does not make as much of a difference as some other major factors but as the saying goes, "save the pennies...".

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Dedric Mauriac added a comment - 17/Apr/09 10:18 AM
I would like to see a plug-in architecture for the client viewer that could solve this sort of problem. Sort of what we have with WoW and other online games. Opening the client up to 3rd party plug-ins would help reduce the need to run redundant methods on the server-side and make the whole experience very rich. Imagine if a company could have everyone install a plug-in that integrates with their existing tools behind a firewall.