search

A3Wasteland / ArmA3_Wasteland.Altis

A3Wasteland is a survival sandbox mission for Arma 3 where two teams and independent players fight for survival. Built in collaboration between GoT, TPG, KoS, 404Games, and others.
http://a3wasteland.com
GNU Affero General Public License v3.0
102 stars 184 forks source link

independents stuck on receiving data #178

Closed bulldogzxz closed 9 years ago

bulldogzxz commented 10 years ago

So i'm an independent trying to get on my usual wasteland server a3wasteland and its stuck on receiving data it has never done this before and i have been playing regularly for months any ideas?

AgentRev commented 10 years ago

The truth is that there's absolutely no relevant information available about this problem. It has been plaguing Arma for years, but nobody knows why, nobody knows what causes it to happen, and nobody knows how to fix it.

AgentRev commented 10 years ago

Although, I think I remember somebody saying that it happens a lot when there are more than 32 indies in the server, but I'm not certain.

wiking-at commented 10 years ago

i had some strange situations were player spawned "in" the headless client character. i think the reason was that the player-id wasn't correctly transfered to the server because of high network load/low server ticks. could be a server load thing. the logs showed "no player" instead of the playeruid.

wiking-at commented 10 years ago

i think this happens when lots of players joining the server simultanously before the server is fully started. i had a restart yesterday where 72 players stormed the server and some indi's couldn't join. even restarting arma on the client side didn't help - they were always stuck in "receiving data".

i had to restart the server and lock it after start - then let players join in slowly to get rid of the problem.

l0dac commented 10 years ago

http://www.ibattle.org/Downloads/Plugins/ConnectionLimiter.zip

If using iBattle, this will prevent the storming of users on restart

AgentRev commented 10 years ago

We had the same problem on one of lodac's servers with Blufor, and even Opfor just before restarting. I tried to diagnose it, but to no avail...

wiking-at commented 10 years ago

thanks for the info and workaround. if this keeps being a problem i'll use the connectionlimiter.

wiking-at commented 10 years ago

i used the connection limiter with quite strict settings now (5 players in 10 seconds - 20 sec lock)- and still some players got the problem. at least if i push a new mission and therefore there is much network traffic on restart. players found a workaround - if they use one of my lower indi slots it starts working again.

therefore i think it might have to do with the groups -> i have two groups for indi's set op on our server (opfor removed, copy of indi group added).

codexGW commented 9 years ago

This still happens a lot on my server. I found that the connection limiter really helps if you set it high enough. I have it set pretty extreme now, but I think its a better option then removing opfor.

set sample time in sec. samptime = 15 set how long the server will be locked.. locktime = 45 set limit of connections. consec = 3

It still happens about once a week or so, but not after each restart if the server is flooded with 20+ connections.