This has always happened on Arma servers in the past. Probably not a big deal if you are taking the server down anyway - so long as the persistence files aren't corrupted.

Attached RPT logs.

Been sitting all day with this issue. Tried verrifying files, reinstalled the game twice and yet the issue remains. Incredibly frustrating and hopefully this will be resolved shortly or else i'll probably throw my computer out the window.

This is STILL an issue in 1.14 Experimental (and of course 1.13 Stable).

I have also experienced the same issue with the experimental servers. They become higher latency when the population in the server increases, and is noticeable during game when you try to open doors or perform other actions like eating you will see the action being performed 20-30 seconds later or you will not see the action performed at all and that's how you know sometimes you are disconnected from the server. Also, you will get an error message if you try to connect back to the server. I have found this to happen on Experimental Server LA when the population is over 30.

I got the same issue too, it’s been 3 days I probably won’t be able to play DayZ again

@AmishZed I don't see the issue lol. You're inside, hes outside, footsteps shouldn't be heard clearly through the wall of the house.
Also to mention you couldn't really hear it cause your footsteps are loud and the waves clashing in the background.
The guy could've been crouch walking/running upto the house.

Hello! On Namalsk today I was killed by a player and I wasn't able to hear any approaching footsteps (which I normally do in a situation like this). I was told about this ticket so I just wanted to share a clip in case it helps. This was on the ZERO Namalsk Server.

foud a solution: ditch all your gear, including clothes and shoes and then retry to open a door. It worked with me

I can confirm the same on my Linux server running Ubuntu 20.04. The settings for:

• timeStampForm
• logAverageFPS
• logMemory
• logPlayers

If someone has the same problem on AMD lags in cities and towns, upload a video here - let the developers see
and turn to this two year old unsolvable problem
and fix it

Hi Geez,

Our gaming group has been noticing this while some can hear the howl and some not. Sometime this can vary, the one last time who didn't hear hears and way around.
This is a bit confusing.

You can close this issue, I believe your first update to 1.14 experimental has resolved the problems.

Yes! That's the one. It's not always the same sound either, not for me anyway, sometimes it's still the 'normal' sound too. Didn't realise someone had already addressed it :)

BE report still wrong player Pings. and this is a global issue.

Sometimes the login timer starts, all is fine and then I see an error "BattlEye not responding" and again cannot connect.

Ok. Restarting + reconnecting both CLient and Server sometimes helps. No steam or launcher restarts.
Takes from 3 to 6 restarts. But at least it is a workaround.

yea, i had to join another server and walk back to my base to get out. Still won't open today.

It is different then before for sure.
Here is an example of how it sounds atm:
https://clips.twitch.tv/DoubtfulScrumptiousHummingbirdCopyThis-vEhRMNAWQn_EC2d_

same problem here, i've already deleted the dayz folder from documents but the problems remains, now i'm locked up in my own base

Same here, it has been really painfull to play DayZ since 1.13 was released!!!

also I want to add that it sometimes says connection to host has been lost

Similar crash here, except it happened for no apparent reason after about 1h runtime:

We had a massive spike in reports of this with 1.13. Battleye seems more sensitive to the time it takes clients to load in, and it's causing people with older or slower PC's to have issues they didn't have prior to 1.13.

I have the same problem sometimes.

Hello chucky20097.
Does this occur on the vanilla version of the game without any mods running when connecting to official servers? Also, do you have this problem with the standard dayz launcher?
Regards,
Geez

this issue still persist in 1.13

@Geez Hi, the issue is still present on todays experimental version. It appears that the bug affects the magazine, that is attached to the gun when logging in.

This issue has happened to me yesterday and it is still happenning. I locked a door with a lockpick, logged out and when i got back in it won't let me unlock it.

This happened to me today on the right side of the Nadbor firestation, inside the compound.

This issue still exist so the fix was not in the next update. Locked inside a one door house after using lockpick. logged back in and now door is still locked and door wont open