Do you know if any other players on the server are having the same issue? If not, sounds like a problem with your internet connection. You could try Alt+Tabbing out and checking if you can view any web pages in your browser while it's counting down.

Yes, other players are experiencing this aswell. When its counting down i can still use steam web browser etc. So it's not my internet connection, also i believe i got this error since the game was last updated (yesterday?)

And.

All the servers i join are with a low ping for me, so that isnt the problem i guess.

Does it just disconnect you or does the server crash?

It just disconnects me.. because right after that i can look up the server in the server list again and join. 10 mins later i get disconnected again though.

AND.

I have this on every server i have played today, i've tried to switch some servers to see if the problem would go away, but it didn't.

If your modem's connection drops, and reconnects with another IP (dynamic IP), you wont be able to reconnect via waiting. You'll have to do as you said, that being, exit to server list and rejoin.

Whilst playing, have a cmd prompt open running 'ping google.com -t'

if it shows any packet drop, then your connection is dropping, and that's why you're being disconnected.

It can be either your connection or server hoster one.

Okay, i tried Radioman's method, i got NO MESSAGE RECEIVED error again, So i checked the cmd prompt that i had running "ping google.com -t". It didn't drop, so my connection wasn't dropping. So i don't think this is a problem with my connection.

And as a reply to Kid18120: Do you think every server has those problems? because i've tried like 7 different servers already. And the no message received error occured at all of them.

Then it's a server-side problem.

I (as well as many others) can play just fine for hours in MP and i have a Thomson router, well known for it's crappy stability :P

EDIT: Didn't see your second comment. Yes actually it can easily be (refer to what i wrote above) for multiple reason, the main one being there are no dedicated servers, yet.

EDIT2: Also, ArmA drops your server-link as soon as you have even the smallest connectin drop (even for like half a second), that may be the issue. Your connection drops for an instant but in the time you do the ping test it has recovered.

I'd say it's because the servers have updated to the latest game version, and they've not updated their missions for the class name change in the Ilfrit vehicles, so, they're probably just crashing, restarting, everyone piles back in and starts playing like nothing happened.

Who knows...

If you don't change the class name you can't even load the mission.
He sais aftter 10 mins (i assume of playing) so i guess the server is able to run the mission

Indeed, after about 10 minutes of playing. Tried some different game modes than Wasteland, still the same error occuring.. is there any way i can fix this? Or am i just going to have to wait for a new update?

EDIT1: And i didnt have the problem yesterday. Yesterday i played on a few servers for a few hours without a problem.

I'm also disconnecting after minutes of gameplay on any server after the update. My internet connection to my shell ,TS3 and anything else stays up while Arma3 loses connection to server.

same issue here

I have the same issue, it got even worse after the new update :/

havent been able to play a mp game today. I keep losing connection. I thought it was just me but on 3 servers, the admin announced that the server was unstable and was going to crass, or they were trying to run tests because they couldnt keep it up.

This is a server crash issue, this is a duplicate of this post here: http://feedback.arma3.com/view.php?id=5956

The issue is that the server crashes every 10-30 minutes. The reason why they come back up is that servers like mine are on auto-restart so they come back online if they crash.

@krunch, I have played at over atleast 10 different servers today, they ALL had the same problem. Do you think this is coincidence?

Not a coincidence, the issue started after this morning update.

#5956