+- Discovery Gaming Community (https://discoverygc.com/forums)
+-- Forum: Discovery General (https://discoverygc.com/forums/forumdisplay.php?fid=3)
+--- Forum: News and Announcements (https://discoverygc.com/forums/forumdisplay.php?fid=13)
+--- Thread: LAG (/showthread.php?tid=3508)
LAG - 13CentKiller - 12-18-2007
My PING averages 450 on a good day!
No lag for me...Im over in New Zealand with a 256kbps ADSL phone line connection and old router with an ISP thats on the other side of the country to me....
No lag for me :cool:
LAG - feron - 12-19-2007
Peronally, i have a latency of 120ms to the server, but everything works fluidly for me. Hell, i can even kill Xenos in Starflies easily. People that experience lag with low latencies should call their ISP and ask if they limit packets per second. Packets per second is what makes the difference, not latency. I suspect that many ISP's limit packets per seconds to reduce the load from torrent applications and VoIP. I too get yellow icon spikes sometimes, but thats only twice a day, and if i am fighting i notice no difference.
LAG - Jinx - 12-19-2007
well, 16mbit connection and an average ping of 80 here. - i get regular yellow/reds - but thats serverside, cause it only happens when the whole server is crashing.
other than that - i get occasional yellows in dogfights with 3 or more people - no lag when the people are just hanging around. most of the time, there is no lag though. lag has increased a bit recently, but i believe that is cause the general poppulation increased.
LAG - mjolnir - 12-19-2007
That is my case too...
I was playing for over 2 months with no lag ever (on 50ms ping)... and suddenly during the last week I frequently experience lag when fighting more than one ship (even with some 60 people on server).... don't think the ISP has changed so much in the meantime.
LAG - EarthPulse - 12-19-2007
It is deffinitly not an ISP problem.
It takes me over 10 minutes to kill 3 rogues atm because of all the weird movements they make.
So only trading for me at the moment.
Yesterday i traveled through 5 star systems and when i finally reach the target planet i lagged out. That was a bummer.
So i am gonna land on every planet now so that my game is saved.
I hope something is gonna improve soon.
LAG - Rogue63 - 12-19-2007
My average ping to server is about 180, but I live a good ways away from server (west coast US). Even when server running near capacity I hardly see any lag at all. The one thing I do notice is that the police npc's, especially Kusari seem to be abit squirrelly, with there 90 degree turns and manuevers. But I have seen this on other servers as well, so it is not this servers issue. About players who lag, well it happens, I say just deal with it. If you are fighting someone who is lagging, i.e. darting all over your screen, I'd say be polite and tell him/her "sorry but you are lagging from my perspective, maybe we can finsh this another time". My 1st online game was Mechwarrior on a 56k dial-up connection in mid/late 90's, most times there were players who's mechs seemed to be moon-walking, there were lagging players in every match, and I'm sure I was one of them at times. My connection is now is considerably better and lag is a thing of the past for me. It is just part of the online experience, not everyone has the best connection.
LAG - trekster - 12-19-2007
Heres my lag Report
Discovery RP Server 2:29 PM 12/19/2007
Pinging 82.113.48.5 with 32 bytes of data:
Reply from 82.113.48.5: bytes=32 time=128ms TTL=107
Reply from 82.113.48.5: bytes=32 time=129ms TTL=107
Reply from 82.113.48.5: bytes=32 time=128ms TTL=107
Reply from 82.113.48.5: bytes=32 time=128ms TTL=107
Ping statistics for 82.113.48.5:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 128ms, Maximum = 129ms, Average = 128ms
Discovery PVP Server 2:30 PM 12/19/2007
Pinging 81.106.177.58 with 32 bytes of data:
Reply from 81.106.177.58: bytes=32 time=105ms TTL=40
Reply from 81.106.177.58: bytes=32 time=101ms TTL=40
Reply from 81.106.177.58: bytes=32 time=108ms TTL=39
Reply from 81.106.177.58: bytes=32 time=110ms TTL=40
Ping statistics for 81.106.177.58:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 101ms, Maximum = 110ms, Average = 106ms
I added PVP for bulldog:cool:
LAG - Epholl - 12-19-2007
Your ping doesnt mean your lags.
Odpoveď od 82.113.48.5: bajty=32 čas=39 ms TTL=114
Čas požiadavky uplynul. <--This is a lag
Odpoveď od 82.113.48.5: bajty=32 čas=146 ms TTL=114 <-- This is a lag
Odpoveď od 82.113.48.5: bajty=32 čas=33 ms TTL=114
Odpoveď od 82.113.48.5: bajty=32 čas=171 ms TTL=114 <-- This is a lag
Odpoveď od 82.113.48.5: bajty=32 čas=38 ms TTL=114
Odpoveď od 82.113.48.5: bajty=32 čas=27 ms TTL=114
Odpoveď od 82.113.48.5: bajty=32 čas=30 ms TTL=114
Odpoveď od 82.113.48.5: bajty=32 čas=28 ms TTL=114
Odpoveď od 82.113.48.5: bajty=32 čas=29 ms TTL=114
Čas požiadavky uplynul. <-- This is a lag
Odpoveď od 82.113.48.5: bajty=32 čas=48 ms TTL=114
Odpoveď od 82.113.48.5: bajty=32 čas=46 ms TTL=114
Odpoveď od 82.113.48.5: bajty=32 čas=38 ms TTL=114
Odpoveď od 82.113.48.5: bajty=32 čas=37 ms TTL=114
Odpoveď od 82.113.48.5: bajty=32 čas=30 ms TTL=114
Odpoveď od 82.113.48.5: bajty=32 čas=37 ms TTL=114
Odpoveď od 82.113.48.5: bajty=32 čas=41 ms TTL=114
Odpoveď od 82.113.48.5: bajty=32 čas=74 ms TTL=114
Odpoveď od 82.113.48.5: bajty=32 čas=39 ms TTL=114
Understand?
LAG - ratmantoo - 12-19-2007
Well heres some Stats From South Africa
Pinging 82.113.48.5 with 32 bytes of data:
Reply from 82.113.48.5: bytes=32 time=452ms TTL=114
Reply from 82.113.48.5: bytes=32 time=451ms TTL=114
Reply from 82.113.48.5: bytes=32 time=458ms TTL=114
Reply from 82.113.48.5: bytes=32 time=452ms TTL=114
Reply from 82.113.48.5: bytes=32 time=457ms TTL=114
Reply from 82.113.48.5: bytes=32 time=452ms TTL=114
Reply from 82.113.48.5: bytes=32 time=449ms TTL=114
Reply from 82.113.48.5: bytes=32 time=450ms TTL=114
Reply from 82.113.48.5: bytes=32 time=459ms TTL=114
Reply from 82.113.48.5: bytes=32 time=454ms TTL=114
Reply from 82.113.48.5: bytes=32 time=453ms TTL=114
Reply from 82.113.48.5: bytes=32 time=451ms TTL=114
Reply from 82.113.48.5: bytes=32 time=451ms TTL=114
Reply from 82.113.48.5: bytes=32 time=453ms TTL=114
Reply from 82.113.48.5: bytes=32 time=452ms TTL=114
Reply from 82.113.48.5: bytes=32 time=452ms TTL=114
Reply from 82.113.48.5: bytes=32 time=451ms TTL=114
Reply from 82.113.48.5: bytes=32 time=450ms TTL=114
Reply from 82.113.48.5: bytes=32 time=450ms TTL=114
Reply from 82.113.48.5: bytes=32 time=451ms TTL=114
Reply from 82.113.48.5: bytes=32 time=454ms TTL=114
Ping statistics for 82.113.48.5:
Packets: Sent = 21, Received = 21, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 449ms, Maximum = 459ms, Average = 452ms
Pinging hp7-pool.centrum.cz [213.29.7.37] with 32 bytes of data:
Reply from 213.29.7.37: bytes=32 time=494ms TTL=232
Request timed out.
Reply from 213.29.7.37: bytes=32 time=489ms TTL=232
Reply from 213.29.7.37: bytes=32 time=490ms TTL=232
Reply from 213.29.7.37: bytes=32 time=490ms TTL=232
Reply from 213.29.7.37: bytes=32 time=490ms TTL=232
Reply from 213.29.7.37: bytes=32 time=489ms TTL=232
Reply from 213.29.7.37: bytes=32 time=488ms TTL=232
Reply from 213.29.7.37: bytes=32 time=490ms TTL=232
Reply from 213.29.7.37: bytes=32 time=490ms TTL=232
Reply from 213.29.7.37: bytes=32 time=491ms TTL=232
Reply from 213.29.7.37: bytes=32 time=490ms TTL=232
Reply from 213.29.7.37: bytes=32 time=490ms TTL=232
Reply from 213.29.7.37: bytes=32 time=490ms TTL=232
Reply from 213.29.7.37: bytes=32 time=489ms TTL=232
Reply from 213.29.7.37: bytes=32 time=488ms TTL=232
Reply from 213.29.7.37: bytes=32 time=491ms TTL=232
Ping statistics for 213.29.7.37:
Packets: Sent = 17, Received = 16, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 488ms, Maximum = 494ms, Average = 489ms
D:\Documents and Settings\Ratman>ping www.seznam.cz
Pinging www.seznam.cz [77.75.72.3] with 32 bytes of data:
Reply from 77.75.72.3: bytes=32 time=445ms TTL=51
Reply from 77.75.72.3: bytes=32 time=442ms TTL=51
Reply from 77.75.72.3: bytes=32 time=443ms TTL=51
Reply from 77.75.72.3: bytes=32 time=442ms TTL=51
Ping statistics for 77.75.72.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 442ms, Maximum = 445ms, Average = 443ms
Pinging server.hcn.cz [82.113.48.3] with 32 bytes of data:
Reply from 82.113.48.3: bytes=32 time=469ms TTL=50
Reply from 82.113.48.3: bytes=32 time=464ms TTL=50
Reply from 82.113.48.3: bytes=32 time=475ms TTL=50
Reply from 82.113.48.3: bytes=32 time=457ms TTL=50
Ping statistics for 82.113.48.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 457ms, Maximum = 475ms, Average = 466ms
Pathetic isn't it? Well TBH these values are a bit high. The best ping time ive had is 285 but normally average around 350.
And teh best of all
Tracing route to hcn-48-5.hanspaul-city.net [82.113.48.5]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.gateway
2 13 ms 15 ms 14 ms dsl-242-64-01.telkomadsl.co.za
3 * * * Request timed out. <----- WTF?
4 * * * Request timed out. <----- WTF?
5 31 ms 29 ms 29 ms 196.43.33.2
6 28 ms 23 ms 23 ms 196.43.33.5
7 386 ms 384 ms 384 ms ny-ip-dir-globalc-pos-3-0.telkom-ipnet.co.za [196.43.18.97] <----- Lovely!!!!!
8 382 ms 383 ms 387 ms nyk-i3-geth3-2.telia.net [213.248.82.237]
9 385 ms 385 ms 383 ms nyk-b1-link.telia.net [213.248.82.141]
10 449 ms 452 ms 456 ms ldn-bb2-link.telia.net [80.91.249.250]
11 420 ms 423 ms 422 ms hbg-bb2-link.telia.net [80.91.250.222]
12 481 ms 484 ms 483 ms prag-b1-link.telia.net [80.91.252.89]
13 446 ms 443 ms 449 ms dial-telecom-ic-119836-prag-b1.c.telia.net [80.239.193.38]
14 453 ms 453 ms 455 ms c3750vin-vlan.dialtelecom.cz [82.119.245.10]
15 453 ms 452 ms 446 ms vinicky2.inway.net [213.151.70.42]
16 453 ms 452 ms 454 ms hcn-48-5.hanspaul-city.net [82.113.48.5]
17 451 ms 455 ms 451 ms hcn-48-5.hanspaul-city.net [82.113.48.5]
The request time out could possibly be due to the phobia in this country of hacking - they dont allow pings or traces)
The "Problem" area is where the South African Exchange (SAIX) connects to the rest of the world.
So it looks like Im going to have to be a trader only......:(:(
LAG - Horon - 12-19-2007
Heres the data I got. Courtesy of my homemade server pinger.
S E R V E R P I N G
By Thomas Merrill (aka Single Earred Dude and KillaDude)
Pings a server, IP, or website.
Enter the IP, server, or internet address you would like to ping, or /exit.
ping: 82.113.48.5
Pinging...
Pinging 82.113.48.5 with 32 bytes of data:
Reply from 82.113.48.5: bytes=32 time=194ms TTL=114
Reply from 82.113.48.5: bytes=32 time=194ms TTL=114
Reply from 82.113.48.5: bytes=32 time=202ms TTL=114
Reply from 82.113.48.5: bytes=32 time=190ms TTL=114
Ping statistics for 82.113.48.5:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 190ms, Maximum = 202ms, Average = 195ms
Press any key to continue . . .
Ayiyi....Looks like I have a phone call to make...
By the way, SBC Yahoo DSL, 384k up, 768k down