180 replies to this topic

[Jon Cunningham]

Rasc4l, on 13 November 2014 - 07:38 AM, said:

I was told by Kaffeangst that he moved within US and while his ping remained the same (55-70 ms), the new location had much worse hit detection.

Unlikely - we've made some major changes to the game and hit reg code since the move.

In terms of what I'm looking for, and helping out with, is making sure traffic flows consistently and quickly from our datacenter to the edge of your ISP along a reasonable path. When I have evidence the traffic is performing poorly, I can act on it and get it fixed.

However, the hit reg algorithims, PC performance, etc. I can't really help out with that, the best route is to speak with Neema if he is available or to send a ticket to support.

That Dawg, on 13 November 2014 - 05:20 AM, said:

Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\>tracert 192.99.109.192 Tracing route to mwomercs.com [192.99.109.192] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms 192.168.1.1 2 7 ms 10 ms 7 ms dynamic-acs-24-112-183-1.zoominternet.net [24.11 2.183.1] 3 23 ms 17 ms 13 ms dynamic-acs-72-23-10-245.zoominternet.net [72.23 .10.245] 4 219 ms 22 ms 228 ms te-8-2.car2.Pittsburgh3.Level3.net [4.49.110.69] 5 * 31 ms 27 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43] 6 * * * Request timed out. 7 35 ms 36 ms 38 ms bhs-g1-6k.qc.ca [198.27.73.205] 8 34 ms 36 ms 35 ms 198.27.73.231 9 33 ms 33 ms 41 ms mwomercs.com [192.99.109.192] Trace complete.

Hey man, are you actually having any problems with lag? With a ping of 33ms, you seem to be in a pretty good spot?

[Captain Stiffy]

Jon Cunningham, on 13 November 2014 - 04:11 PM, said:

I should be able to get you fixed a bit. I don't think you'll see 8 again (the DC is no longer in Toronto) but there is no good reason for your traffic to go south to Texas before coming back north to Canada.

Awesome! Glad it was helpful to you.

[Rasc4l]

Jon Cunningham, on 13 November 2014 - 04:20 PM, said:

Unlikely - we've made some major changes to the game and hit reg code since the move.

However, the hit reg algorithims, PC performance, etc. I can't really help out with that, the best route is to speak with Neema if he is available or to send a ticket to support.

Well it sure is interesting to know that changes were made. Is anyone at PGI currently aware that the changes have made hitreg horribly worse? There are many threads like this for example with no answer from PGI representative while trivialities like weapon groups are high priority. I would certainly think the ingame experience over the Internet would be of highest priority instead of something like weapon groups, which take 5 seconds in the beginning of the match to fix when they are wrong. Don't take me wrong, I certainly appreciate if you finally manage to crack down the weapon group bug but come on, the actual hitreg in a game which is based on h i t t i n g the enemies...? Weapon groups bug is annoying, buggy hitreg is game breaking.

Now do I really need to start PM:ing Neema or whoever is in charge of netcode if he would happen to be available or could you perhaps just give him a hint or is in-house information sharing at PGI just as bad as it was between PGI and IGP?

[Alexander Garden]

Evaluation of the hitreg is ongoing. I hope to have some updates for everyone soon.

[GernMiester]

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

1 <1 ms <1 ms <1 ms REMOVED

2 21 ms 23 ms 28 ms REMOVED.hsd1.pa.comcast.net

3 10 ms 10 ms 11 ms nj.panjde.comcast.net [68.85.77.49]

4 13 ms 13 ms 16 ms xe-6-1-3-0-ar03.absecon.nj.panjde.comcast.net [6
8.85.35.197]

5 25 ms 19 ms 18 ms he-3-10-0-0-cr01.ashburn.va.ibone.comcast.net [6
8.86.166.105]

6 22 ms 22 ms 19 ms be-10002-cr01.newyork.ny.ibone.comcast.net [68.8
6.86.234]

7 20 ms 18 ms 18 ms te-0-1-0-3-pe04.ashburn.va.ibone.comcast.net [68
.86.84.246]

8 45 ms 39 ms 40 ms 198.27.73.61

9 * * * Request timed out.

10 42 ms 43 ms 41 ms bhs-g1-6k.qc.ca [198.27.73.205]

11 46 ms 46 ms 56 ms 198.27.73.231

12 45 ms 42 ms 40 ms mwomercs.com [192.99.109.192]

Trace complete.

[KrazedOmega]

Not really having any issues, but here it is anyways.


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

1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 14 ms 10 ms 13 ms Dx4sc-g15.wp.shawcable.net [64.59.179.105]
4 21 ms 15 ms 18 ms 66.163.73.10
5 22 ms 23 ms 31 ms rc3ec-tge0-11-0-30.il.shawcable.net [66.163.73.2
29]
6 39 ms 48 ms 35 ms 66.163.75.117
7 * * * Request timed out.
8 54 ms * 53 ms 198.27.73.179
9 54 ms 55 ms 54 ms bhs-g1-6k.qc.ca [198.27.73.5]
10 55 ms 54 ms 57 ms 198.27.73.231
11 55 ms 55 ms 54 ms mwomercs.com [192.99.109.192]

Trace complete.

[SoggyGorilla]

you'll notice the last hop is the mwo site ip. also that my ping doubles at that point. definitely a routing problem. its most likely a latency issue with a hardware firewall, or they are capping your bandwidth.

also the router that shows no info is some kind of firewall or has ping disabled.


the reason this is strange is because people that are in Australia have lower ping than me. i live in Texas.

Edited by SoggyGorilla, 13 November 2014 - 07:11 PM.

[SoggyGorilla]

apparently things have taken a turn for the worse, at the data-center as my ping is now quadrupled. started at 75, is now 332.

[StraferX]

Normaly have no issues other than random occasional nvidia driver failure just had a game that was a total rubber banding lag fest

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.


C:\Users\StraferX>tracert 192.99.109.192

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

1 2 ms 30 ms 30 ms router.asus.com [192.168.1.1]
2 62 ms 61 ms 46 ms 107.4.180.1
3 46 ms 46 ms 30 ms te-4-2-ur01.bluefield.wv.richmond.comcast.net [6
8.85.214.133]
4 30 ms 46 ms 61 ms te-4-2-ur02.huntington.wv.richmond.comcast.net [
69.139.165.150]
5 62 ms 62 ms 46 ms te-6-1-ur01.huntington.wv.richmond.comcast.net [
68.85.214.13]
6 46 ms 61 ms 77 ms xe-12-0-2-0-ar02.charlvilleco.va.richmond.comcas
t.net [68.86.172.169]
7 62 ms 77 ms 77 ms pos-1-2-0-0-cr01.ashburn.va.ibone.comcast.net [6
8.86.91.53]
8 77 ms 77 ms 77 ms be-10002-cr01.newyork.ny.ibone.comcast.net [68.8
6.86.234]
9 93 ms 93 ms 77 ms he-0-13-0-0-pe03.111eighthave.ny.ibone.comcast.n
et [68.86.85.182]
10 77 ms 77 ms * 198.27.73.61
11 * * * Request timed out.
12 123 ms 108 ms 93 ms bhs-g1-6k.qc.ca [198.27.73.205]
13 109 ms 108 ms 93 ms 198.27.73.231
14 93 ms 108 ms 124 ms mwomercs.com [192.99.109.192]

Trace complete.

C:\Users\StraferX>

Edited by StraferX, 13 November 2014 - 07:24 PM.

[SoggyGorilla]

well its edged somewhat higher to 356ms ping. apparently, if i was located on the moon, my ping should average about 1200ms, so with that logic im about 1/4 of the way there now.

[Troopie]

[Quietruck]

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Quietruck>tracert 192.99.109.192

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 44 ms 56 ms 44 ms adsl-67-67-15-254.dsl.okcyok.swbell.net [67.67.1
5.254]
3 45 ms 48 ms 46 ms 12.83.42.109
4 54 ms 51 ms 51 ms gar26.dlstx.ip.att.net [12.123.16.85]
5 * * * Request timed out.
6 * 175 ms * ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
7 124 ms * 181 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
8 * * * Request timed out.
9 93 ms 93 ms 95 ms bhs-g1-6k.qc.ca [198.27.73.205]
10 93 ms 93 ms 93 ms 198.27.73.231
11 92 ms 91 ms 92 ms mwomercs.com [192.99.109.192]

Trace complete.

My ping in game is always around 109, I never see a ping of even 54. Things get really lagging when the action increases. Looking here at the results, it's worse then I thought. Must be the fact that I'm in a fly over state of Oklahoma. Got a buddy in Arizona who wants to play, but his ping is like 300-600. Please fix soon

Edited by Quietruck, 13 November 2014 - 10:30 PM.

[Gargoth]

C:\Windows\system32>tracert 192.99.109.192

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

1 <1 ms 1 ms <1 ms router.asus.com [192.168.1.1]
2 20 ms 18 ms 18 ms dsl-tkubrasgw2-54faa0-1.dhcp.inet.fi [84.250.160
.1]
3 23 ms 22 ms 22 ms hls-b2-link.telia.net [62.115.143.50]
4 29 ms 31 ms 30 ms s-bb4-link.telia.net [213.155.133.74]
5 48 ms 47 ms 47 ms ffm-bb2-link.telia.net [213.155.135.30]
6 48 ms 48 ms 51 ms ffm-b11-link.telia.net [62.115.138.11]
7 * * * Request timed out.
8 59 ms 58 ms 59 ms sbg-g1-a9.fr.eu [91.121.128.127]
9 69 ms 62 ms 63 ms 37.187.36.153
10 * * * Request timed out.
11 141 ms 142 ms 141 ms mwomercs.com [192.99.109.192]

Trace complete.
There you go. Some more data to be crunched.

[DaFurryFury]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Roland>tracert 192.99.109.192

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

1 <1 ms <1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 14 ms 9 ms 69.145.247.141
4 11 ms 12 ms 22 ms chywyaT1cr5-XE-5-0-0-U0.int.bresnan.net [72.175.110.136]
5 14 ms 19 ms 90 ms dencofh1cr5-XE-4-0-0-U0.int.bresnan.net [69.146.190.246]
6 15 ms 24 ms 37 ms dencofh1tr5-XE-4-3-0-U0.int.bresnan.net [72.175.111.142]
7 16 ms 75 ms 19 ms 4.34.48.149
8 147 ms 66 ms 79 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
9 * 98 ms 69 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
10 * * * Request timed out.
11 113 ms 106 ms 83 ms bhs-g1-6k.qc.ca [198.27.73.205]
12 72 ms 109 ms 73 ms 198.27.73.231
13 78 ms 68 ms 73 ms mwomercs.com [192.99.109.192]

Trace complete.

C:\Users\Roland>

Edited by DaFurryFury, 14 November 2014 - 12:22 AM.

[Jaawa]

From approximately the middle of Finland:

[VXJaeger]

Central Finland, 100/10 optic fibre connection.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\X>tracert 192.99.109.192

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

1 65 ms 99 ms 99 ms dsldevice.lan [192.168.1.1]
2 19 ms 18 ms 19 ms dsl-jklbrasgw1-54fb00-1.dhcp.inet.fi [84.251.0.1
]
3 27 ms 28 ms 27 ms hls-b1-link.telia.net [62.115.143.84]
4 34 ms 34 ms 34 ms s-bb4-link.telia.net [80.91.247.220]
5 53 ms 53 ms 53 ms ffm-bb2-link.telia.net [80.91.251.156]
6 58 ms 58 ms 56 ms ffm-b11-link.telia.net [213.155.130.227]
7 * * * Request timed out.
8 66 ms 66 ms 66 ms rbx-s11-6k.fr.eu [91.121.131.250]
9 72 ms 65 ms 69 ms 37.187.36.153
10 * * * Request timed out.
11 139 ms 139 ms 139 ms mwomercs.com [192.99.109.192]

Trace complete.


Tracing route to ns7000224.ip-192-99-40.net [192.99.40.103]
over a maximum of 30 hops:

1 2 ms 99 ms 99 ms dsldevice.lan [192.168.1.1]
2 19 ms 19 ms 19 ms dsl-jklbrasgw1-54fb00-1.dhcp.inet.fi [84.251.0.1
]
3 25 ms 26 ms 25 ms hls-b1-link.telia.net [62.115.143.84]
4 33 ms 33 ms 34 ms s-bb3-link.telia.net [80.91.245.178]
5 126 ms 114 ms 57 ms ffm-bb1-link.telia.net [213.155.135.50]
6 55 ms 53 ms 54 ms ffm-b11-link.telia.net [62.115.137.251]
7 * * * Request timed out.
8 70 ms 70 ms 69 ms rbx-g1-a9.fr.eu [91.121.131.193]
9 * * * Request timed out.
10 * * 238 ms nwk-1-6k.nj.us [178.33.100.234]
11 141 ms 141 ms 141 ms bhs-g1-6k.qc.ca [198.27.73.205]
12 142 ms 141 ms 142 ms bhs-s4-6k.qc.ca [198.27.73.144]
13 144 ms 144 ms 144 ms ns7000224.ip-192-99-40.net [192.99.40.103]

Trace complete.


Tracing route to 209.15.227.106 over a maximum of 30 hops

1 3 ms 99 ms 99 ms dsldevice.lan [192.168.1.1]
2 19 ms 19 ms 18 ms dsl-jklbrasgw1-54fb00-1.dhcp.inet.fi [84.251.0.1
]
3 27 ms 27 ms 27 ms hls-b2-link.telia.net [62.115.143.50]
4 33 ms 32 ms 34 ms s-bb4-link.telia.net [213.155.134.110]
5 65 ms 40 ms 39 ms kbn-bb4-link.telia.net [62.115.139.173]
6 128 ms 129 ms 129 ms nyk-bb2-link.telia.net [80.91.254.91]
7 151 ms 151 ms 150 ms chi-b21-link.telia.net [62.115.137.35]
8 150 ms 205 ms 150 ms peer1-ic-307697-chi-b21.c.telia.net [80.239.128.
30]
9 * * * Request timed out.
10 * * * Request timed out.
11 151 ms 151 ms 150 ms 209.15.227.106

Trace complete.

Edited by VXJaeger, 14 November 2014 - 08:42 AM.

[Paavo Perusjuntti]

Central/Western Finland, 4G LTE connection ()



Usually a very playable connection, at least compared to my old ADSL...

[Iteration616]

Southern Finland, nominally 24/1 DSL connection


C:\>tracert 192.99.109.192

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

1 2 ms <1 ms <1 ms 192.168.0.254
2 25 ms 22 ms 24 ms jarjpa1.fi.elisa.net [88.113.128.1]
3 21 ms 22 ms 22 ms ge1-1-0.vanhel-p1.fi.elisa.net [139.97.10.25]
4 22 ms 24 ms 21 ms ae10.helpa-p1.fi.elisa.net [139.97.6.205]
5 22 ms 21 ms 21 ms ae2.helpa-gw1.fi.elisa.net [139.97.6.250]
6 22 ms 21 ms 21 ms ae1-10.bbr1.hel2.fi.eunetip.net [213.192.191.53]

7 58 ms 57 ms 56 ms as0-0.bbr1.ffm1.de.eunetip.net [213.192.191.197]

8 * * 57 ms decix.routers.ovh.net [80.81.192.209]
9 60 ms 60 ms 60 ms sbg-g2-a9.fr.eu [91.121.128.125]
10 56 ms 57 ms 57 ms 37.187.36.155
11 * * * Request timed out.
12 153 ms 152 ms 152 ms mwomercs.com [192.99.109.192]

Trace complete.

C:\>tracert 192.99.109.192

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

1 1 ms 3 ms 6 ms 192.168.0.254
2 23 ms 25 ms 23 ms jarjpa1.fi.elisa.net [88.113.128.1]
3 23 ms 22 ms 22 ms ge1-1-0.vanhel-p1.fi.elisa.net [139.97.10.25]
4 30 ms 23 ms 22 ms ae10.helpa-p1.fi.elisa.net [139.97.6.205]
5 21 ms 22 ms 23 ms ae2.helpa-gw1.fi.elisa.net [139.97.6.250]
6 21 ms 21 ms 21 ms ae1-10.bbr1.hel2.fi.eunetip.net [213.192.191.53]

7 57 ms 56 ms 59 ms as0-0.bbr1.ffm1.de.eunetip.net [213.192.191.197]

8 96 ms * 89 ms decix.routers.ovh.net [80.81.192.209]
9 61 ms 62 ms 65 ms sbg-g2-a9.fr.eu [91.121.128.125]
10 58 ms 58 ms 56 ms 37.187.36.155
11 * * * Request timed out.
12 152 ms 153 ms 152 ms mwomercs.com [192.99.109.192]

Trace complete.

C:\>tracert 192.99.109.192

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

1 1 ms <1 ms <1 ms 192.168.0.254
2 25 ms 23 ms 24 ms jarjpa1.fi.elisa.net [88.113.128.1]
3 22 ms 22 ms 22 ms ge1-1-0.vanhel-p1.fi.elisa.net [139.97.10.25]
4 28 ms 22 ms 23 ms ae10.helpa-p1.fi.elisa.net [139.97.6.205]
5 41 ms 23 ms 23 ms ae2.helpa-gw1.fi.elisa.net [139.97.6.250]
6 22 ms 22 ms 23 ms ae1-10.bbr1.hel2.fi.eunetip.net [213.192.191.53]

7 57 ms 56 ms 57 ms as0-0.bbr1.ffm1.de.eunetip.net [213.192.191.197]

8 * * * Request timed out.
9 60 ms 60 ms 60 ms sbg-g2-a9.fr.eu [91.121.128.125]
10 56 ms 57 ms 58 ms 37.187.36.155
11 * * * Request timed out.
12 152 ms 153 ms 153 ms mwomercs.com [192.99.109.192]

Trace complete.

[Jon Cunningham]

Lots of complaints from different people in Finland. Will investigate.

[Jack Avery]

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 10 ms 8 ms 10.10.0.1
3 8 ms 13 ms 7 ms host-5-2-220-24-static.midco.net [24.220.2.5]
4 15 ms 12 ms 13 ms host-41-13-220-24-static.midco.net [24.220.13.41
]
5 29 ms 17 ms 17 ms host-137-13-220-24-static.midco.net [24.220.13.1
37]
6 17 ms 18 ms 21 ms host-41-19-220-24-static.midco.net [24.220.19.41
]
7 88 ms 87 ms 108 ms eqx.snj.ovh.net [206.223.116.193]
8 84 ms * 84 ms pal-1-6k.ca.us [178.32.135.169]
9 * * * Request timed out.
10 101 ms 219 ms 102 ms 198.27.73.173
11 105 ms 106 ms 107 ms bhs-g2-6k.qc.ca [198.27.73.7]
12 111 ms 108 ms 105 ms 198.27.73.233
13 108 ms 104 ms 127 ms mwomercs.com [192.99.109.192]

Trace complete.

Wait...did that just send me to France? WTH...