same problems you had three years ago

I noticed that someone closed the "teleporting crashes" thread. It's probably being discussed in some other place without any sort of tip from the Lindens in the forum. Just like the last time I was on and left in frustration in early 2006.

Back then you'd crash half the time you teleported too. Textures were slow to load, SL ran weirdly slow on very, very fast hardware, and the lindens were entirely unresponsive to feedback.

Looks like not one single thing has changed.

Leaving in frustration again,


beatrix blackheart

(ps see ya in three more years, please get it together guys)

Wow, i come back a week later and now teleport doesn't work at ALL. I can't figure out how linden labs excuses this kind of incompetence. Or do they excuse it at all? Years ago they just never mentioned how craptacular things were. I've just hopped around the site and found exactly nothing at all about teleport problems.

How are these people still in business? It's got to be the porn.

I have no problems with teleports... perhaps you should post your specs and see if anyone has some ideas to help you, if you looked past your negativity you may realise that it's a problem your end.

(although having said that Sundays have been notoriously bad for months).

I've talked to half a dozen people all over the place this morning, and they're all having the same teleport problems.

Specs:

Quad core nehalem w/4 gigs RAM, nvidia Quadro GTX 250 (2x SLI), copper gig-E to an Apple router, to cable modem, 2mbps up, 128kbps down, less than 10ms away from anything that talks directly to Cogent, Telia or Sprint's NYC hub, and a quick look at general internet activity shows no black holes, weird latencies or any other oddness between me and the portions of the grid that I'm attempting to connect to. I'm running the latest client release beta, on Ubuntu Linux.


Thoughts?

EDIT: found the problem, and of course no one had any thoughts. It's because my avatar was loaded with scripted prims, each of which needs to be saved in-state (god only knows why, its utterly unnecessary) before teleport. Since there are so many, and the save took so long each time, the timeout threshold was met and the teleport failed each time.

There are so many things wrong with this that I'm not even going to start. I'm just going to go back to Eve, where someone, somewhere has a pretty good idea of how to do a modern MMO.

Baibai

Please... stay with Eve.. she needs you..

Sorry if the content of my post was a little beyond you. All you had to do was say you didnt have any ideas.

I'm glad you found the problem, Beatrix.

Please note that this isn't a problem with SL...it's a case of poor product design. A lot of us are complaining about overuse of scripts in prims, primarily for resizing.

Why does this happen? Because the makers are tired of having their designs ripped off, and this is one way to make them No Copy, but still adjustable by the user. It's not a perfect solution, though, it's a clumsy workaround.

LL is about to do something about it. In their usual backwards fashion. There are now plans in the works to limit script use, in the same way that land only supports a certain limited number of prims.

What LL *should* be doing is strengthening the permissions system and copy protection, not imposing resource limits. Attack the root of the problem, not the symptom.

But that's just me, ranting. What YOU should do is just get yourself some hair or jewelry that doesn't have those laggy scripts in it. Problem solved.

No. What I want is for linden labs to fix it so that every single state change in any object ever isn't immediately inserted into a huge, broken, slow MYSQL database.

Pretty elementary there. You're looking at it from inside the world of Second Life, and I'm looking at it from inside the world of system engineering. They've done an atrocious job with the latter, and there's no way to fix it at this point beyond completely trashing it and starting over again.

Which of course won't happen, not that it even should. Second Life is doomed to a mediocre existence, and its because of the incompetence and short sightedness of the engineers who designed it.

SL works great for me. But then I dont wear scripted stuff hardly at all. Maybe Im a princess of mediocrity or I just like eating apples so I paying for my sins or something.

I'm currently running SL on a Windows PC with a 1.6 Ghz Duron, 512 Mb RAM and a 128 Gfx card. In a fair number of sims, I can have my draw distance up to 512, with plenty of extras and Teleports are no issue, even when wearing script intensive gear. Therefore, I can only fathom that it is your OS that is causing the problem, not SL, and either that, or it's whatever you're wearing, more likely your OS, as Linux derivatives aren't the most stable platforms to run SL from. My guess is that your networking operations within the OS are sub standard or perhaps faulty/incomplete. Another possible is your connection setup. You may be close to a central hub, but what concerns me is that you have a 2meg upload and only 128Kb download, conversely, for example, I have around 3 Meg upload and an average of 600-800Kbs down. Possibly look at a service change/upgrade there.
My last issue is that you say "State Change" which implies that you have many prims containing many scripts that contain many states. This is not good. It's better to use variables so that you can make a script do numerous things depending on some defined values from a single state, rather than have SL change dozens or possibly hundreds of states each time you zip between sims. Just a collection of thoughts there, hope some of them may be useful and do correct me if I got anything wrong ^^