The five most HORRID glitches in SL.

I'm making this thread because I want the Lindens to see what we testers believe are the WORST bugs and glitches in Second Life. These next five are mostly personal, and I want everyone who agrees with my ranking to reply. If you don't agree, please reply saying which bug you think is THE worst. I don't want this thread to be a catch all, I want it to be a catch worst.

1: Contents Loading bug. I am now inflicted by this bug!! Although it only happened during off-hours, I could not shake it off, and it was seriously even more annoying than the Listen bug. Inside sources tell me the listen bug is squashed soon, so I'm moving this one straight to the top. Please, I need my contents to load!

2: llListen() working incorrectly. You already know about this bug, please fix it as soon as possible. It debilitates the majority of scripts that are in world, thus needs to be fixed as soon as possible.
Update: Inside sources say this will be fixed soon, but I'm leaving it in this position.

3: Objects are misplaced once loaded to the client. You know about this bug too. As far as I'm concerned, we've lived with it for too long. Whether it be spawning in a new area, or just moving around the world, having to click on objects to get their correct position is getting old and sickening. It makes good looking things look bad. I know that as of late it hasn't hit as hard as it used to, but it's still there, and we want it gone.

4: The ghost of deleted objects bug. Another old one that's extremely annoying. Where's our "refresh button" guys?

5: Group edit bug. A non-personal bug, because I don't do much group editing at the moment (until CyberCity is allowed to expand) is the group edit bug. I know the Lindens have already replied that they know of this bug, and I'm officially putting it in the top five.

I'm pretty sure you Lindens also want these bugs fixed, but I know how you have priorities for things, and I'm simply trying to tell you what I feel should be on the top rungs. To anybody else, like I said before, please reply if you agree, and if you want to re-rank, or add one or two, feel free. I just don't want this to be a catch-all.

To any Lindens who respond, thank you for your time in reading this.

~Dave Zeeman

Edited again: Now reflects updated information.

Move #2 to the top. I have some really cool ideas for my Arcade (players club to reward people who play alot as well as jackpots that go up when people play other games and more) that I simply can not do unless llListen() is reliable.

My top 5 would be (in order):

#2

- Scripts that can break physics in a sim

#5

#1

#3

#4
#5
#3
#2
#1


4 is by far the most annoying, especially when you have to relog in order to continue building when your "ghosts" are in the way for building to continue....


also just as annoying but not sure if it should make the list...is not being able to manipulate objects across sim lines.

Like if your build spans a sim line you have to run/fly across the line in order to do certain things to the objects in the opposite sim, not to mention falling through objects that cross sim lines.

Dave, if you do any large quantity of group object editing, you would place the group edit bug WELL above some of those others. The inability to edit objects made by someone else in your group forcing them to leave and rejoin the group to clear it (and sometimes even THAT doesn't work) or trying to "chat" them through the changes you want to make is beyond painful.

Also, not being able to edit textures of someone else's group projects is mildly frustrating as well (also part of the group bug, so I am told).

That being said, your bug #3 affects me A LOT! Practically all of my house suffers from this one. And it's frustrating to maintain by constantly clicking. "Object Sag" should not be an issue!

My $0.02.

i believe andrew has actually made a post about the object shifting bug somewhere... he mentioned something about compression and/or losing precision or something... look for it

#2
#5

But, have to agree with Zanlew, the group bug for me is the most annoying. I have to leave the group several times a night for him to readd me just to fix this problem. Worse thing, is if I am not online then he has to wait till I return to continue working on a project we are doing together.

#1 is a driver issue. I had the same problem until I read the Knowledge Base.

The fix

I updated my SoundBlaster Live! Value card's drivers, and sound's been flawless since.

The problem with soundblaster drivers is that they mess up my system much more than the 3rd party ones I'm using right now...

*sigh* maybe they've been updated so they work now I guess I'll go try.... *whimper*

edit: it worked! hehe the list is now edited

*bump* updated the list, please reply with your thoughts and opinions (the more replies this gets, the quicker the worst bugs are fixed!)

I would swap 4 and 5 myself personally. While 4 is really annoying, it's not debilitating. You can get around it. With 5 you're stuck. Not only are you stuck at that point in time, but if that person in your group is not on, you are dead in the water until such a time as you are both on again. Actually, using that logic I would swap 3 and 5 for a 1,2,5,3,4 deal.

Sigh. As I've described in a thread elsewhere in "Technical Issues," the driver from the Creative website doesn't work for me. Creative told me they don't support OEM-installed SoundBlasters, and Dell doesn't have any updated drivers. I had hoped that, if the sound bug remained on Dave's list, it might get some further attention from the Lindens.

Sorry Jake. Although this list is mostly a personal collection of what I believe are the worst bugs for me, I don't think the Lindens will specifically focus on every thing that I need I'm sure in reading this thread (and your OEM thread) that they will find priority for the bug.

I think I've finally gotten some useful information about my sound card problem. Looks like it's not something the Lindens can fix, so I won't mention it further on this thread. See my other thread for more information.

No Linden has responded to this thread so far--probably because no one wants to create unrealistic expectations. But I thought you should know that this thread has been widely read and discussed here at Linden Lab.

We reshuffle our bug priorty list pretty frequently to keep the most important issues on top. Your feedback is really valuable. Keep it coming!

Thanks!
Aaron