UO Second Age

From a DOS prompt if I "ping -t uosecondage.com" I consistently see between 38 and 42. In game however, my average is always in the 120-140 range. Should they be different? If not, are they any suggestion of how I can fix the issue. I'm always lagging in game.

If this helps:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 6 ms 7 ms XXXXXXXXXX
3 9 ms 6 ms 9 ms XXXXXXXXXX
4 7 ms 9 ms 9 ms te-8-2-ur02.lakeworth.fl.pompano.comcast.net [68.86.165.178]
5 7 ms 7 ms 8 ms te-9-1-ur02.staterd7.fl.pompano.comcast.net [68.86.165.101]
6 8 ms 7 ms 9 ms te-9-4-ur01.staterd7.fl.pompano.comcast.net [68.86.165.93]
7 11 ms 9 ms 9 ms te-0-12-0-4-ar03.northdade.fl.pompano.comcast.net [68.86.165.82]
8 11 ms 11 ms 9 ms pos-0-5-0-0-cr01.miami.fl.ibone.comcast.net [68.86.91.81]
9 9 ms 11 ms 10 ms xe-10-1-0.edge2.Miami1.Level3.net [64.156.8.9]
10 18 ms 18 ms 16 ms ae-32-52.ebr2.Miami1.Level3.net [4.69.138.126]
11 25 ms 36 ms 36 ms ae-2.ebr2.Atlanta2.Level3.net [4.69.140.142]
12 26 ms 36 ms 35 ms ae-73-70.ebr3.Atlanta2.Level3.net [4.69.138.20]
13 43 ms 37 ms 37 ms ae-2.ebr1.Washington1.Level3.net [4.69.132.86]
14 42 ms 36 ms 37 ms ae-71-71.csw2.Washington1.Level3.net [4.69.134.134]
15 40 ms 39 ms 40 ms ae-2-79.edge2.Washington3.Level3.net [4.68.17.76]
16 114 ms 199 ms 172 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.234.6]
17 * * * Request timed out.
18 * * * Request timed out.
19 38 ms 46 ms 39 ms mx.alienseed.com [64.34.163.237]

-----


Pinging uosecondage.com [64.34.163.237] with 32 bytes of data:

Reply from 64.34.163.237: bytes=32 time=40ms TTL=107
Reply from 64.34.163.237: bytes=32 time=39ms TTL=107
Reply from 64.34.163.237: bytes=32 time=41ms TTL=107
Reply from 64.34.163.237: bytes=32 time=38ms TTL=107
Reply from 64.34.163.237: bytes=32 time=40ms TTL=107
Reply from 64.34.163.237: bytes=32 time=40ms TTL=107
Reply from 64.34.163.237: bytes=32 time=40ms TTL=107
Reply from 64.34.163.237: bytes=32 time=40ms TTL=107
Reply from 64.34.163.237: bytes=32 time=41ms TTL=107
Reply from 64.34.163.237: bytes=32 time=40ms TTL=107
Reply from 64.34.163.237: bytes=32 time=40ms TTL=107

Ping statistics for 64.34.163.237:
Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 41ms, Average = 39ms

The difference between the ingame ping and the commandline ping is razor and client overhead. You may get better results by fiddling with the video option in the client, or possibly adjusting your MTU to 576 (I've heard this has good results, google to find out how to do this)

Thanks, I'll work with the video settings.

I had actually already changed the MTU settings before that post (I saw the information from another post).

Just an update on this...the only setting that seems to have a major effect is "Use full screen display". The problem with that is it's very cumbersome to access Razor, and I lose a lot of Razor's features such as the title bar. Also when I tried to login a second account (to buy a horse for my red) the second client just froze up.

When I ask a player who PvP's well, I inevitably get an answer below 50. When I ask players from now on, be more specific about asking for ingame pings, but do you think these players are referring to the command prompt pings? Do they perhaps have command line pings in the low 20s and their ingame, non-full-screen-display "double up" ping is the one they are quoting me that is below 50? Or are they ALL running in full screen display (I would be surprised that they would handicap Razor)?

My computer is only 2-3 years old and I have GEForce 6200 which I would imagine is plenty of power for UO. I guess if I knew that I just got an unlucky draw of the cards because of my location, and my ping (or # of hops or whatever) is just not that great, I could accept that and not pursue any more time in finding a solution. If it's buying a new graphics card, or just grinning and bearing until I upgrade my computer, I could also live with that.

On the second client freeze up, be sure you have UnChecked "Use Smart CPU Reduction" in Razor

Any ping under 100 should be incredible. Theoretically, you shouldn't notice any movement lag under 200

Thanks for the reply, Derrik. I feel much better now.