35 replies to this topic

[elbloom]

EarlGrey83, on 28 February 2013 - 05:05 AM, said:

Same here, since tuesday. Ping is hopping from my ~120 normally to up to 250. Playing from Hamburg, Germany.

Could be many non MWO related reasons for this, still would be nice to get this overlooked.

http://www.teltarif....nd1/1316-7.html

Bist bestimmt am Telekom Backbone ! Dem kann man nur mit ausgewählten ISPs entkommen, z.B. Kabelanbieter wenn ich da richtig liege.
1&1 und andre grosse Deutsche Anbieter benutzen alle den Telekom Backbone.

Im Artikel oben steht kurzgesagt, wie die Amis aufgrund der unfairen Belastung des Transatlantikkabels, einfach Datenpakete "unter den Tisch" fallen lassen um für fairness zu sorgen.
Das ist dann im Spiel unerträglich. Zuviel Packetloss führt zu warping etc.

Die Beschwerde wurde auch am letzten Dienstag verfasst.... passt genau in Deinen Zeitrahmen

Edited by elbloom, 28 February 2013 - 05:19 AM.

[Hawks]

elbloom, on 28 February 2013 - 05:02 AM, said:

It must be terrible to have the IQ of a shoebox and be completely unable to detect a joke.

You have my sympathy

[MonkeyCheese]

elbloom, on 28 February 2013 - 05:08 AM, said:

tracert www.mwomercs.com , find responsible hop/ip, email support from your ISP, give them the tracert, don´t give up hope ^^

the more i read what others say in the various threads the more it seems to me atleast that it could be a problem caused by one of the last patches

[Ghogiel]

elbloom, on 28 February 2013 - 05:08 AM, said:

tracert www.mwomercs.com , find responsible hop/ip, email support from your ISP, give them the tracert, don´t give up hope ^^

traceroute this address> 70.42.29.65

[elbloom]

Routenverfolgung zu 70.42.29.65 über maximal 30 Abschnitte

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 7 ms 10.208.127.254
3 7 ms 7 ms 8 ms 10.72.234.254
4 8 ms 7 ms 7 ms 192.168.230.15
5 10 ms 8 ms 7 ms 192.168.230.75
6 26 ms 23 ms 23 ms 82.82.1.189
7 29 ms 23 ms 23 ms 92.79.211.206
8 21 ms 27 ms 23 ms 64.213.33.209
9 124 ms 123 ms 123 ms 64.214.150.82
10 123 ms 123 ms 123 ms border1.te7-1-bbnet1.tor001.pnap.net [70.42.24.132]
11 125 ms 124 ms 125 ms 70.42.29.65

Ablaufverfolgung beendet.

[jay35]

Wispsy, on 27 February 2013 - 06:41 AM, said:

My ping is not really much different but I keep teleporting and my mech changes directions randomly at times which is quite frustrating. I am in England.

I've been getting that quite a bit here in the US since the last patch as well.

I've noticed times where the game decides I'm not where it's been showing me I am, and it warps me several hundred meters away, often into the midst of enemy fire and I'm either already dead or near dead, no thanks to anything I actually did. Some weird netcode interpolation going on there. Other times it comes across as being one-shot killed by an enemy, which is supposed to be impossible but has happened 4-5 times since the last patch for me, having never happened even once prior to that patch.

Combine that with the other problem that's been significant since the last patch, which is the collision issue being stuck against an enemy mech and any other non-passable object like a building or cliff face at the same time, will cause you to repeatedly warp 1 second backward in time and be unable to extricate yourself from this loop unless somehow either you or other other mech dies.

[Django Jr]

elbloom, on 27 February 2013 - 02:03 PM, said:

yeah file a support ticket.... but with your ISP, cause this is not PGIs fault

ping stable, packetloss 0,01%, servers are good.

That's what I'm trying to find out. No sense in complaining before you know who to complain to.

[Ghogiel]

Django Jr, on 28 February 2013 - 06:44 AM, said:

That's what I'm trying to find out. No sense in complaining before you know who to complain to.

ping the server at that address I posted earlier for starters.

[Django Jr]

Well, I did both traceroutes suggested... For your information:


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

1 7 ms 9 ms 7 ms 80-219-112-1.dclient.hispeed.ch [80.219.112.1]
2 28 ms 10 ms 10 ms 217-168-61-45.static.cablecom.ch [217.168.61.45]
3 13 ms 9 ms 9 ms 84.116.202.241
4 9 ms 19 ms 10 ms ch-zrh01b-ra1-ae-9-0.aorta.net [84.116.134.22]
5 10 ms 23 ms 9 ms 213.46.171.42
6 114 ms 111 ms 113 ms xe-5-2-0.tor10.ip4.tinet.net [141.136.108.189]
7 119 ms 119 ms 120 ms internap-gw.ip4.tinet.net [77.67.71.62]
8 118 ms 120 ms 119 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.196]
9 * * * Request timed out.




Tracing route to 70.42.29.65 over a maximum of 30 hops

1 9 ms 8 ms 11 ms 80-219-112-1.dclient.hispeed.ch [80.219.112.1]
2 10 ms 9 ms 11 ms 217-168-61-45.static.cablecom.ch [217.168.61.45]
3 17 ms 11 ms 15 ms 84.116.202.241
4 9 ms 9 ms 9 ms ch-zrh01b-ra1-ae-9-0.aorta.net [84.116.134.22]
5 27 ms 11 ms 9 ms 213.46.171.42
6 115 ms 119 ms 118 ms xe-5-2-0.tor10.ip4.tinet.net [141.136.108.189]
7 120 ms 125 ms 129 ms internap-gw.ip4.tinet.net [77.67.71.62]
8 120 ms 121 ms 121 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.196]
9 123 ms 123 ms 124 ms 70.42.29.65

Trace complete.

Ghogiel, on 28 February 2013 - 06:47 AM, said:

ping the server at that address I posted earlier for starters.

100% packet loss

[elbloom]

the server can´t be pinged, it doesn´t respond to ICMP - thus 100% packet loss if only ICMP packets are requested (what a ping does).

the server can only be tracert and the last hop won´t respond to ping.

Django, your traceroute looks perfectly fine, you should be able to play without any kind of jerky movement (at the moment).

Edited by elbloom, 28 February 2013 - 07:27 AM.

[Cebi]

I've been convinced that my internet is going the way of the dodo. But seems others are having the exact same issue!

Problems started recently; ping suddenly increasing making gameplay rather irritating. I'm in the UK.

Restarting my router/modem seems to work... though sometimes takes several cycles.

My ISP is plusnet; just in case this is an ISP routing issue!

[Django Jr]

elbloom, on 28 February 2013 - 07:26 AM, said:

the server can´t be pinged, it doesn´t respond to ICMP - thus 100% packet loss if only ICMP packets are requested (what a ping does).

the server can only be tracert and the last hop won´t respond to ping.

Django, your traceroute looks perfectly fine, you should be able to play without any kind of jerky movement (at the moment).

I pinged 70.42.29.65, the other server he gave me, not mwmercs.com. I assume it's an other server in the area. Made a traceroute for both. as expected mwmercs.com got a timeout.

well, I tried after the tests... Ping jumped again to over 800 for a short time. It stabilized around 500. It was more like a jerky warping. I wasn't a great help for the team...

Edited by Django Jr, 28 February 2013 - 07:58 AM.

[M X Striker]

I'll throw my hat into this ring as well, although even my "bad" ping is better than most. I'm here on the East Coast of the US. My normal ping is around 21. Since the last patch, it's moved to 38. Yes, I know, it's still pretty darned good, but I've started seeing more rubberbanding and such which is not.

[Ghogiel]

Django Jr, on 28 February 2013 - 07:52 AM, said:

I pinged 70.42.29.65, the other server he gave me, not mwmercs.com. I assume it's an other server in the area. Made a traceroute for both. as expected mwmercs.com got a timeout.

70.42.29.65 is the address support game me, and I assume that is the sever the game is run on.

[Cebi]

Ok so my ping is now unreliable again. Seems to happen every evening. Anyone else getting it about now every day?

[Gilwen]

Trying to ping the www.mwomercs.com and getting blocked, but when pinging the address 70.42.29.74 I get through.
I'm using PingPlotter to sort my connetivity issues, but for some reason it won't show the addresses between 2nd jump and the final destination.
Anyway, here are my pings