Extreme lag recently, Day Z/Arma 2 specific

[Belisk 0]

Hey Guys I have been playing Day Z for months with usually very little latency problems. Naturally it would depend on the server and you would get a few that were not optimal but recently I have been getting solid yellow chains with latencies of 1k+ on any server except Australian ones which still give me in the several hundreds, significantly higher than previously.

The strange thing about this is that it only seems to affect Day Z. I recently ran an isolation test including changing router and while I no longer get disconnected for ping my ping is so consistently high I don't understand why I don't. Furthermore when I play Day Z other sites are significantly slower and latency baloons out as well. I cannot see why all of a sudden Day Z should start causing extreme congestion for me even after checking my home network.

Furthermore other international and national games do not suffer this. For example WoW does not. Furthermore in performing ping tests I get very little jitter to both national and international web hosts. For example to mmo-champion.com my variance was 9ms with the average 1ms higher than the minimum after 100 packet sent. Nationally the variance was even smaller.

Any ideas why Day Z would be behaving in such a way?

[Belisk 0]

Pinging 85.24.144.164 with 32 bytes of data:

Reply from 85.24.144.164: bytes=32 time=328ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=322ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

[...................]

Reply from 85.24.144.164: bytes=32 time=322ms TTL=47

Reply from 85.24.144.164: bytes=32 time=323ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=322ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=322ms TTL=47

Reply from 85.24.144.164: bytes=32 time=322ms TTL=47

Reply from 85.24.144.164: bytes=32 time=323ms TTL=47

Reply from 85.24.144.164: bytes=32 time=320ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=322ms TTL=47

Reply from 85.24.144.164: bytes=32 time=323ms TTL=47

Reply from 85.24.144.164: bytes=32 time=322ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=322ms TTL=47

Reply from 85.24.144.164: bytes=32 time=324ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=322ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=322ms TTL=47

Reply from 85.24.144.164: bytes=32 time=323ms TTL=47

Reply from 85.24.144.164: bytes=32 time=323ms TTL=47

Reply from 85.24.144.164: bytes=32 time=322ms TTL=47

Reply from 85.24.144.164: bytes=32 time=322ms TTL=47

Reply from 85.24.144.164: bytes=32 time=322ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=322ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=322ms TTL=47

Reply from 85.24.144.164: bytes=32 time=322ms TTL=47

Reply from 85.24.144.164: bytes=32 time=321ms TTL=47

Reply from 85.24.144.164: bytes=32 time=327ms TTL=47

Reply from 85.24.144.164: bytes=32 time=322ms TTL=47

Ping statistics for 85.24.144.164:

Packets: Sent = 115, Received = 115, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 320ms, Maximum = 345ms, Average = 322ms

Sometimes a test like this may show minor packet loss ~1%. Although with ICMP requests most router depriotise these so it does not surprise me. It could still be a factor but packet loss would theoretically show up differently to a constant yellow chain and 1k+ latency without noticeable in game rubber banding.

Also for those wondering why 300ms, its because I am in Australia pinging a European server. Ping to other closer server appear normal also, however, it is the ingame counter that reports stupendously high latency.

Edited September 29, 2012 by Belisk

[Duckimus Maximus 2]

You appear knowledgeable enough to have tried this already, but I'm suggesting it anyway, have you tried port forwarding?

Do you know others with the same ISP, and do they share the same problem, or can you replicate it if you test it on their systems.

The ISP where I worked at recorded a similar issue once, I can't remember what the root cause was, or how it was solved, but the error was on our network at the time.

If you can replicate the error on another line connected to the same ISP you should call them. Users at the time had a lot of issues connecting to a single French provider.

It took ages before complaints rolled in because the issue was so isolated.

It could also be a router issue, I assume there is a reason why the router you tested with isn't in normal use, and if the assumption of it being broken is correct, you could try another router.

One that's confirmed to work on your isp's network.

If you can't replicate it, and after testing another router (or is it a modem with LAN) you'd need to look for something on your pc.

Edited October 1, 2012 by Duckimus Maximus

[Belisk 0]

Port forwarding has been done.

Do not know anyone on the same ISP network that is experiencing these issues. It is an intermittent issue as well.

As previously said I have run an isolation test including fully replacing a modem/router combination. Also this happens on national and international servers on 3 continents so I doubt it is my ISP. I am personally leaning towards a computer problem, but what is the question. being so specific to just dayz and the yellow chain/ latency reporting issue it seems strange to me my ping is reported so high and yet I do not get disconnected. I am thinking it may be a battleye issue.

When running independant ping test over ICMP it seems it does not occur, it is merely the in game ping counter that reports such a problem.

Edited October 1, 2012 by Belisk

[Belisk 0]

I am trying to verify game content through steam, may help.

EDIT: no change

Edited October 1, 2012 by Belisk

[Belisk 0]

DELETED

Edited October 1, 2012 by Belisk

[Belisk 0]

Checked the following

* Game integrity

* Virus's

* Port Forwarding

* UPNP disabled (reports of it affecting performance)

* Anti Virus's disabled, seemingly no effect although this is an intermittent issue making it harder to diagnose.

[Belisk 0]

I bit the bullet and did a full reinstall, wish me luck.

[Belisk 0]

Battleeye giving me a corrupted memory error #29 tipped me off it might be battleeye so I re-installed battleeye through steam and no more lag!

EDIT: lag seems to have returned. damn this shit.

Edited October 4, 2012 by Belisk