Jump to content

Let's Talk About Ping. At What Point Do You Start Actually Noticing A Difference To Your Gameplay?

Started by Jon Cunningham, Mar 12 2015 03:22 PM

475 replies to this topic

#81 Bulletsponge0

    Member

  • PipPipPipPipPipPipPipPipPip
  • The Vicious
  • The Vicious
  • 2,947 posts

Posted 13 March 2015 - 05:23 PM

View PostJohnnyWayne, on 13 March 2015 - 04:15 PM, said:

tracert www.mwomercs.com >C:\results.txt

This writes the output directly under C in a textfile.

that isn't working for me..its not writing any file at all

#82 Cyborne Elemental

    Member

  • PipPipPipPipPipPipPipPipPip
  • 3,982 posts
  • LocationUSA

Posted 13 March 2015 - 05:38 PM

Tracing route to www.mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Zhone.Home [192.168.35.1]
2 8 ms 8 ms 9 ms dlrp-edge1.gwtc.net [64.251.185.10]
3 9 ms 9 ms 9 ms 169.232.115.66.unassigned.sdncommunication
[66.115.232.169]
4 * 69 ms 49 ms eqx.chi.ovh.NET [206.223.119.152]
5 118 ms 41 ms * mtl-2-6k.qc.ca [198.27.73.181]
6 43 ms 45 ms 43 ms bhs-g2-6k.qc.ca [198.27.73.7]
7 43 ms 43 ms 43 ms 198.27.73.233
8 43 ms 43 ms 43 ms mwomercs.com [192.99.109.192]

Trace complete.

I did this 5x, Sometimes Chicago is still freaking out, and I'll get request timed out every other try.

#83 Bulletsponge0

    Member

  • PipPipPipPipPipPipPipPipPip
  • The Vicious
  • The Vicious
  • 2,947 posts

Posted 13 March 2015 - 05:41 PM

View PostMister D, on 13 March 2015 - 05:38 PM, said:

Tracing route to www.mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Zhone.Home [192.168.35.1]
2 8 ms 8 ms 9 ms dlrp-edge1.gwtc.net [64.251.185.10]
3 9 ms 9 ms 9 ms 169.232.115.66.unassigned.sdncommunication
[66.115.232.169]
4 * 69 ms 49 ms eqx.chi.ovh.NET [206.223.119.152]
5 118 ms 41 ms * mtl-2-6k.qc.ca [198.27.73.181]
6 43 ms 45 ms 43 ms bhs-g2-6k.qc.ca [198.27.73.7]
7 43 ms 43 ms 43 ms 198.27.73.233
8 43 ms 43 ms 43 ms mwomercs.com [192.99.109.192]

Trace complete.

I did this 5x, Sometimes Chicago is still freaking out, and I'll get request timed out every other try.

how do you retrieve the results like that?

#84 Cyborne Elemental

    Member

  • PipPipPipPipPipPipPipPipPip
  • 3,982 posts
  • LocationUSA

Posted 13 March 2015 - 05:43 PM

CMD prompt

just go to the windows run box (windows search for win-7), type in Cmd.

paste in the traceroute, right click on the window when its done and mark a selection, press CTRL-C to copy it, then paste it where ever.

Edited by Mister D, 13 March 2015 - 05:44 PM.

#85 Bulletsponge0

    Member

  • PipPipPipPipPipPipPipPipPip
  • The Vicious
  • The Vicious
  • 2,947 posts

Posted 13 March 2015 - 05:55 PM

View PostMister D, on 13 March 2015 - 05:43 PM, said:

CMD prompt

just go to the windows run box (windows search for win-7), type in Cmd.

paste in the traceroute, right click on the window when its done and mark a selection, press CTRL-C to copy it, then paste it where ever.

the window closes the instant its done...there's no time to click anything

#86 Cyborne Elemental

    Member

  • PipPipPipPipPipPipPipPipPip
  • 3,982 posts
  • LocationUSA

Posted 13 March 2015 - 06:05 PM

C:\Windows\System32\cmd.exe
?

#87 Bulletsponge0

    Member

  • PipPipPipPipPipPipPipPipPip
  • The Vicious
  • The Vicious
  • 2,947 posts

Posted 13 March 2015 - 06:20 PM

View PostMister D, on 13 March 2015 - 06:05 PM, said:

C:\Windows\System32\cmd.exe
?

ah...thanks
you taught me the error I was making... instead of going where you just posted, I was using the windows key -R and running the tracert from there...

Tracing route to www.mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 3 ms 3 ms 3 ms homeportal [192.168.1.254]
2 24 ms 19 ms 21 ms 104-52-112-2.lightspeed.clmboh.sbcglobal.net [10
4.52.112.2]
3 19 ms 19 ms 20 ms 71.158.32.154
4 22 ms 22 ms 23 ms 12.83.38.17
5 28 ms 31 ms 30 ms ggr4.cgcil.ip.att.net [12.122.133.33]
6 * * * Request timed out.
7 * 29 ms 30 ms ae-21-3621.ear1.Chicago3.Level3.net [4.69.141.15
8]
8 * 58 ms * 192.99.146.65
9 * 61 ms * mtl-1-6k.qc.ca [198.27.73.183]
10 62 ms 62 ms 61 ms bhs-g1-6k.qc.ca [198.27.73.1]
11 62 ms 61 ms 63 ms 198.27.73.231
12 61 ms 59 ms 60 ms mwomercs.com [192.99.109.192]

Trace complete.

#88 MartyMechFly

    Rookie

  • 7 posts

Posted 14 March 2015 - 12:59 AM

playing from europe, i would say at 150 it gets really ugly concerning hitreg,

but just since a few weeks.

since then ping started to move anywhere between 150 and 250+.

disconnects and game crashes got very common, i am a league player (not this account :) )

and there it gets really uncomfortable, when you have to hold a game or do a redo sometimes

every few minutes because someone in both teams crashes.

hsr works worse now for me, dmg in pugs dropped in half.

gone are the times where i would put 1k dmg in my lights into opfor :(

my best hsr experience was where i put a dual gauss behind a light strafing by and killing him, keep in mind he was running out

of my aim, not in it.

___________________________________________________________________________________________

well heres a trcrt from 9 in the morning in my timezone (utc +1):


Routenverfolgung zu www.mwomercs.com [192.99.109.192] über maximal 30 Abschnitte
:

1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 6 ms 6 ms 6 ms 217.0.119.13
3 7 ms 7 ms 7 ms 87.190.184.14
4 15 ms 14 ms 15 ms f-ee5-i.F.DE.NET.DTAG.DE [62.154.14.238]
5 14 ms * 15 ms fra-1-6k.de.eu [94.23.122.153]
6 18 ms 17 ms 17 ms sbg-g2-a9.fr.eu [91.121.128.82]
7 17 ms 17 ms 17 ms 37.187.36.155
8 * * * Zeitüberschreitung der Anforderung.
9 107 ms 106 ms 106 ms mwomercs.com [192.99.109.192]

Ablaufverfolgung beendet.

Routenverfolgung zu www.mwomercs.com [192.99.109.192] über maximal 30 Abschnitte
:

1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 7 ms 6 ms 6 ms 217.0.119.13
3 7 ms 6 ms 7 ms 87.190.184.14
4 14 ms 14 ms 14 ms f-ee5-i.F.DE.NET.DTAG.DE [62.154.14.238]
5 * 15 ms * fra-1-6k.de.eu [94.23.122.153]
6 18 ms 18 ms 17 ms sbg-g2-a9.fr.eu [91.121.128.82]
7 18 ms 18 ms 17 ms 37.187.36.155
8 * * * Zeitüberschreitung der Anforderung.
9 107 ms 107 ms 106 ms mwomercs.com [192.99.109.192]

Ablaufverfolgung beendet.

Routenverfolgung zu www.mwomercs.com [192.99.109.192] über maximal 30 Abschnitte
:

1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 6 ms 6 ms 6 ms 217.0.119.13
3 7 ms 6 ms 7 ms 87.190.184.14
4 15 ms 14 ms 14 ms f-ee5-i.F.DE.NET.DTAG.DE [62.154.14.238]
5 14 ms * 15 ms fra-1-6k.de.eu [94.23.122.153]
6 17 ms 17 ms 18 ms sbg-g2-a9.fr.eu [91.121.128.82]
7 18 ms 17 ms 17 ms 37.187.36.155
8 * * * Zeitüberschreitung der Anforderung.
9 107 ms 107 ms 107 ms mwomercs.com [192.99.109.192]

Ablaufverfolgung beendet.

_________________________________________________________________________________________

pings with mwo running (syntax : ping 66.220.22.86 -l 64 -n 20), 3 times a ping
(concerning this : https://www.reddit.c..._to_do_a_quick/)

Ping wird ausgeführt für 66.220.22.86 mit 64 Bytes Daten:
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=167ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=345ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=222ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=175ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=174ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=167ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=163ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=167ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244

Ping-Statistik für 66.220.22.86:
Pakete: Gesendet = 20, Empfangen = 20, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 163ms, Maximum = 345ms, Mittelwert = 178ms


ping 66.220.22.86 -l 64 -n 20

Ping wird ausgeführt für 66.220.22.86 mit 64 Bytes Daten:
Antwort von 66.220.22.86: Bytes=64 Zeit=342ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=401ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=171ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=163ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=167ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=167ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244

Ping-Statistik für 66.220.22.86:
Pakete: Gesendet = 20, Empfangen = 20, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 163ms, Maximum = 401ms, Mittelwert = 186ms

ping 66.220.22.86 -l 64 -n 20

Ping wird ausgeführt für 66.220.22.86 mit 64 Bytes Daten:
Antwort von 66.220.22.86: Bytes=64 Zeit=171ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=174ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=163ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=167ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=163ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=178ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=168ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=227ms TTL=244

Ping-Statistik für 66.220.22.86:
Pakete: Gesendet = 20, Empfangen = 20, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 163ms, Maximum = 227ms, Mittelwert = 169ms



ping 188.165.12.106 -l 64 -n 20

Ping wird ausgeführt für 188.165.12.106 mit 64 Bytes Daten:
Antwort von 188.165.12.106: Bytes=64 Zeit=25ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=25ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=25ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57

Ping-Statistik für 188.165.12.106:
Pakete: Gesendet = 20, Empfangen = 20, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 24ms, Maximum = 25ms, Mittelwert = 24ms

ping 188.165.12.106 -l 64 -n 20

Ping wird ausgeführt für 188.165.12.106 mit 64 Bytes Daten:
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=25ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=25ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=25ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=25ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57

Ping-Statistik für 188.165.12.106:
Pakete: Gesendet = 20, Empfangen = 20, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 24ms, Maximum = 25ms, Mittelwert = 24ms

ping 188.165.12.106 -l 64 -n 20

Ping wird ausgeführt für 188.165.12.106 mit 64 Bytes Daten:
Antwort von 188.165.12.106: Bytes=64 Zeit=25ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=25ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=25ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57

Ping-Statistik für 188.165.12.106:
Pakete: Gesendet = 20, Empfangen = 20, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 24ms, Maximum = 25ms, Mittelwert = 24ms



ping 192.99.109.192 -l 64 -n 20

Ping wird ausgeführt für 192.99.109.192 mit 64 Bytes Daten:
Antwort von 192.99.109.192: Bytes=64 Zeit=108ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=108ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=108ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56

Ping-Statistik für 192.99.109.192:
Pakete: Gesendet = 20, Empfangen = 20, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 106ms, Maximum = 108ms, Mittelwert = 107ms

ping 192.99.109.192 -l 64 -n 20

Ping wird ausgeführt für 192.99.109.192 mit 64 Bytes Daten:
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=108ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=1619ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=109ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56

Ping-Statistik für 192.99.109.192:
Pakete: Gesendet = 20, Empfangen = 20, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 106ms, Maximum = 1619ms, Mittelwert = 182ms

ping 192.99.109.192 -l 64 -n 20

Ping wird ausgeführt für 192.99.109.192 mit 64 Bytes Daten:
Antwort von 192.99.109.192: Bytes=64 Zeit=108ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=108ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=108ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56

Ping-Statistik für 192.99.109.192:
Pakete: Gesendet = 20, Empfangen = 20, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 106ms, Maximum = 108ms, Mittelwert = 106ms



________________________________________________________________


this ones without running mwo, last 2 only one time because they were stable pings :


ping 66.220.22.86 -l 64 -n 20

Ping wird ausgeführt für 66.220.22.86 mit 64 Bytes Daten:
Antwort von 66.220.22.86: Bytes=64 Zeit=176ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=178ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=163ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=167ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=168ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=180ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244

Ping-Statistik für 66.220.22.86:
Pakete: Gesendet = 20, Empfangen = 20, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 163ms, Maximum = 180ms, Mittelwert = 167ms

ping 66.220.22.86 -l 64 -n 20

Ping wird ausgeführt für 66.220.22.86 mit 64 Bytes Daten:
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=209ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=168ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=182ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=163ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=168ms TTL=244

Ping-Statistik für 66.220.22.86:
Pakete: Gesendet = 20, Empfangen = 20, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 163ms, Maximum = 209ms, Mittelwert = 167ms


ping 66.220.22.86 -l 64 -n 20

Ping wird ausgeführt für 66.220.22.86 mit 64 Bytes Daten:
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=168ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=167ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=168ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=171ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=163ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=279ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=165ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=166ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=366ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=205ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244
Antwort von 66.220.22.86: Bytes=64 Zeit=164ms TTL=244

Ping-Statistik für 66.220.22.86:
Pakete: Gesendet = 20, Empfangen = 20, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 163ms, Maximum = 366ms, Mittelwert = 183ms


ping 192.99.109.192 -l 64 -n 20

Ping wird ausgeführt für 192.99.109.192 mit 64 Bytes Daten:
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Zeitüberschreitung der Anforderung.
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=106ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56
Antwort von 192.99.109.192: Bytes=64 Zeit=107ms TTL=56

Ping-Statistik für 192.99.109.192:
Pakete: Gesendet = 20, Empfangen = 19, Verloren = 1
(5% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 106ms, Maximum = 107ms, Mittelwert = 106ms


ping 188.165.12.106 -l 64 -n 20

Ping wird ausgeführt für 188.165.12.106 mit 64 Bytes Daten:
Antwort von 188.165.12.106: Bytes=64 Zeit=25ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=25ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=25ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=25ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=25ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=25ms TTL=57
Antwort von 188.165.12.106: Bytes=64 Zeit=24ms TTL=57

Ping-Statistik für 188.165.12.106:
Pakete: Gesendet = 20, Empfangen = 20, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 24ms, Maximum = 25ms, Mittelwert = 24ms

Edited by MartyMechFly, 14 March 2015 - 01:02 AM.

#89 p4r4g0n

    Member

  • PipPipPipPipPipPipPipPip
  • Knight Errant
  • 1,511 posts
  • LocationMalaysia

Posted 14 March 2015 - 04:51 AM

On a good day, my in-game ping is 280'ish. Most of the time its something between between 300 to 350. I am not citing ICMP ping numbers obtained thru the command window as it is meaningless insofar as the game is concerned as it frequently differs from the in-game ping.

Regardless of ping values, I am used to dealing with the level of latency that exists and accept that there are some things I will never be able to do that low pingers can.

It is pretty obvious in-game when something is up with the connection because target acquisition, zoom, target info is slow to update and checking the in-game ping will usually show an increase of 100ms or more. My assumption when this happens is that some packet loss or congestion has occurred somewhere along the connection.

If it persists, for more than a few seconds or repeats in a second match, it is usually time to call it a night as it is pretty difficult to play when it takes half a second or more just to acquire a target, etc.

Insofar as HSR is concerned, while there are some anomalous instances where shots go through targets even when ping is stable, it is generally fine with the appropriate caveat for lasers due to HSR mechanics. Regardless of its faults, it is better than not having HSR especially since my connection has frequent minor latency fluctuations leading to variations in how much on is required to lead a target in order to hit it.

Edited by p4r4g0n, 14 March 2015 - 04:51 AM.

#90 CaptOven

    Member

  • PipPipPip
  • The 1 Percent
  • The 1 Percent
  • 77 posts

Posted 14 March 2015 - 10:00 AM

Mine is usually 90ish but sometimes goes up to 120ish. But I can't say I can spot the difference.

#91 990Dreams

    Member

  • PipPipPipPipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 2,908 posts
  • LocationHotlanta

Posted 14 March 2015 - 10:46 AM

I notice a drastic change around 150-200+ in my hit reg/rubber-banding/lag, before that everything seems normal.

Edited by DavidHurricane, 14 March 2015 - 10:46 AM.

#92 Bulletsponge0

    Member

  • PipPipPipPipPipPipPipPipPip
  • The Vicious
  • The Vicious
  • 2,947 posts

Posted 14 March 2015 - 04:48 PM

oh...and don't bother firing any kind of PPC at a light with a ping over 110... it absolutely will not register at all

#93 Nathan Foxbane

    Member

  • PipPipPipPipPipPipPipPipPip
  • The Wolf
  • The Wolf
  • 2,984 posts

Posted 14 March 2015 - 08:02 PM

I notice a change once I break 150+ which has been happening a lot lately. Last several patches have seen my ping steadily creep up.

#94 Chimperator

    Member

  • PipPipPipPipPipPip
  • 239 posts
  • Twitch: Link
  • LocationGermany

Posted 14 March 2015 - 08:15 PM

I normaly have a ping about 100-115 and it seems to me anyone with a ping under 90 dosen't take the dmg they should like.
The smaler the ping of my opponent is the issues are more noticeable.
Around pings under 50 it looks like some people just point there laser for a millisecond on me and jittering all over my mech with there lasers but they does full dmg on one component.

And with pings about 135+ the game becomes lags when I activate zoom or heat/nightvision and some rubberbandings.

#95 aniviron

    Member

  • PipPipPipPipPipPipPipPipPip
  • 3,752 posts

Posted 14 March 2015 - 09:13 PM

I was on ~60 ping for about a year, and the game played well. I moved, and had around 80ish, and noticed virtually no difference in performance. I'm on Time Warner, and for a while after the server move I was getting 110-120, and that was definitely a huge step down, and very noticeable in terms of what hit and did not, and how mechs moved.

About the only difference between 60 and 80 seems to be the delay on zooming in, which is for some reason linked to ping? In the testing grounds zooming is instant, but it hitches in net play, and takes longer to zoom in/out when you have a higher ping, and that gets bad really fast.

#96 Juju Shinobi

    Member

  • PipPipPipPipPip
  • Rage
  • Rage
  • 168 posts
  • LocationSingapore

Posted 14 March 2015 - 09:29 PM

I'm usually hovering around 250 ping. Laser hit reg is one major issue I have because I will have to lead my target a lot when using laser boats. I never dare 1v1 another light because even if they aren't as good as me, they probably have a lot better laser hit reg and can pinpoint components unlike me.

I also have issues of ghost SRMs/AC20s (the projectile flies through a target) when I'm within around 150m of the target which has caused me to die on multiple occasions.

Best example I could find showing how bad my laser hit reg is.


Edited by JujuShinobi, 15 March 2015 - 08:12 AM.

#97 On1m

    Member

  • PipPipPipPipPip
  • Elite Founder
  • Elite Founder
  • 110 posts

Posted 14 March 2015 - 09:34 PM

I usually play at under 50ms ping. I notice a lot of lag and hit registration problems when I get spikes up to the 90-140ms range.

#98 white0Fox

    Member

  • PipPipPipPipPipPipPip
  • WC 2017 Participant
  • 577 posts

Posted 15 March 2015 - 05:21 AM

My Ping 90-140 ms.
Many hitereg problems. (SRM and C-ERPPC very bad)


#99 skill gap

    Member

  • PipPipPip
  • Heavy Lifter
  • 74 posts

Posted 15 March 2015 - 05:40 AM

Hit reg is awful with a 26-30ms ping. Some players are nearly invincible, some aren't. It's like rolling dice.

#100 Rubaulianta

    Rookie

  • Bad Company
  • 4 posts

Posted 15 March 2015 - 01:05 PM

Yeah well.. Light mechs turn to be hard to defeat over 200 ms somehow. Like hitting a bee with a slingshot.
But under this level, is acceptable overall.
Back to Developer Outreach · Next Unread Topic →


14 user(s) are reading this topic

0 members, 14 guests, 0 anonymous users