Unable to move

OK, new bug.

Today when I logged I was hardly able to move my avatar.
When it did move it started to run towards lower and lower co-ordinates, so I thought it must be on its way to 0,0,0... Not so! It keeps on running into negative co-ordinates now.

Anyone else experiencing this?

Am I really the only one with this problem?

What you’re describing is not a bug, but a feature called LAG…lol.
Sorry…
I would say we need more information. Are you logging into a busy, crowded or overly primed location ie a welcome area? Have you tried clearing your cache?

I have cleared my cache now and the results are fantastic. I am now flying in the direction of positive co-ordinates. Again unable to stop this motion of course.
If this were lag, the system would have to sssssssssssssslllllllllloooooooooooowwwwwwwwwwwwlllllllllyyyyyyyyyy respond to my keystrokes in some way, but it does not.

I am still flying in positive Y-direction at about 4 m/s.
Maybe I should just let it fly until it reaches a numeric overflow.
That may give the lindens a crash log to get their teeth into

Got the same problem here since this morning. I'm in Europe (Holland).

Whenever I login I can move and use IM for a short period of time. After that, the client seems to lose the connection to the server and I can't move anymore. Also, IM stops working. And when I was moving I just keeping moving endlessly.

Help please!

Ok, I turned on debug logging and as soon as things go wrong I get this line repeated over and over:

2007-04-17T22:03:15Z WARNING: sendMessage - Trying to send AgentUpdate on unknown circuit 72.5.13.96:13006

I don't know how to switch on debug logging, but I have the exact same symptoms.
And interestingly enough, I also live in Holland.
Maybe LL has given up on our country, it had to happen sooner or later

Some more info from the debug log. This is how it looks when the problem starts:

2007-04-17T22:01:11Z WARNING: LLCircuitData::checkCircuitTimeout for 72.5.13.96:13006 last ping 103.311 seconds ago.
2007-04-17T22:01:11Z WARNING: LLCircuitData::checkCircuitTimeout for 72.5.13.96:13006 still dead, dropping.
2007-04-17T22:01:11Z INFO: LLCircuit::removeCircuitData for 72.5.13.96:13006
2007-04-17T22:01:11Z WARNING: LLMessageSystem::checkMessages: Packet from invalid circuit 72.5.13.96:13006
2007-04-17T22:01:11Z WARNING: sendMessage - Trying to send AgentUpdate on unknown circuit 72.5.13.96:13006
2007-04-17T22:01:11Z WARNING: sendMessage - Trying to send AgentUpdate on unknown circuit 72.5.13.96:13006
2007-04-17T22:01:11Z WARNING: sendMessage - Trying to send AgentUpdate on unknown circuit 72.5.13.96:13006
2007-04-17T22:01:11Z WARNING: LLMessageSystem::checkMessages: Packet from invalid circuit 72.5.13.96:13006
2007-04-17T22:01:11Z WARNING: sendMessage - Trying to send RequestImage on unknown circuit 72.5.13.96:13006
2007-04-17T22:01:11Z WARNING: sendMessage - Trying to send AgentUpdate on unknown circuit 72.5.13.96:13006
2007-04-17T22:01:11Z WARNING: LLMessageSystem::checkMessages: Packet from invalid circuit 72.5.13.96:13006
2007-04-17T22:01:11Z WARNING: LLMessageSystem::checkMessages: Packet from invalid circuit 72.5.13.96:13006
2007-04-17T22:01:11Z WARNING: LLMessageSystem::checkMessages: Packet from invalid circuit 72.5.13.96:13006
2007-04-17T22:01:11Z WARNING: sendMessage - Trying to send AgentUpdate on unknown circuit 72.5.13.96:13006

Looks like a timeout occurs to one of the SL servers and after that everything just stops working.

Debug logging can be turned on by hitting Ctrl-Alt-D and then selecting Client -> Consoles -> Debug Console from the menu.

Same issue here, also from Holland (Weert)

I am very happy to read that I'm not the only one, been tinkering so much today with this!

We wouldn't happen to all have the same provider: XS4All/KPN, would we???

Demon - But bought up by XS4All, moving over etc.

I'm having the same issue, and guess what: I'm also from Holland! And guess who my ISP is... That's right, it's Demon/XS4All! Yay!

LLMessageSystem::checkMessages: Packet from invalid circuit xxx.xxx.xxx.xxx

Means you got disconnected, or sim crashed, that isp doesnt have a rule against heavy apps like torrents and such?, SL is tagged heavy on isp load easy might be when it cuts you off.

OH NO !!!
Haven't checked today, but last night was a nightmare... And yes: xs4all

Xs4all here as well... hmm sounds like a pattern is emerging...

Just logged on to SL.. Problem still there. Disconnected after about 2-3 minutes

I got disconnected from sim1199.agni.lindenlab.com [72.5.13.95] this time.

Yesterday it was sim1200.agni.lindenlab.com [72.5.13.96].

Strange thing is, I can ping and tracert to these addressed just fine. Ping delay is about 160-170 ms.

I have contacted the XS4All helpdesk about this.
It may be a good idea if other people do the same.
In particular those of us who are able to explain them more about the technical details...

Must be XS4ALL....I'm currently in Holland too...no probs for me. My ISP is Versatel.

Mandy C

What did xs4all tell you ?

I am not sure it is xs4all anyway: I have problems with regions like plush and zarathud, but not tourmaline for example...

And yes, I lose the connections too! Sometimes and some places. For me it start to notice it yesterday (17th).

Maybe related. I have a constant ping to user time of 1000, but I do have that also in regions which seem ok.

You are right. Tourmaline Island does not seem to effect me either for some reason.

Hmmmm... Is the problem gone ?
Zarathud was a disaster yesterday, but I'm fine right there now.
Can anyone name a region with a problem ? (related to xs4all ?)

Sables dAlliez

SL is split between Texas and California.

/me wonders if the ISP is throttling connections to one but not the other. Help->About will tell you the DNS name of the sim that you're in and a tracert should give you a good idea of which state the server is in. Maybe people could post good/bad sims and which part of the US they're in.

Good sim:
Heloise located at sim2492.agni.lindenlab.com (64.129.41.242:13004)

Bad sim:
Opium Island located at sim306.agni.lindenlab.com (66.150.245.242:13006)

Although the problem is not present now... it is exactly as described earlier.
Normal connection for a while...and poof. Bandwith 0.0, and no walking typing anything.

For me the problem is over