3 replies to this topic

[The Unstoppable Puggernaut]

Hello all,

Just looking for help/suggestions on the following issue. I believe it started happening not on this patch but the one before.

Randomly at any time (not in the mechbay), I'd get weird superlag bouts where I can hear people speaking but no mechs seem to move (although I can). Normally once a few maps this may happen. What actually happens is that the server records the last buttons I pressed during the superlag and keeps them pressed until I return; In the Spirit Bear, I died before any fighting started as I MASC'ed myself to death :\

From the recent patch I feel its happening more, one match it happened more than once, and my very last match I got kicked out. When I rejoined the match was over.

I have run the repair tool and no joy.

Nothing else in the background is running (unless it's doing so secretively).

No one else in the house is using the internet at that time.

Whenever it happens I normally hit tab to see what my ping was, and it's always lowish at 20~30. When I used to get some lag, I'd see this value increase, then come down so it was pretty obvious.

Perhaps it's not lag but packet drops?

Superlag 1:
https://youtu.be/8Aiy6ffcZMI

Superlag 2 (with disconnect)
https://youtu.be/xEDuMifLKlo

Not sure why nVidia's recording tool didnt save it at 3440x1440 but this will have to suffice.

Any ideas or help is most welcome !

[Tarl Cabot]

Posted in an archived section so it may receive fewer looks.

I take it you are actually in London?

You may want to move this to either the newest patch thread or to Workarounds.

ISP?
Wired or Wireless? If both which portion of your connection?
Brand/model of modem, router or gateway (combo modem/router)

Rebooted modem/router?

[General Solo]

Im not having such a bad experience as the OP but something is up

My avg match score dropped 50 or so points over nite

Last month Feb it was 308, so far this month its 260

feels like my weapons don't do so much damage.

Frustrating

[The Unstoppable Puggernaut]

Looks like it's a local issue for my end:

C:\Users\Sanman>tracert 192.99.109.129

Tracing route to 192.99.109.129 over a maximum of 30 hops

1 1 ms * 2 ms 192.168.0.1
2 * * * Request timed out.
3 10 ms 10 ms 9 ms haye-core-2b-xe-033-0.network.virginmedia.net [62.253.8.137]
4 * * * Request timed out.
5 15 ms 15 ms 15 ms tcl5-ic-6-ae0-0.network.virginmedia.net [62.254.85.66]
6 * * * Request timed out.
7 90 ms 84 ms 85 ms be100-1298.nwk-5-a9.nj.us [192.99.146.133]
8 90 ms 91 ms 90 ms be100-1323.bhs-g2-nc5.qc.ca [192.99.146.138]
9 * * * Request timed out.
10 93 ms 92 ms 91 ms be9-6.bhs-g5-a9.qc.ca [178.32.135.196]
11 88 ms 87 ms 90 ms 192.99.109.129

Trace complete.

--------------------------------