129 replies to this topic

[kiriage]

was 270..now high 400's

Cairns, Australia

Hit reg bizarrely seems better..although I did change from ADSL to ADSL2+ whilst the server transitioned.

[Major Derps]

Daemonhunter, on 30 August 2014 - 05:29 PM, said:

Before: ~225ms
After: ~320ms
Location: NZ

My ping before the move was fairly consistently around 225ms, which was a disadvantage but a playable one (we New Zealanders generally take that sort of thing as a given for most online games). Unfortunately now it's mostly over 300ms, usually in the 315-340 range (sometimes higher), with lots of desyncs occurring. This does not create a satisfactory gaming experience, and I expect I am not the only player who would be forced to abandon the game if it doesn't improve. This would be a shame since I've sunk a fair few $ into it and have enjoyed it enough to overlook various bugs, but this particular issue is not one that can be easily ignored.

Judging from the comments so far, it generally looks like the ping only improved for people who already had a good ping in the first place. Those who most needed a boost have been hurt considerably. It's like tax hikes for the poor to give tax breaks to the wealthy. I sincerely hope these are just teething issues on the new setup and that there is something that can be done to fine-tune the servers and improve performance where it is actually needed.

PS: it's even more annoying that this should occur when a lot of us still have premium time from the last challenge, which is now going to waste...

I have premium time I've payed for ticking away, but can't use due to these connection issues. The more I investigate it (because I'm pissed my premium time is going unused), PGI essentially excluding part of their player base (mainly those which will have money invested/spent on the game), through no fault of the players; is leaving PGI way to open to legal/class action.

Long story short, I have payed for a product I can not use, through no action or fault of my own.

Edited by Mokey Mot, 30 August 2014 - 08:23 PM.

[FatYak]

just had a match where my ping spiked anywhere from 270 to 600. Hit registration is bloody terrible

[Oderint dum Metuant]

For the complainants from the Asia regions, do some traceroutes and post them.
If like another Aus based player your all being routed through Europe, that is not PGI's problem nor is it there fault, that's down to ISP and above.

(probably the first time i have defended PGI and i feel sick)

[Amardez]

DV McKenna, on 31 August 2014 - 12:05 AM, said:

For the complainants from the Asia regions, do some traceroutes and post them.
If like another Aus based player your all being routed through Europe, that is not PGI's problem nor is it there fault, that's down to ISP and above.

(probably the first time i have defended PGI and i feel sick)

This is too common to be down to one or two ISP's, if it is a standard then it is PGI who should have done the leg work and checked what the end result for MOST people would have been all of OZ and NZ (every player i know who lives in OZ and NZ has been affected) and even some eastern block people (from what is saw and redit and people i have talked to in those few games i managed to get into and not really play) is too many to have not realized if they were doing a good job of checking these things out. So yes it is their fault not so much for they way ISP(s) rout done but for not checking first it is a total lack of due dalliance.

[Oderint dum Metuant]

Amardez, on 31 August 2014 - 12:20 AM, said:

This is too common to be down to one or two ISP's, if it is a standard then it is PGI who should have done the leg work and checked what the end result for MOST people would have been all of OZ and NZ (every player i know who lives in OZ and NZ has been affected) and even some eastern block people (from what is saw and redit and people i have talked to in those few games i managed to get into and not really play) is too many to have not realized if they were doing a good job of checking these things out. So yes it is their fault not so much for they way ISP(s) rout done but for not checking first it is a total lack of due dalliance.

Really? You want them to go and ask tier 1 and 2 ISP's how they will route their traffic?
There is a chap from melbourne in another thread who's ping has improved, so it is not every Aus and NZ player at all.

Has the new move boned a good number of you, yes it appears to have done so, is that down to PGI well perhaps a little for moving servers, but in large it's down at the Tier 1 and 2 ISP level, for routing traffic in such a ******** way.

This is not a unique situation, it happens all the time ISP forums are littered with these problems, i remember having the same issues with Virgin and Telia's routing to blizzard servers, it takes a long long time to get ISP's to fix it, lot's of traceroutes showing the problem (and in the end lots of people migrating ISP lol)

Same reason why from a UK perspective i left Virgin Media, my ping here was 130+ moving to sky it was 100 or less and now 90 or less.
I get a better ping from the UK than most Americans do.

Edited by DV McKenna, 31 August 2014 - 12:40 AM.

[Marmon Rzohr]

Strange that I can't find an offical feedback thread for this.

Region: Central EU
Old ping: 150
New ping: 113-124

[Amardez]

DV McKenna, on 31 August 2014 - 12:36 AM, said:

Really? You want them to go and ask tier 1 and 2 ISP's how they will route their traffic?
There is a chap from melbourne in another thread who's ping has improved, so it is not every Aus and NZ player at all.

Has the new move boned a good number of you, yes it appears to have done so, is that down to PGI well perhaps a little for moving servers, but in large it's down at the Tier 1 and 2 ISP level, for routing traffic in such a ******** way.

This is not a unique situation, it happens all the time ISP forums are littered with these problems, i remember having the same issues with Virgin and Telia's routing to blizzard servers, it takes a long long time to get ISP's to fix it, lot's of traceroutes showing the problem (and in the end lots of people migrating ISP lol)

Same reason why from a UK perspective i left Virgin Media, my ping here was 130+ moving to sky it was 100 or less and now 90 or less.
I get a better ping from the UK than most Americans do.

The Reason I used caps for most is because there is almost always exceptions to the rule.

As to Knowing the internet they provide goods all be it Digital and services over the internet so know how it works and what effects their changes will make to their costumes is the very core of their business, the quality of game(s) is a moot point if they can not proved it to their costumes.

Now as for going and asking every ISP not at all they would tender a contract for a company the specialties in that kind of thing just like when you want to open a Cafe or shop you if you are doing your due dalliance would pay someone to do a Survey of the area looking at things like foot traffic and likely customer flows. Just because it is Digital is no excuse to ignore things like that, but you are quite right it happens to other games that however makes it even worse they have other peoples sins they could have learnt from.

and as a side note on a firer connection going from NZ to US i am still +300. 1 have one link in Auckland then the next which is just a IP number is listed as US

[Idealsuspect]

My ping didnt move

Location EU

Edited by Idealsuspect, 31 August 2014 - 06:03 AM.

[DarthPayne]

In-game pings:
Old: 145-165 ms
New: 100-190 ms
Location: Switzerland
ISP: UPC Cablecom, 125 MBit/s down, 10 Mbit/s up.
Local Network: Modem CATV Cable Modem Ubee EVM3200, Router AVM FritzBox 7390, Gigabit Ethernet Cabling

Two hops more in the tracert now. Much more ping deviation. Was much more stable before. A much higher degree of warping and higher number of desynced games.

Tracert:

Spoiler

Tracing route to 192.99.109.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  fritz.box [192.168.0.1]
  2    10 ms    10 ms    10 ms  80-218-120-1.dclient.hispeed.ch [80.218.120.1]
  3    11 ms	 9 ms	 7 ms  217-168-53-37.static.cablecom.ch [217.168.53.37]
  4    12 ms    11 ms    13 ms  84.116.200.233
  5	 9 ms	 9 ms	 9 ms  ch-zrh01b-ra1-ae-1.aorta.net [84.116.134.142]
  6	 *	   10 ms	 *	 zur-1-6k.ch.eu [91.121.131.61]
  7    17 ms	 *	    *	 fra-5-6k.fr.eu [94.23.122.145]
  8    21 ms    20 ms    21 ms  sbg-g2-a9.fr.eu [91.121.128.125]
  9    20 ms    23 ms    23 ms  37.187.36.155
 10	 *	    *	    *	 Request timed out.
 11	 *	    *	    *	 Request timed out.
 12   111 ms   113 ms   114 ms  192.99.109.129

Tracing route to relay-1.mwtactics.com [70.42.29.65]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  fritz.box [192.168.0.1]
  2	 8 ms	 8 ms	 9 ms  80-218-120-1.dclient.hispeed.ch [80.218.120.1]
  3	 9 ms	 9 ms	 9 ms  217-168-53-37.static.cablecom.ch [217.168.53.37]
  4   122 ms   121 ms   121 ms  84.116.211.18
  5   121 ms   123 ms   121 ms  84.116.204.233
  6   116 ms   118 ms   117 ms  84-116-130-57.aorta.net [84.116.130.57]
  7   121 ms   122 ms   119 ms  ch-zrh02a-ra1-xe-2-1-0.aorta.net [84.116.130.114]
  8   130 ms   122 ms   140 ms  us-was03a-rd1-xe-0-3-0.aorta.net [84.116.130.66]
  9   120 ms   119 ms   119 ms  us-was03a-rd1-xe-0-1-0.aorta.net [84.116.130.165]
 10   114 ms   113 ms   115 ms  ash-b2-link.telia.net [62.115.41.9]
 11   120 ms   121 ms   123 ms  globalcrossing-ic-130167-ash-bb1.c.telia.net [213.248.84.154]
 12   132 ms   123 ms   124 ms  lag9.csr1.DCA3.gblx.net [67.16.146.25]
 13   117 ms   115 ms   115 ms  ae3.scr4.WDC2.gblx.net [67.16.166.229]
 14   143 ms   142 ms   140 ms  te8-3-10G.asr1.YYZ1.gblx.net [209.130.131.122]
 15   135 ms   133 ms   135 ms  64.210.12.62
 16   134 ms   133 ms   131 ms  border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.196]
 17   135 ms   133 ms   135 ms  relay-1.mwtactics.com [70.42.29.65]

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

  1    <1 ms    <1 ms    <1 ms  fritz.box [192.168.0.1]
  2	 7 ms	 7 ms    10 ms  80-218-120-1.dclient.hispeed.ch [80.218.120.1]
  3	 9 ms    11 ms	 9 ms  217-168-53-37.static.cablecom.ch [217.168.53.37]
  4	 9 ms    11 ms    11 ms  84.116.200.233
  5    10 ms    12 ms    12 ms  ch-zrh01b-ra1-ae-1.aorta.net [84.116.134.142]
  6    12 ms	 *	   12 ms  zur-1-6k.ch.eu [91.121.131.61]
  7	 *	   41 ms	 *	 fra-5-6k.fr.eu [94.23.122.145]
  8    29 ms    25 ms    26 ms  rbx-g2-a9.fr.eu [91.121.131.134]
  9	 *	    *	    *	 Request timed out.
 10	 *	    *	    *	 Request timed out.
 11   113 ms   116 ms   117 ms  bhs-g2-6k.qc.ca [198.27.73.207]
 12   111 ms   109 ms	 *	 bhs-s3-6k.qc.ca [198.27.73.142]
 13   111 ms   111 ms   111 ms  ns7000227.ip-192-99-40.net [192.99.40.106]

[Gerdskies]

whats really pissing me off is that they arent replying to tickets on this issue

[ei8ht]

FWIW I'm happy to see lower pings on my end, average lower by 30 ~ 50ms.

OTOH still getting occasional desyncs, better than before but still happening.

[RolloI]

Region : ITA
Latency before : 165-180ms
Latency now : 190-210ms
ping worse
for me too

Edited by RolloI, 31 August 2014 - 11:21 AM.

[B0oN]

After playing a bit with the new patch I saw more of the old :
-De-syncing/warping mechs
-Game freezes, which occur seemingly random
-Laser (any kind) hitreg is far off
-PPC/Gauss hitreg is not properly accepting all "hits" (not refering to crosshair´s "red-glow-on-damage fade-out time")
-Rocket hitreg of any kind is acceptable
-AC hitreg is acceptable

We need some more work in these fields please, so in other words : you know what to do with the "TestServer" soon, aye ?

[EvilCow]

May be the new data center is cheaper but cutting out a whole continent worth of customers probably it is not the best idea for business.

[Appogee]

Mine increased 9% from 219 to 239.

GG PGI.

Location: UAE.

Edited by Appogee, 31 August 2014 - 12:34 PM.

[SwalerD]

As Mokey Mot stated before, I too have premium time ticking away that I can't use. Literally can't. My ping has gone from an average of 110-118ms to a whopping 4000+ (it even capped out at around 7500 one match).It now takes around 8 seconds to register target lock and another 5-10 seconds for the missiles to fire, weaponry never hits because what I'm shooting at has either long gone or killed me.

I really wish I was kidding about the figures too, but this problem is so extreme it's not even worth playing anymore. I've sunk a fair bit of cash into this game in the form of paints, camos, cockpit items, 16 heros, 2 champs and four clanners(as well as the sarah's jenner) and, as you guys can probably guess by this being my second post, I never complain about stuff on the forums...mostly because I take game changes and glitches as par for the course. But to completely break the game for me....that's not cricket, old beans.

PGI, you owe it to me, and to every other loyal MWO fan out there, to sort this problem out FAST.

Sincerely,

Disgruntled.

[Unnatural Growth]

My ping doubled. I was always below 70 and usually between 50 and 60.

Now it's always over 100, and hovers between 110-120

Northern Central US


Way to go PGI, you found something new to screw up.

[Carlos Vinson]

LordBaconPants, on 29 August 2014 - 11:33 PM, said:

My ping has shot up quite considerably since the patch. Makes firing on the run nigh impossible

Same here. Before 65-75 now 160-180.

[WarHorseOne]

DV McKenna, on 31 August 2014 - 12:05 AM, said:

For the complainants from the Asia regions, do some traceroutes and post them.
If like another Aus based player your all being routed through Europe, that is not PGI's problem nor is it there fault, that's down to ISP and above.

(probably the first time i have defended PGI and i feel sick)

No routing through the Europe this time but still getting an in game ping around 340ms.

Spoiler

Tracing route to 192.99.109.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 12 ms 12 ms 12 ms 172.18.209.7
3 12 ms 12 ms 12 ms 172.18.65.173
4 13 ms 12 ms 13 ms TenGigE0-5-0-0.chw-edge902.sydney.telstra.net [139.130.207.81]
5 15 ms 14 ms 14 ms bundle-ether14.chw-core10.sydney.telstra.net [203.50.11.100]
6 17 ms 15 ms 15 ms Bundle-ether17.oxf-gw2.sydney.telstra.net [203.50.13.70]
7 14 ms 15 ms 15 ms bundle-ether1.sydo-core01.sydney.reach.com [203.50.13.38]
8 14 ms 15 ms 15 ms i-0-3-2-0.sydo-core02.bi.telstraglobal.net [202.84.220.189]
9 157 ms 159 ms 159 ms i-0-2-0-3.1wlt-core01.bx.telstraglobal.net [202.84.140.222]
10 157 ms 157 ms 157 ms i-0-4-0-1.eqla01.bi.telstraglobal.net [202.84.251.154]
11 157 ms 156 ms 157 ms tisparkle-peer.eqla01.pr.telstraglobal.net [134.159.61.26]
12 155 ms 155 ms 154 ms xe-11-1-0.paloalto2.pao.seabone.net [89.221.35.129]
13 221 ms 221 ms 221 ms pal-5-6k.ca.us [178.32.135.206]
14 * * * Request timed out.
15 288 ms 288 ms 288 ms 198.27.73.175
16 286 ms 287 ms 286 ms bhs-g1-6k.qc.ca [198.27.73.1]
17 286 ms 286 ms 286 ms 198.27.73.231
18 287 ms 286 ms 286 ms 192.99.109.129
Trace complete.

Spoiler

Tracing route to 192.99.109.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 13 ms 13 ms 13 ms 172.18.209.7
3 13 ms 12 ms 13 ms 172.18.65.173
4 14 ms 12 ms 13 ms TenGigE0-5-0-0.chw-edge902.sydney.telstra.net [139.130.207.81]
5 13 ms 13 ms 15 ms bundle-ether14.chw-core10.sydney.telstra.net [203.50.11.100]
6 14 ms 15 ms 19 ms Bundle-ether17.oxf-gw2.sydney.telstra.net [203.50.13.70]
7 14 ms 15 ms 18 ms bundle-ether1.sydo-core01.sydney.reach.com [203.50.13.38]
8 15 ms 15 ms 16 ms i-0-3-2-0.sydo-core02.bi.telstraglobal.net [202.84.220.189]
9 158 ms 159 ms 159 ms i-0-2-0-3.1wlt-core01.bx.telstraglobal.net [202.84.140.222]
10 157 ms 157 ms 157 ms i-0-4-0-1.eqla01.bi.telstraglobal.net [202.84.251.154]
11 156 ms 157 ms 156 ms tisparkle-peer.eqla01.pr.telstraglobal.net [134.159.61.26]
12 155 ms 155 ms 154 ms xe-11-1-0.paloalto2.pao.seabone.net [89.221.35.129]
13 * 221 ms 221 ms pal-5-6k.ca.us [178.32.135.206]
14 311 ms * * 198.27.73.177
15 289 ms * 288 ms 198.27.73.175
16 286 ms 286 ms 287 ms bhs-g1-6k.qc.ca [198.27.73.1]
17 286 ms 287 ms 289 ms 198.27.73.231
18 287 ms 288 ms 286 ms 192.99.109.129
Trace complete.

Marmon Rzohr, on 31 August 2014 - 02:33 AM, said:

Strange that I can't find an offical feedback thread for this.

Region: Central EU
Old ping: 150
New ping: 113-124

Gerdskies, on 31 August 2014 - 09:49 AM, said:

whats really pissing me off is that they arent replying to tickets on this issue

Public holiday / long weekend in Canada, I doubt we see anything remotely official even recognising this till at least Wednesday down-under time.

*Crosses fingers and waits patiently for a speedy resolution*