Jump to content

Stu Pot

  • Content count

  • Joined

  • Last visited

  1. Weird Crash on server

    Sorry for the late response. Yes this would also block/break the custom sounds on the server. Was not to bad of an option to me tbh, yet it is the only approach to have atleast some sort of "antihack" in this case. Source: https://forums.bistudio.com/forums/topic/77100-arma-2-dedicated-server-maxcustomfilesize/ In ArmA2OA.cfg language="Spanish"; adapter=-1; 3D_Performance=93750; Resolution_Bpp=32; MaxCustomFileSize = 1; //dunno if it works, setting it on one worked for me, if possible try MaxCustomFileSize = 0; should disable it completly --------------------------------------------------------- Source: https://community.bistudio.com/wiki/basic.cfg Other Tuning Options ! NOTE: See the talk page for some more background info by Suma. MaxCustomFileSize=<size_in_bits>; Users with custom face or custom sound larger than this size are kicked when trying to connect. Note The greatest level of optimization can be achieved by setting the MaxMsgSend and MinBandwidth parameters. For a server with 1024 kbps we recommend the following values: MaxMsgSend = 256; MinBandwidth = 768000;
  2. Weird Crash on server

    Set custom sound file size to 0 or 1. That might prevent the issue. Even if you would ban the guy executing this, he is still able to achieve client/server crashes with this.