Basic.cfg issues with latest build

[chris5790 24]

Hey,

 

since 1.54 we have issues with our server. We have 90 Slots (which ran good so far) but if the player count rises (above 80 players) all players get kicked because of "Ping too high".

Our server has a normal 1Gbp/s connection (OVH). Speed test results are fine too (800 mbit/s up and down). However, I'm really frustrated as nobody can't help me. Our Server doesn't has really heavy scripted load (loops, threads, etc). All DB stuff is handled by a hc. Especially due to the low scripted load this is a strange behaviour I've never seen before.

 

Our basic.cfg:

MinBandwidth=107374182;

MaxBandwidth=524288000;
MaxMsgSend = 384;
MaxSizeGuaranteed=384;
MaxSizeNonguaranteed=256;
MinErrorToSend = 0.005;
MinErrorToSendNear = 0.05;
MaxCustomFileSize = 0;
class sockets {maxPacketSize = 1400;};

I already had a look at these tutorials:

 

https://community.bistudio.com/wiki/basic.cfg

https://forums.bistudio.com/topic/147591-tutorial-server-bandwidth-optimisation/

 

I heard of a startup paramterer writing a network log which could help to identify the problem. If somebody knows more about it help would be appreciated.

 

 

Thanks for your help!

 

Best regards

 

[SavageCDN 231]

I believe you are looking for the -netlog parameter

 

https://community.bistudio.com/wiki/Arma_3_Startup_Parameters

[chris5790 24]

Thanks! Do you have any other tips for me regarding this bandwith issue?

[SavageCDN 231]

Check these threads for some good info regarding basic.cfg:

 

https://www.reddit.com/r/armadev/comments/2zkw7p/understanding_basiccfg/

https://forums.nfoservers.com/viewtopic.php?t=11674

 

The most players I've ever had on a server in A3 is approx 50.. so no experience with that high of a player count.  Trial and error might be your only solution :)