Getting really pee'd off with this.

Only been here for a few days & I'm ready to scrap this & leave.

Nothing's working as it should. I go to walk & either it doesn't, (my av just stands still), or when it does walk, I can't control it. If I try to turn while walking, more often than not, it will not just turn, but spin around & start walking backwards, other times it will not turn at all. When I release the arrow key to stop walking more often than not my av will continue on. Usually keeps going until it hits an unmoveable object that stops it.

It's walked into the sea or off a bridge/structure or bumped into other avs etc so many times it's not funny. Pressing the arrow key to walk backwards to stop the avs forward motion does nothing.

Then other times, it will start walking off by itself without any input from me. I've just got no idea wtf is going on. It's done this since day 1.

Flying is hit & miss too. Sometimes won't go up, or stop going up, come down or stop coming down until the av is underground/water. Same as walking when trying to go forwards or turn when flying.

I'm in Australia if you think it could be a lag problem, but I'm telling you, it's no fun at all.

If it's any use to you my computer specs are...

2.4GHz Celeron.
512 Meg Ram.
80 Gig HDD. About 9 gig used. So plenty of free space.
128meg ATI 9200SE graphics card with latest drivers installed.
Win XP Pro SP2.
256/64 ADSL Broadband connection.

Andrew

There's your problem

Sooo, more money to spend on the puter. That'd be right.

Thanks for your answer though, I appreciate it. Just out of curiosity, why is the Celeron a problem?

I'm just messin with ya! I have personally had "blah" experiences with Celerons and will never buy a compiyer with a Celeron in it ever again.

But it sounds like a lag problem. Do you have other stuff running in the background? If so, close everything and try it again. There's also some helpful threads on fixing and dealing with lag. I'll try and find them for you.

Read this:
/111/1f/106305/1.html
Hope that helps

Ok thanks. No nothing else running, just SL.

I've got 2 puters with Celerons. This one & my other one with a 400MHz Celeron. Neither have ever given me grief with anything before. Might see if I can get a cheap 1.7 or 1.8GHz Pent4 & see how that goes.

Again, I really appreciate your help.

Don't! As MadamG said, she's just messing with you. That processor is fine for SL. Actually, all the things you mention are classic lag symptoms, and this sounds like the most likely cause:

**256/64 ADSL Broadband connection.**

I'm not certain (maybe somebody else will confirm this) but I do believe that Second Life really requires a 512kbps downstream connection. If you look in preferences > network, you should even see that "maximum bandwidth" is set to 512 by default. You could try reducing that to 256kbps, but I've got a feeling it won't help much because it's just too slow. You might also ensure the music and video streams are constantly disabled too.

If you're looking at performance issues, your graphics card is less than ideal, and you have way too little RAM, too.

But I'd go with the broadband being the problem here - it does sound more like you are seeing comms lag rather than just slow framerates.

Before you go upgrading your system, I'd suggest turning down your preferences and seeing what happens. It may be a connection issue. With the last update, things have slowed down noticeably - and since I have a 256K ADSL (unlike most people on these forums, it seems), the update has triggered all sorts of weirdness which partly seems to be connection lag.

Other things to troubleshoot are packet loss issues, etc. I've had problems with DNS, and have used open DNS servers to bypass that problem. When you're lagging really bad, pull up the command prompt and do a tracert to secondlife.com.

What the Celeron answer is about is that Celeron's can handle word processing really well, but this is 3D graphics - something Celerons are not so good at. It would be a good idea to upgrade the processor/motherboard, but don't go running off with your hard earned cash before verifying that this will solve your problem. If you have the money to toss at it, go for it... but if you're close to red or in the red, check things out first.

Thanks guys. I'll try what's suggested that doesn't cost me money.

I'm not likely to throw money at it Nobody Fugazi, as I'm only on a disability pension, so can't afford to do that.

Here's the tracert result I got. Not sure what it all means, but I don't think all the "Request timed out" lines can be good. Am I right here?
Can anyone please explain it to me.

Tracing route to secondlife.com [66.150.244.125]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms BigPond.bigpond [10.0.0.138]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * 4315 ms 3091 ms border1.ge2-1-bbnet2.sfo002.pnap.net [63.251.63.
65]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 3942 ms 2990 ms 2560 ms web2.lindenlab.com [66.150.244.125]

Trace complete.

Could you download WinMTR from http://winmtr.sourceforge.net/ and use that as a traceroute program - it gives a lot more detail, and allows for slower packet replies to still be responses

I _think_ looking at the timestamps that are in there, that the droppage was due to slowness, not loss, but even so, the times are really bad - really really bad.

Also, was that run while you were running SL, or not?

Finally, while you are in SL, if you click on Help-->About Second Life, then the packet loss stats for the current session will be listed there. Could you let us know what the percentage is?

Yes Bitzer, it was while I was running SL.

I'll get back to you soon about the WinMTR results & packet loss stats percentage.

Cheers mate.

Bitzer

The packets lost thingo read... 0/1079 (0.0%)


This came out a bit all over the place but you should be able to make it out.


|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| BigPond.bigpond - 0 | 103 | 103 | 0 | 204 | 1682 | 10 |
| 172.18.112.43 - 0 | 103 | 103 | 40 | 1422 | 8042 | 110 |
| 172.18.66.30 - 0 | 103 | 103 | 40 | 1465 | 8132 | 110 |
| cht-core-1.nsw.bigpond.net.au - 0 | 103 | 103 | 40 | 1444 | 8212 | 90 |
|TenGigabitEthernet4-1.chw44.Sydney.telstra.net - 0 | 103 | 103 | 30 | 1444 | 8242 | 90 |
|TenGigE0-1-0-0.chw-core2.Sydney.telstra.net - 9 | 103 | 94 | 30 | 1441 | 8833 | 100 |
|10GigabitEthernet1-0.oxf-core1.Sydney.telstra.net - 0 | 103 | 103 | 40 | 1460 | 7431 | 61 |
|10GigabitEthernet2-2.syd-core03.Sydney.net.reach.com - 0 | 103 | 103 | 40 | 1452 | 7821 | 50 |
| i-6-0.syd-core01.net.reach.com - 1 | 103 | 102 | 40 | 1456 | 7371 | 50 |
| i-3-0.wil-core03.net.reach.com - 0 | 102 | 102 | 180 | 1575 | 7541 | 221 |
| i-3-4.wil03.net.reach.com - 0 | 102 | 102 | 180 | 1634 | 7431 | 181 |
| ge-6-21.car3.LosAngeles1.Level3.net - 0 | 102 | 102 | 180 | 1652 | 7500 | 190 |
| ae-2-52.bbr2.LosAngeles1.Level3.net - 0 | 102 | 102 | 180 | 1601 | 7190 | 230 |
| so-3-0-0.mp1.SanFrancisco1.Level3.net - 0 | 102 | 102 | 200 | 1620 | 7000 | 210 |
| ge-7-0-0.gar1.SanFrancisco1.Level3.net - 0 | 102 | 102 | 200 | 1640 | 6920 | 200 |
| 4.78.242.18 - 0 | 102 | 102 | 200 | 1642 | 6960 | 200 |
| border1.ge2-1-bbnet2.sfo002.pnap.net - 0 | 102 | 102 | 200 | 1632 | 7130 | 241 |
| web2.lindenlab.com - 0 | 102 | 102 | 190 | 1606 | 6880 | 211 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( [email]stanimir@cr.nivis.com[/email] )

OK, looking at those stats, either the traceroute was partly with SL and partly without it, or you have a really strange internet connection.

To summarise the data
-----------------------------Average time...worst time
first hop......................... 204................1682
second hop....................1422................8042
Far side of your isp.........1444................8212
To America....................1575................7541
To Linden Labs...............1606................6880

worst pacet times are not very useful statistically, but they are indicative.

Basically, it looks like you have a failry slow link to the net, which is then further throttled (or congested) as the first stage in your ISP (?)

Of the 1.6 seconds (average time for a ping to LL), 1.4 seconds of that is there by the second hop. the other 200ms is pretty reasonable for an Australia to USA link, so your ISP is pretty well connected, they just aren't letting your packets out (very fast).

Likewise, on the worst case stats, the second hop (your ISP's throttling router from the look of it) can take 1.2 seconds LONGER to reply (worst case) than LL, so you really are looking that all the network delays are happening at your end.

Thanks for the in game stats, although 1079 packes must make it pretty much the first thing you did inworld


However, given that it can take up to 6 seconds for a packet to get from you to LL and back, you are GOING to see at least that order of lag on everything you do.


My advice, forget hardware upgrades, nothing in your stated spec is going to make a damn of difference when your connection is this slow. You need to upgrade your broadband.

Bitzer. Thanks heaps for that mate. Thinking about it, that 6 seconds you mentioned does seem about the amount of time that my commands transfer to my av.

Yeah, my connection, even just browsing the net, is slow a lot of times, & I'm almost nearly the furtherest connection from the phone exchange. It's the price I pay for living in a very small country town in the middle of nowhere, 100's of kms from the nearest capital city. Country people over here really get a rough deal on the net.

No problems trace route results can be tough to read without experience....


Even so..... there is something going on between the first and second hop that is adding a huge latency. Hundreds of kms from the city wouldn't do it, unless you have everyone on the same exchange as you sharing one underspecced intenet pipe.

It looks like the ISP is throttling the access there, either due to lack of bandwidth, or some strange clause in your access agreement. It may be worth talking to their technical department (especially if it is a smaller ISP) and seeing if they can do anything to boost or optimise your throughput, maybe on some other account package - can't do any harm to ask.

haha, mate they are the biggest provider in the country. Bigpond is a division of Telstra who are the main telephone provider here. They own all the phone lines & so have a monolopy.

Anyway, I turned a couple of things down in the preferences, set the max bandwidth to 240 kbps, set the terrain detail to low & the draw distance to 64 meters which at least is making it work better.

Thanks again for your help, & hope to see you inworld sometime.

Cheers mate.

You should find that you can get it to work well enough with mid-range settings ofr detail - your PC spec isn't _that_ bad. It will take a while to rez, but if you keep your bandwidth setting down below what your line is capable of, then you shouldn't get too much loss, or queueing (which massively raises latency), so the lag shouldn't get too oppressive.

Best of luck, anyway

The original poster's problem isn't Celeron. I have a Pentium and double his RAM and having the same problems after this latest update. Didn't have them before. Card is ATI Radeon 9800 Pro which runs some of the most graphics intensive games out there, smoothly. I'm on DSL.

The game is very laggy now. Give them some time to see what's causing the lag and to get rid of it, then I think we'll be able to manipulate our avs and get things to work for us again.