Well after taking some time out from Second Life, for several reasons, mainly being burnout prevention. I have decided that burnout is now prevented. To my horror however the lag issues that Second Life has been experiencing have not changed (lag was another reason for timeout). So, me being me, I have decided to hopefully do something to help matters. I don’t see the point of just sitting back and complaining, I would rather put that energy into comming up with solutions. I don’t have the skills to be able to edit the Client to implement my suggestion but I can and do think about things like this alot.
So my suggestion, rather than moan about the awful FPS we get, try think of things you can do to help with the situation. We all have Agents within the world and we all contribute to that lag.
To that end I had an idea while I was looking into what on my agent created a large ammount of lag, (unfortunatly my dreads by the look of it) and I had a thought as to one thing that pretty much most agents use. I myself have reccommended people get a multigadget and then more recently the MystiTools Hud, just because I find them so useful myself. However, considering that most people have one of those two or something similar, it would seem a good thing to have a look at reducing the effects they create within Second Life. It doesn’t matter how well either of those devices or similar are coded they are creating lag within Second Life. I put in a lot of effort making my sim so that I only have one sensor in it and numerous other measures to try reduce the server load. However I run events there, and the instant another agent comes into the sim that instantly introduces another (at least) sensor.
Don’t get me wrong, I loved my Mg and I love my Mysti, (and I am not going to stop using my Mysti until something like what I am suggestin is put into place) But both of these devices are putting extra strain on the servers to provide users with extraneous information.
When I say “Extraneous” by that I mean it’s information that the servers are already telling the clients computer, both for (I am guessing but would seem logical) for purposes of rendering the world for the agent, and for the Ventrillo Voice chat. Both of them need to know distances between avatars. Which is basically exactly what the sensor devices are doing. The sensor devices seem to be running a sensor loop for all local agents every second (which is quite a strain on the servers).
So, what is becoming a long story quite rapidly shorter, go check out this link, vote and tell your friends.
07/05/2008 at 7:12 pm Permalink
T - I found the same thing with my avatar. Much to my shock I scores over 1300 - over 1000 of it being my hair and 153 for my multi - so I got new 300 score hair and will only use my multi in non-event sims.
08/05/2008 at 8:01 pm Permalink
something interesting that i’m not sure many people knew about… the original first incarnation of the sl with voice RC HAD avatar detection!
that little box that shows you when people are chatting on voice used to actually show you how far away the person was (not with numbers but you could tell if they were in chat range) it also showed if they were typing or not which is something i love my radar for because when you are role playing you don’t want to type over someone, and if they have an ao that hides their typing animation it’s hard to know if they are responding or not. but when they finished testing and released voice features they omitted those from that box.
now it will show you who’s chatting on voice, but not the rest. that could have been a great fix but they seemed to have decided it wasn’t needed. so the ability is there for them to install this sort of thing that you are proposing, and hopefully with your jira maybe we can persuade them to do that.
14/05/2008 at 5:59 pm Permalink
Semi-relevant LOLgreenie