Page 5 of 8

Posted: Wed Jan 17, 2007 8:52 pm
by Cortex
Jonan wrote:QUOTE (Jonan @ Jan 17 2007, 09:58 AM) Although I'm new, etc, isn't *ping* more or less equal to seconds from last refresh from server? When it is growing there is only client side state and no fresh reference to server state, meaning he's flying in alternate universe for over a minute at a time. Unlikely playable.
That's what every other game says, but as you might already have noticed, Allegiance is different from other games. /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />


-- Cort

Posted: Wed Jan 17, 2007 9:11 pm
by madpeople
yeah, we call latency (ping), lag
and ping, sync

Posted: Wed Jan 17, 2007 9:49 pm
by Cortex
madpeople wrote:QUOTE (madpeople @ Jan 17 2007, 10:11 PM) yeah, we call latency (ping), lag
and ping, sync
Many use 'ping' as a synonym for (Alleg's) 'lag' value, though. /mrgreen.gif" style="vertical-align:middle" emoid=":D" border="0" alt="mrgreen.gif" /> Case in point, some posts in this thread.


-- Cort

Posted: Wed Jan 17, 2007 10:20 pm
by Bunnywabbit
Cortex wrote:QUOTE (Cortex @ Jan 17 2007, 10:49 PM) Many use 'ping' as a synonym for (Alleg's) 'lag' value, though. /mrgreen.gif" style="vertical-align:middle" emoid=":D" border="0" alt="mrgreen.gif" />
-- Cort

... and manage to confuse the living daylights out me.

Posted: Wed Jan 17, 2007 11:08 pm
by strike700
QUOTE C:\Documents and Settings\Administrator>tracert 84.243.253.94

Tracing route to 84.243.253.94 over a maximum of 30 hops

1 12 ms 12 ms 11 ms cable3-1.sweetwaterhsa.com [65.113.234.1]2 15 ms 11 ms 18 ms 65.121.101.225
3 18 ms 20 ms 24 ms chy-edge-01.inet.qwest.net [65.121.98.49]
4 19 ms 19 ms 18 ms chy-core-02.inet.qwest.net [205.171.158.37]
5 24 ms 31 ms 26 ms dvr-core-02.inet.qwest.net [205.171.8.138]
6 48 ms 44 ms 66 ms svl-core-02.inet.qwest.net [67.14.12.10]
7 47 ms 51 ms 44 ms pax-brdr-02.inet.qwest.net [205.171.205.30]
8 49 ms 49 ms 53 ms if-1-1.core3.PDI-PaloAlto.Teleglobe.net [207.45.
213.133]
9 48 ms 51 ms 68 ms if-1-1.mcore4.PDI-PaloAlto.Teleglobe.net [207.45
.196.78]
10 105 ms 95 ms 99 ms if-4-0.mcore4.NQT-NewYork.teleglobe.net [216.6.8
6.14]
11 173 ms 170 ms 174 ms if-3-0.core2.PG1-Paris.teleglobe.net [216.6.87.2
6]
12 183 ms 181 ms 176 ms 195.219.228.25
13 176 ms 181 ms 177 ms 195.219.228.2
14 186 ms 180 ms 182 ms if-6-0.core2.AD1-Amsterdam.teleglobe.net [80.231
.81.9]
15 191 ms 179 ms 179 ms Vlan3.msfc1.AD1-Amsterdam.teleglobe.net [80.231.
82.171]
16 177 ms 183 ms 190 ms Vlan856.msfc1.AD1-Amsterdam.teleglobe.net [80.23
1.82.62]
17 181 ms 184 ms 187 ms rtr-1.rtd-kub.grafix.nl [217.67.247.5]
18 186 ms 184 ms 187 ms 84.243.253.94

Trace complete.

C:\Documents and Settings\Administrator>[/quote]

I get a higher lag but otherwise see no difference when playing on the EU servers. Not even during the Multisquad game of 50+ people.

Posted: Wed Jan 17, 2007 11:31 pm
by mcwarren4


PS - how do you copy/paste the data from the command prompt so I don't have to take a screenshot? And what do all of those numbers mean anyway?

Posted: Wed Jan 17, 2007 11:35 pm
by strike700
Right-Click->Selectall->"Ctrl-C" then paste it into the the post window. *Note* you can't use "right click->Copy" because it deselects the text.

Posted: Wed Jan 17, 2007 11:46 pm
by Anguirel
My guess is that packets are bunching up and being set in larger bursts. Cross-ocean pipes are like that. It will lead to reasonable average pings but unpredictable effects in game, especially when packets arrive out of order (and as you get further from a given server, that becomes more likely - for more, see ImmZ and the amazing retarded global routers).

Posted: Thu Jan 18, 2007 2:06 am
by Clay_Pigeon
Because I want to belong

Code: Select all

Silence:~ troy$ traceroute -I -m 255 84.243.253.94
traceroute to 84.243.253.94 (84.243.253.94), 255 hops max, 60 byte packets
 1  192.168.0.1 (192.168.0.1)  0.957 ms  0.701 ms  0.268 ms
 2  10.71.96.1 (10.71.96.1)  8.211 ms  7.772 ms  12.157 ms
 3  gig2-2.akrnoh2-ybr2.neo.rr.com (24.164.103.54)  8.077 ms  8.352 ms  11.926 ms
 4  srp12-1.ncntoh1-rtr2.neo.rr.com (24.164.101.37)  148.310 ms  203.196 ms  199.463 ms
 5  son2-1-1.mtgmoh1-rtr0.columbus.rr.com (65.25.128.249)  20.017 ms  22.687 ms  21.375 ms
 6  te-3-1.car1.cincinnati1.level3.net (4.78.216.9)  23.257 ms  24.595 ms te-3-2.car1.cincinnati1.level3.net (4.78.216.13)  21.453 ms
 7  * ae-5-5.ebr2.chicago1.level3.net (4.69.132.206)  31.462 ms *
 8  * * ae-1-100.ebr1.chicago1.level3.net (4.69.132.41)  35.170 ms
 9  * ae-2.ebr2.newyork1.level3.net (4.69.132.66)  56.507 ms  52.359 ms
10  ae-22-54.car2.newyork1.level3.net (4.68.97.117)  57.187 ms  64.211 ms  52.448 ms
11  interoute-c.car2.newyork1.level3.net (4.78.166.254)  50.893 ms  57.258 ms  69.446 ms
12  po5-0.nyc-002-inter-1.interoute.net (212.23.43.129)  139.310 ms  128.629 ms  128.410 ms
13  po3-0.lon-wal-core-2.interoute.net (212.23.43.150)  125.795 ms  145.044 ms  124.524 ms
14  po5-0.lon-wal-core-1.interoute.net (84.233.152.161)  118.392 ms  118.474 ms  119.712 ms
15  po1-2.rtm-vla-access-1.interoute.net (212.23.41.205)  122.767 ms  122.682 ms  124.081 ms
16  217.118.121.134 (217.118.121.134)  123.994 ms  123.202 ms  122.935 ms
17  84.243.253.94 (84.243.253.94)  135.989 ms  126.767 ms  126.722 ms

Posted: Thu Jan 18, 2007 4:52 am
by ImmortalZ
My experience is on-average much smoother on the EU server than when playing on the US servers. But when it decides to screw up, I can't play at all.

@madpeople.

Code: Select all

ping <ip> > filename.txt
The file will have the ping output. There won't be anything on the console as the output is piped to the file.