Arma 3: Basic Server Config File - Revision history

R3vo: Added note about String Number Formats and linked to the page

2025-06-22T13:47:30Z

Added note about String Number Formats and linked to the page

← Older revision		Revision as of 15:47, 22 June 2025
Line 1:		Line 1:
	{{TOC\|side}}		{{TOC\|side}}
	{{Navbox/A3ServerSetup}}		{{Navbox/A3ServerSetup}}


	{{Feature\|arma2oa\|This page is about '''{{arma3}}''' basic server configuration. For previous titles, see [[Arma 2: Basic Server Config File]].}}		{{Feature\|arma2oa\|This page is about '''{{arma3}}''' basic server configuration. For previous titles, see [[Arma 2: Basic Server Config File]].}}
			{{Feature\|informative\|Some config entries or script parameters support receiving numbers as a string. These string formats are Case-Sensitive! See {{Link\|Number#String_Number_Formats\|String Number Formats}}}}

	This article deals with the '''basic.cfg''', the name means nothing, and can be called anything. The real name is determined by the [[Arma 3: Startup Parameters\|-cfg]] command line option when launching the dedicated server or the game executable - in other words '''it also works for clients'''. When you do not provide a name, the default {{hl\|Arma3.cfg}} file is loaded located in the user profile folder.		This article deals with the '''basic.cfg''', the name means nothing, and can be called anything. The real name is determined by the [[Arma 3: Startup Parameters\|-cfg]] command line option when launching the dedicated server or the game executable - in other words '''it also works for clients'''. When you do not provide a name, the default {{hl\|Arma3.cfg}} file is loaded located in the user profile folder.

Lou Montana: Text replacement - "{{Table/A3ServerSetup}}" to "{{Navbox/A3ServerSetup}}"

2024-05-04T22:24:48Z

Text replacement - "{{Table/A3ServerSetup}}" to "{{Navbox/A3ServerSetup}}"

← Older revision		Revision as of 00:24, 5 May 2024
Line 1:		Line 1:
	{{TOC\|side}}		{{TOC\|side}}
	{{~~Table~~/A3ServerSetup}}		{{Navbox/A3ServerSetup}}

Lou Montana: Some wiki formatting

2023-01-05T12:41:26Z

Some wiki formatting

← Older revision		Revision as of 14:41, 5 January 2023
Line 49:		Line 49:
	</syntaxhighlight>		</syntaxhighlight>
	\| {{hl\|1400}}		\| {{hl\|1400}}
	\| Maximal size of packet sent over network. This '''can be set for both''' client-to-server and server-to-client(s) independently''! {{Feature\|important\|Only use in the case your router or ISP enforces lower packet size and you have connectivity issues with the game.}} ''Desync might happen if used '''MaxSizeGuaranteed/MaxSizeNonguaranteed values over the maxPacketSize'''.		\| Maximal size of packet sent over network. This '''can be set for both''' client-to-server and server-to-client(s) independently! {{Feature\|important\|Only use in the case your router or ISP enforces lower packet size and you have connectivity issues with the game.}} Desync might happen if used '''MaxSizeGuaranteed/MaxSizeNonguaranteed values over the maxPacketSize'''.
	\|-		\|-
	\| {{hl\|c= MaxCustomFileSize = 1024}} \|\| {{hl\|UNKNOWN}} \|\| Users with custom face or custom sound larger than this size are kicked when trying to connect.		\| {{hl\|c= MaxCustomFileSize = 1024}} \|\| {{hl\|UNKNOWN}} \|\| Users with custom face or custom sound larger than this size are kicked when trying to connect.

Lou Montana: Text replacement - "{{ExternalLink|" to "{{Link|"

2023-01-04T15:22:22Z

Text replacement - "{{ExternalLink|" to "{{Link|"

← Older revision		Revision as of 17:22, 4 January 2023
Line 38:		Line 38:
	* When using MinErrorToSend alone, for small values of distance (d) the frequency of high errors (E) would cause excessive network messages that are not necessary but could negatively impact FPS.		* When using MinErrorToSend alone, for small values of distance (d) the frequency of high errors (E) would cause excessive network messages that are not necessary but could negatively impact FPS.
	* Too large of a value for METSN can prevent timely desirable network update messages which can result in units appearing to "warp"		* Too large of a value for METSN can prevent timely desirable network update messages which can result in units appearing to "warp"
	{{~~ExternalLink~~\|link= http://forums.bistudio.com/showthread.php?125396-Arma-2-OA-beta-build-84984&p=2103305&highlight=minerrortosend#post2103305\|text= Detailed explanation of METS and METSN by Suma}}		{{Link\|link= http://forums.bistudio.com/showthread.php?125396-Arma-2-OA-beta-build-84984&p=2103305&highlight=minerrortosend#post2103305\|text= Detailed explanation of METS and METSN by Suma}}
	\|-		\|-
	! colspan="3" \| Networking Tuning Options		! colspan="3" \| Networking Tuning Options

Lou Montana: Some wiki formatting

2022-07-27T11:58:38Z

Some wiki formatting

← Older revision		Revision as of 13:58, 27 July 2022
Line 77:		Line 77:
	MaxMsgSend = 256;		MaxMsgSend = 256;
	MinBandwidth = 768000;		MinBandwidth = 768000;
	While connected to the dedicated server, you can use the [[Multiplayer Server Commands\|admin command]] {{ic\|#monitor}} to monitor server resource usage. (You have to be logged in as or voted as game admin to do this.) The server never runs at more than 50 fps. When running slower, it always uses all available CPU processing power to maintain the smoothest possible gameplay. When running at less than 20 fps, you can consider the server overloaded – the mission currently played is probably too complex for given server. If you see the server is not using bandwidth that it could use, you can try increasing values ''MaxMsgSend'' and ''MinBandwidth''.		While connected to the dedicated server, you can use the [[Multiplayer Server Commands\|admin command]] {{hl\|#monitor}} to monitor server resource usage. (You have to be logged in as or voted as game admin to do this.) The server never runs at more than 50 fps. When running slower, it always uses all available CPU processing power to maintain the smoothest possible gameplay. When running at less than 20 fps, you can consider the server overloaded – the mission currently played is probably too complex for given server. If you see the server is not using bandwidth that it could use, you can try increasing values ''MaxMsgSend'' and ''MinBandwidth''.

	----		----

Lou Montana: Fix

2021-11-15T23:27:12Z

Fix

← Older revision		Revision as of 01:27, 16 November 2021
Line 27:		Line 27:
	\| {{hl\|c= MinBandwidth = 131072}} \|\| {{hl\|131072}} \|\| Bandwidth the server is guaranteed to have (in bps). This value helps server to estimate bandwidth available. Increasing it to too optimistic values can increase lag and CPU load, as too many messages will be sent but discarded.		\| {{hl\|c= MinBandwidth = 131072}} \|\| {{hl\|131072}} \|\| Bandwidth the server is guaranteed to have (in bps). This value helps server to estimate bandwidth available. Increasing it to too optimistic values can increase lag and CPU load, as too many messages will be sent but discarded.
	\|-		\|-
	\| ~~<tt>~~MaxBandwidth = 200000 \|\| {{hl\|UNKNOWN}} \|\| Bandwidth the server is guaranteed to never have (in bps). This value helps the server to estimate bandwidth available.		\| {{hl\|c= MaxBandwidth = 200000}} \|\| {{hl\|UNKNOWN}} \|\| Bandwidth the server is guaranteed to never have (in bps). This value helps the server to estimate bandwidth available.
	\|-		\|-
	\| {{hl\|c= MinErrorToSend = 0.001}} \|\| {{hl\|0.001}} \|\| Minimal error to send updates across network. Using a smaller value can make units observed by binoculars or sniper rifle to move smoother at the trade off of increased network traffic.		\| {{hl\|c= MinErrorToSend = 0.001}} \|\| {{hl\|0.001}} \|\| Minimal error to send updates across network. Using a smaller value can make units observed by binoculars or sniper rifle to move smoother at the trade off of increased network traffic.

Lou Montana: Text replacement - "\{\{hl\|([a-zA-Z0-9\. _"\\'-]+=[a-zA-Z0-9\. _"\\'-]+)\}\}" to "{{hl|c= $1}}"

2021-11-15T22:59:05Z

Text replacement - "\{\{hl\|([a-zA-Z0-9\. _"\\'-]+=[a-zA-Z0-9\. _"\\'-]+)\}\}" to "{{hl|c= $1}}"

Lou Montana: Text replacement - "`([a-zA-Z0-9\. _"\\'=-]+)<\/tt>" to "{{hl|$1}}"`

2021-11-15T22:57:15Z Text replacement - "<tt>([a-zA-Z0-9\. _"\\'=-]+)<\/tt>" to "{{hl|$1}}" ← Older revision Revision as of 00:57, 16 November 2021 Line 19: Line 19: ! Parameter !! Default !! Description ! Parameter !! Default !! Description |- |- | <tt>MaxMsgSend = 128</tt> || {{hl|128}} || Maximum number of packets (aggregate messages) that can be sent in one simulation cycle ("frame"). Increasing this value can decrease lag on high upload bandwidth servers. | {{hl|MaxMsgSend = 128}} || {{hl|128}} || Maximum number of packets (aggregate messages) that can be sent in one simulation cycle ("frame"). Increasing this value can decrease lag on high upload bandwidth servers. |- |- | <tt>MaxSizeGuaranteed = 512</tt> || {{hl|512}} || Maximum size (payload) of guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Guaranteed packets (aggregate messages) are used for non-repetitive events like shooting. | {{hl|MaxSizeGuaranteed = 512}} || {{hl|512}} || Maximum size (payload) of guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Guaranteed packets (aggregate messages) are used for non-repetitive events like shooting. |- |- | <tt>MaxSizeNonguaranteed = 256</tt> || {{hl|256}} || Maximum size (payload) of non-guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Non-guaranteed packets (aggregate messages) are used for repetitive updates like soldier or vehicle position. Increasing this value may improve bandwidth requirement, but it may increase lag. | {{hl|MaxSizeNonguaranteed = 256}} || {{hl|256}} || Maximum size (payload) of non-guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Non-guaranteed packets (aggregate messages) are used for repetitive updates like soldier or vehicle position. Increasing this value may improve bandwidth requirement, but it may increase lag. |- |- | <tt>MinBandwidth = 131072</tt> || {{hl|131072}} || Bandwidth the server is guaranteed to have (in bps). This value helps server to estimate bandwidth available. Increasing it to too optimistic values can increase lag and CPU load, as too many messages will be sent but discarded. | {{hl|MinBandwidth = 131072}} || {{hl|131072}} || Bandwidth the server is guaranteed to have (in bps). This value helps server to estimate bandwidth available. Increasing it to too optimistic values can increase lag and CPU load, as too many messages will be sent but discarded. |- |- | <tt>MaxBandwidth = 200000 || {{hl|UNKNOWN}} || Bandwidth the server is guaranteed to never have (in bps). This value helps the server to estimate bandwidth available. | <tt>MaxBandwidth = 200000 || {{hl|UNKNOWN}} || Bandwidth the server is guaranteed to never have (in bps). This value helps the server to estimate bandwidth available. |- |- | <tt>MinErrorToSend = 0.001</tt> || {{hl|0.001}} || Minimal error to send updates across network. Using a smaller value can make units observed by binoculars or sniper rifle to move smoother at the trade off of increased network traffic. | {{hl|MinErrorToSend = 0.001}} || {{hl|0.001}} || Minimal error to send updates across network. Using a smaller value can make units observed by binoculars or sniper rifle to move smoother at the trade off of increased network traffic. * Example: A unit 1km (distance d = 1km) from the player with MinErrorToSend = 0.001 (METS = 0.001) would send an update when that unit moves 50m (error value E = 50). * Example: A unit 1km (distance d = 1km) from the player with MinErrorToSend = 0.001 (METS = 0.001) would send an update when that unit moves 50m (error value E = 50). * Formula: d = sqrt[(20E)/METS] ; 1000 = sqrt[(20E)/0.001] -> E = 50 * Formula: d = sqrt[(20E)/METS] ; 1000 = sqrt[(20E)/0.001] -> E = 50 Line 35: Line 35: * When the error value (E) between the master copy of an object (whoever "owns" the object) and a client's perceived/simulated copy of the same object >= MinErrorToSend (METS), a network update message will be sent for it. * When the error value (E) between the master copy of an object (whoever "owns" the object) and a client's perceived/simulated copy of the same object >= MinErrorToSend (METS), a network update message will be sent for it. |- |- | <tt>MinErrorToSendNear = 0.01</tt> || {{hl|0.01}} || Minimal error to send updates across network for near units. Using larger value can reduce traffic sent for near units. Used to control client to server traffic as well. | {{hl|MinErrorToSendNear = 0.01}} || {{hl|0.01}} || Minimal error to send updates across network for near units. Using larger value can reduce traffic sent for near units. Used to control client to server traffic as well. * When using MinErrorToSend alone, for small values of distance (d) the frequency of high errors (E) would cause excessive network messages that are not necessary but could negatively impact FPS. * When using MinErrorToSend alone, for small values of distance (d) the frequency of high errors (E) would cause excessive network messages that are not necessary but could negatively impact FPS. * Too large of a value for METSN can prevent timely desirable network update messages which can result in units appearing to "warp" * Too large of a value for METSN can prevent timely desirable network update messages which can result in units appearing to "warp" Line 51: Line 51: | Maximal size of packet sent over network. This '''can be set for both''' client-to-server and server-to-client(s) independently''! {{Feature|important|Only use in the case your router or ISP enforces lower packet size and you have connectivity issues with the game.}} ''Desync might happen if used '''MaxSizeGuaranteed/MaxSizeNonguaranteed values over the maxPacketSize'''. | Maximal size of packet sent over network. This '''can be set for both''' client-to-server and server-to-client(s) independently''! {{Feature|important|Only use in the case your router or ISP enforces lower packet size and you have connectivity issues with the game.}} ''Desync might happen if used '''MaxSizeGuaranteed/MaxSizeNonguaranteed values over the maxPacketSize'''. |- |- | <tt>MaxCustomFileSize = 1024</tt> || {{hl|UNKNOWN}} || Users with custom face or custom sound larger than this size are kicked when trying to connect. | {{hl|MaxCustomFileSize = 1024}} || {{hl|UNKNOWN}} || Users with custom face or custom sound larger than this size are kicked when trying to connect. |} |}

Lou Montana: Text replacement - "([a-zA-Z0-9\. _"\\']+)<\/tt>" to "{{hl|$1}}" 2021-11-15T22:55:48Z Text replacement - "<tt>([a-zA-Z0-9\. _"\\']+)<\/tt>" to "{{hl|$1}}" ← Older revision Revision as of 00:55, 16 November 2021 Line 6: Line 6: This article deals with the '''basic.cfg''', the name means nothing, and can be called anything. The real name is determined by the [[Arma 3: Startup Parameters|-cfg]] command line option when launching the dedicated server or the game executable - in other words '''it also works for clients'''. When you do not provide a name, the default <tt>Arma3.cfg</tt> file is loaded located in the user profile folder. This article deals with the '''basic.cfg''', the name means nothing, and can be called anything. The real name is determined by the [[Arma 3: Startup Parameters|-cfg]] command line option when launching the dedicated server or the game executable - in other words '''it also works for clients'''. When you do not provide a name, the default {{hl|Arma3.cfg}} file is loaded located in the user profile folder. In this configuration file you should configure your server's connectivity, mainly for performance tuning. In this configuration file you should configure your server's connectivity, mainly for performance tuning. Line 19: Line 19: ! Parameter !! Default !! Description ! Parameter !! Default !! Description |- |- | <tt>MaxMsgSend = 128</tt> || <tt>128</tt> || Maximum number of packets (aggregate messages) that can be sent in one simulation cycle ("frame"). Increasing this value can decrease lag on high upload bandwidth servers. | <tt>MaxMsgSend = 128</tt> || {{hl|128}} || Maximum number of packets (aggregate messages) that can be sent in one simulation cycle ("frame"). Increasing this value can decrease lag on high upload bandwidth servers. |- |- | <tt>MaxSizeGuaranteed = 512</tt> || <tt>512</tt> || Maximum size (payload) of guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Guaranteed packets (aggregate messages) are used for non-repetitive events like shooting. | <tt>MaxSizeGuaranteed = 512</tt> || {{hl|512}} || Maximum size (payload) of guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Guaranteed packets (aggregate messages) are used for non-repetitive events like shooting. |- |- | <tt>MaxSizeNonguaranteed = 256</tt> || <tt>256</tt> || Maximum size (payload) of non-guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Non-guaranteed packets (aggregate messages) are used for repetitive updates like soldier or vehicle position. Increasing this value may improve bandwidth requirement, but it may increase lag. | <tt>MaxSizeNonguaranteed = 256</tt> || {{hl|256}} || Maximum size (payload) of non-guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Non-guaranteed packets (aggregate messages) are used for repetitive updates like soldier or vehicle position. Increasing this value may improve bandwidth requirement, but it may increase lag. |- |- | <tt>MinBandwidth = 131072</tt> || <tt>131072</tt> || Bandwidth the server is guaranteed to have (in bps). This value helps server to estimate bandwidth available. Increasing it to too optimistic values can increase lag and CPU load, as too many messages will be sent but discarded. | <tt>MinBandwidth = 131072</tt> || {{hl|131072}} || Bandwidth the server is guaranteed to have (in bps). This value helps server to estimate bandwidth available. Increasing it to too optimistic values can increase lag and CPU load, as too many messages will be sent but discarded. |- |- | <tt>MaxBandwidth = 200000 || <tt>UNKNOWN</tt> || Bandwidth the server is guaranteed to never have (in bps). This value helps the server to estimate bandwidth available. | <tt>MaxBandwidth = 200000 || {{hl|UNKNOWN}} || Bandwidth the server is guaranteed to never have (in bps). This value helps the server to estimate bandwidth available. |- |- | <tt>MinErrorToSend = 0.001</tt> || <tt>0.001</tt> || Minimal error to send updates across network. Using a smaller value can make units observed by binoculars or sniper rifle to move smoother at the trade off of increased network traffic. | <tt>MinErrorToSend = 0.001</tt> || {{hl|0.001}} || Minimal error to send updates across network. Using a smaller value can make units observed by binoculars or sniper rifle to move smoother at the trade off of increased network traffic. * Example: A unit 1km (distance d = 1km) from the player with MinErrorToSend = 0.001 (METS = 0.001) would send an update when that unit moves 50m (error value E = 50). * Example: A unit 1km (distance d = 1km) from the player with MinErrorToSend = 0.001 (METS = 0.001) would send an update when that unit moves 50m (error value E = 50). * Formula: d = sqrt[(20E)/METS] ; 1000 = sqrt[(20E)/0.001] -> E = 50 * Formula: d = sqrt[(20E)/METS] ; 1000 = sqrt[(20E)/0.001] -> E = 50 Line 35: Line 35: * When the error value (E) between the master copy of an object (whoever "owns" the object) and a client's perceived/simulated copy of the same object >= MinErrorToSend (METS), a network update message will be sent for it. * When the error value (E) between the master copy of an object (whoever "owns" the object) and a client's perceived/simulated copy of the same object >= MinErrorToSend (METS), a network update message will be sent for it. |- |- | <tt>MinErrorToSendNear = 0.01</tt> || <tt>0.01</tt> || Minimal error to send updates across network for near units. Using larger value can reduce traffic sent for near units. Used to control client to server traffic as well. | <tt>MinErrorToSendNear = 0.01</tt> || {{hl|0.01}} || Minimal error to send updates across network for near units. Using larger value can reduce traffic sent for near units. Used to control client to server traffic as well. * When using MinErrorToSend alone, for small values of distance (d) the frequency of high errors (E) would cause excessive network messages that are not necessary but could negatively impact FPS. * When using MinErrorToSend alone, for small values of distance (d) the frequency of high errors (E) would cause excessive network messages that are not necessary but could negatively impact FPS. * Too large of a value for METSN can prevent timely desirable network update messages which can result in units appearing to "warp" * Too large of a value for METSN can prevent timely desirable network update messages which can result in units appearing to "warp" Line 48: Line 48: }; }; </syntaxhighlight> </syntaxhighlight> | <tt>1400</tt> | {{hl|1400}} | Maximal size of packet sent over network. This '''can be set for both''' client-to-server and server-to-client(s) independently''! {{Feature|important|Only use in the case your router or ISP enforces lower packet size and you have connectivity issues with the game.}} ''Desync might happen if used '''MaxSizeGuaranteed/MaxSizeNonguaranteed values over the maxPacketSize'''. | Maximal size of packet sent over network. This '''can be set for both''' client-to-server and server-to-client(s) independently''! {{Feature|important|Only use in the case your router or ISP enforces lower packet size and you have connectivity issues with the game.}} ''Desync might happen if used '''MaxSizeGuaranteed/MaxSizeNonguaranteed values over the maxPacketSize'''. |- |- | <tt>MaxCustomFileSize = 1024</tt> || <tt>UNKNOWN</tt> || Users with custom face or custom sound larger than this size are kicked when trying to connect. | <tt>MaxCustomFileSize = 1024</tt> || {{hl|UNKNOWN}} || Users with custom face or custom sound larger than this size are kicked when trying to connect. |} |} Lou Montana: Some wiki formatting 2021-08-06T09:01:29Z Some wiki formatting Show changes

← Older revision		Revision as of 00:59, 16 November 2021
Line 19:		Line 19:
	! Parameter !! Default !! Description		! Parameter !! Default !! Description
	\|-		\|-
	\| {{hl\|MaxMsgSend = 128}} \|\| {{hl\|128}} \|\| Maximum number of packets (aggregate messages) that can be sent in one simulation cycle ("frame"). Increasing this value can decrease lag on high upload bandwidth servers.		\| {{hl\|c= MaxMsgSend = 128}} \|\| {{hl\|128}} \|\| Maximum number of packets (aggregate messages) that can be sent in one simulation cycle ("frame"). Increasing this value can decrease lag on high upload bandwidth servers.
	\|-		\|-
	\| {{hl\|MaxSizeGuaranteed = 512}} \|\| {{hl\|512}} \|\| Maximum size (payload) of guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Guaranteed packets (aggregate messages) are used for non-repetitive events like shooting.		\| {{hl\|c= MaxSizeGuaranteed = 512}} \|\| {{hl\|512}} \|\| Maximum size (payload) of guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Guaranteed packets (aggregate messages) are used for non-repetitive events like shooting.
	\|-		\|-
	\| {{hl\|MaxSizeNonguaranteed = 256}} \|\| {{hl\|256}} \|\| Maximum size (payload) of non-guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Non-guaranteed packets (aggregate messages) are used for repetitive updates like soldier or vehicle position. Increasing this value may improve bandwidth requirement, but it may increase lag.		\| {{hl\|c= MaxSizeNonguaranteed = 256}} \|\| {{hl\|256}} \|\| Maximum size (payload) of non-guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Non-guaranteed packets (aggregate messages) are used for repetitive updates like soldier or vehicle position. Increasing this value may improve bandwidth requirement, but it may increase lag.
	\|-		\|-
	\| {{hl\|MinBandwidth = 131072}} \|\| {{hl\|131072}} \|\| Bandwidth the server is guaranteed to have (in bps). This value helps server to estimate bandwidth available. Increasing it to too optimistic values can increase lag and CPU load, as too many messages will be sent but discarded.		\| {{hl\|c= MinBandwidth = 131072}} \|\| {{hl\|131072}} \|\| Bandwidth the server is guaranteed to have (in bps). This value helps server to estimate bandwidth available. Increasing it to too optimistic values can increase lag and CPU load, as too many messages will be sent but discarded.
	\|-		\|-
	\| <tt>MaxBandwidth = 200000 \|\| {{hl\|UNKNOWN}} \|\| Bandwidth the server is guaranteed to never have (in bps). This value helps the server to estimate bandwidth available.		\| <tt>MaxBandwidth = 200000 \|\| {{hl\|UNKNOWN}} \|\| Bandwidth the server is guaranteed to never have (in bps). This value helps the server to estimate bandwidth available.
	\|-		\|-
	\| {{hl\|MinErrorToSend = 0.001}} \|\| {{hl\|0.001}} \|\| Minimal error to send updates across network. Using a smaller value can make units observed by binoculars or sniper rifle to move smoother at the trade off of increased network traffic.		\| {{hl\|c= MinErrorToSend = 0.001}} \|\| {{hl\|0.001}} \|\| Minimal error to send updates across network. Using a smaller value can make units observed by binoculars or sniper rifle to move smoother at the trade off of increased network traffic.
	* Example: A unit 1km (distance d = 1km) from the player with MinErrorToSend = 0.001 (METS = 0.001) would send an update when that unit moves 50m (error value E = 50).		* Example: A unit 1km (distance d = 1km) from the player with MinErrorToSend = 0.001 (METS = 0.001) would send an update when that unit moves 50m (error value E = 50).
	* Formula: d = sqrt[(20E)/METS] ; 1000 = sqrt[(20E)/0.001] -> E = 50		* Formula: d = sqrt[(20E)/METS] ; 1000 = sqrt[(20E)/0.001] -> E = 50
Line 35:		Line 35:
	* When the error value (E) between the master copy of an object (whoever "owns" the object) and a client's perceived/simulated copy of the same object >= MinErrorToSend (METS), a network update message will be sent for it.		* When the error value (E) between the master copy of an object (whoever "owns" the object) and a client's perceived/simulated copy of the same object >= MinErrorToSend (METS), a network update message will be sent for it.
	\|-		\|-
	\| {{hl\|MinErrorToSendNear = 0.01}} \|\| {{hl\|0.01}} \|\| Minimal error to send updates across network for near units. Using larger value can reduce traffic sent for near units. Used to control client to server traffic as well.		\| {{hl\|c= MinErrorToSendNear = 0.01}} \|\| {{hl\|0.01}} \|\| Minimal error to send updates across network for near units. Using larger value can reduce traffic sent for near units. Used to control client to server traffic as well.
	* When using MinErrorToSend alone, for small values of distance (d) the frequency of high errors (E) would cause excessive network messages that are not necessary but could negatively impact FPS.		* When using MinErrorToSend alone, for small values of distance (d) the frequency of high errors (E) would cause excessive network messages that are not necessary but could negatively impact FPS.
	* Too large of a value for METSN can prevent timely desirable network update messages which can result in units appearing to "warp"		* Too large of a value for METSN can prevent timely desirable network update messages which can result in units appearing to "warp"
Line 51:		Line 51:
	\| Maximal size of packet sent over network. This '''can be set for both''' client-to-server and server-to-client(s) independently''! {{Feature\|important\|Only use in the case your router or ISP enforces lower packet size and you have connectivity issues with the game.}} ''Desync might happen if used '''MaxSizeGuaranteed/MaxSizeNonguaranteed values over the maxPacketSize'''.		\| Maximal size of packet sent over network. This '''can be set for both''' client-to-server and server-to-client(s) independently''! {{Feature\|important\|Only use in the case your router or ISP enforces lower packet size and you have connectivity issues with the game.}} ''Desync might happen if used '''MaxSizeGuaranteed/MaxSizeNonguaranteed values over the maxPacketSize'''.
	\|-		\|-
	\| {{hl\|MaxCustomFileSize = 1024}} \|\| {{hl\|UNKNOWN}} \|\| Users with custom face or custom sound larger than this size are kicked when trying to connect.		\| {{hl\|c= MaxCustomFileSize = 1024}} \|\| {{hl\|UNKNOWN}} \|\| Users with custom face or custom sound larger than this size are kicked when trying to connect.
	\|}		\|}

← Older revision		Revision as of 00:57, 16 November 2021
Line 19:		Line 19:
	! Parameter !! Default !! Description		! Parameter !! Default !! Description
	\|-		\|-
	\| ~~<tt>~~MaxMsgSend = 128~~</tt>~~ \|\| {{hl\|128}} \|\| Maximum number of packets (aggregate messages) that can be sent in one simulation cycle ("frame"). Increasing this value can decrease lag on high upload bandwidth servers.		\| {{hl\|MaxMsgSend = 128}} \|\| {{hl\|128}} \|\| Maximum number of packets (aggregate messages) that can be sent in one simulation cycle ("frame"). Increasing this value can decrease lag on high upload bandwidth servers.
	\|-		\|-
	\| ~~<tt>~~MaxSizeGuaranteed = 512~~</tt>~~ \|\| {{hl\|512}} \|\| Maximum size (payload) of guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Guaranteed packets (aggregate messages) are used for non-repetitive events like shooting.		\| {{hl\|MaxSizeGuaranteed = 512}} \|\| {{hl\|512}} \|\| Maximum size (payload) of guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Guaranteed packets (aggregate messages) are used for non-repetitive events like shooting.
	\|-		\|-
	\| ~~<tt>~~MaxSizeNonguaranteed = 256~~</tt>~~ \|\| {{hl\|256}} \|\| Maximum size (payload) of non-guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Non-guaranteed packets (aggregate messages) are used for repetitive updates like soldier or vehicle position. Increasing this value may improve bandwidth requirement, but it may increase lag.		\| {{hl\|MaxSizeNonguaranteed = 256}} \|\| {{hl\|256}} \|\| Maximum size (payload) of non-guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Non-guaranteed packets (aggregate messages) are used for repetitive updates like soldier or vehicle position. Increasing this value may improve bandwidth requirement, but it may increase lag.
	\|-		\|-
	\| ~~<tt>~~MinBandwidth = 131072~~</tt>~~ \|\| {{hl\|131072}} \|\| Bandwidth the server is guaranteed to have (in bps). This value helps server to estimate bandwidth available. Increasing it to too optimistic values can increase lag and CPU load, as too many messages will be sent but discarded.		\| {{hl\|MinBandwidth = 131072}} \|\| {{hl\|131072}} \|\| Bandwidth the server is guaranteed to have (in bps). This value helps server to estimate bandwidth available. Increasing it to too optimistic values can increase lag and CPU load, as too many messages will be sent but discarded.
	\|-		\|-
	\| <tt>MaxBandwidth = 200000 \|\| {{hl\|UNKNOWN}} \|\| Bandwidth the server is guaranteed to never have (in bps). This value helps the server to estimate bandwidth available.		\| <tt>MaxBandwidth = 200000 \|\| {{hl\|UNKNOWN}} \|\| Bandwidth the server is guaranteed to never have (in bps). This value helps the server to estimate bandwidth available.
	\|-		\|-
	\| ~~<tt>~~MinErrorToSend = 0.001~~</tt>~~ \|\| {{hl\|0.001}} \|\| Minimal error to send updates across network. Using a smaller value can make units observed by binoculars or sniper rifle to move smoother at the trade off of increased network traffic.		\| {{hl\|MinErrorToSend = 0.001}} \|\| {{hl\|0.001}} \|\| Minimal error to send updates across network. Using a smaller value can make units observed by binoculars or sniper rifle to move smoother at the trade off of increased network traffic.
	* Example: A unit 1km (distance d = 1km) from the player with MinErrorToSend = 0.001 (METS = 0.001) would send an update when that unit moves 50m (error value E = 50).		* Example: A unit 1km (distance d = 1km) from the player with MinErrorToSend = 0.001 (METS = 0.001) would send an update when that unit moves 50m (error value E = 50).
	* Formula: d = sqrt[(20E)/METS] ; 1000 = sqrt[(20E)/0.001] -> E = 50		* Formula: d = sqrt[(20E)/METS] ; 1000 = sqrt[(20E)/0.001] -> E = 50
Line 35:		Line 35:
	* When the error value (E) between the master copy of an object (whoever "owns" the object) and a client's perceived/simulated copy of the same object >= MinErrorToSend (METS), a network update message will be sent for it.		* When the error value (E) between the master copy of an object (whoever "owns" the object) and a client's perceived/simulated copy of the same object >= MinErrorToSend (METS), a network update message will be sent for it.
	\|-		\|-
	\| ~~<tt>~~MinErrorToSendNear = 0.01~~</tt>~~ \|\| {{hl\|0.01}} \|\| Minimal error to send updates across network for near units. Using larger value can reduce traffic sent for near units. Used to control client to server traffic as well.		\| {{hl\|MinErrorToSendNear = 0.01}} \|\| {{hl\|0.01}} \|\| Minimal error to send updates across network for near units. Using larger value can reduce traffic sent for near units. Used to control client to server traffic as well.
	* When using MinErrorToSend alone, for small values of distance (d) the frequency of high errors (E) would cause excessive network messages that are not necessary but could negatively impact FPS.		* When using MinErrorToSend alone, for small values of distance (d) the frequency of high errors (E) would cause excessive network messages that are not necessary but could negatively impact FPS.
	* Too large of a value for METSN can prevent timely desirable network update messages which can result in units appearing to "warp"		* Too large of a value for METSN can prevent timely desirable network update messages which can result in units appearing to "warp"
Line 51:		Line 51:
	\| Maximal size of packet sent over network. This '''can be set for both''' client-to-server and server-to-client(s) independently''! {{Feature\|important\|Only use in the case your router or ISP enforces lower packet size and you have connectivity issues with the game.}} ''Desync might happen if used '''MaxSizeGuaranteed/MaxSizeNonguaranteed values over the maxPacketSize'''.		\| Maximal size of packet sent over network. This '''can be set for both''' client-to-server and server-to-client(s) independently''! {{Feature\|important\|Only use in the case your router or ISP enforces lower packet size and you have connectivity issues with the game.}} ''Desync might happen if used '''MaxSizeGuaranteed/MaxSizeNonguaranteed values over the maxPacketSize'''.
	\|-		\|-
	\| ~~<tt>~~MaxCustomFileSize = 1024~~</tt>~~ \|\| {{hl\|UNKNOWN}} \|\| Users with custom face or custom sound larger than this size are kicked when trying to connect.		\| {{hl\|MaxCustomFileSize = 1024}} \|\| {{hl\|UNKNOWN}} \|\| Users with custom face or custom sound larger than this size are kicked when trying to connect.
	\|}		\|}

← Older revision		Revision as of 00:55, 16 November 2021
Line 6:		Line 6:


	This article deals with the '''basic.cfg''', the name means nothing, and can be called anything. The real name is determined by the [[Arma 3: Startup Parameters\|-cfg]] command line option when launching the dedicated server or the game executable - in other words '''it also works for clients'''. When you do not provide a name, the default ~~<tt>~~Arma3.cfg~~</tt>~~ file is loaded located in the user profile folder.		This article deals with the '''basic.cfg''', the name means nothing, and can be called anything. The real name is determined by the [[Arma 3: Startup Parameters\|-cfg]] command line option when launching the dedicated server or the game executable - in other words '''it also works for clients'''. When you do not provide a name, the default {{hl\|Arma3.cfg}} file is loaded located in the user profile folder.

	In this configuration file you should configure your server's connectivity, mainly for performance tuning.		In this configuration file you should configure your server's connectivity, mainly for performance tuning.
Line 19:		Line 19:
	! Parameter !! Default !! Description		! Parameter !! Default !! Description
	\|-		\|-
	\| <tt>MaxMsgSend = 128</tt> \|\| ~~<tt>~~128~~</tt>~~ \|\| Maximum number of packets (aggregate messages) that can be sent in one simulation cycle ("frame"). Increasing this value can decrease lag on high upload bandwidth servers.		\| <tt>MaxMsgSend = 128</tt> \|\| {{hl\|128}} \|\| Maximum number of packets (aggregate messages) that can be sent in one simulation cycle ("frame"). Increasing this value can decrease lag on high upload bandwidth servers.
	\|-		\|-
	\| <tt>MaxSizeGuaranteed = 512</tt> \|\| ~~<tt>~~512~~</tt>~~ \|\| Maximum size (payload) of guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Guaranteed packets (aggregate messages) are used for non-repetitive events like shooting.		\| <tt>MaxSizeGuaranteed = 512</tt> \|\| {{hl\|512}} \|\| Maximum size (payload) of guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Guaranteed packets (aggregate messages) are used for non-repetitive events like shooting.
	\|-		\|-
	\| <tt>MaxSizeNonguaranteed = 256</tt> \|\| ~~<tt>~~256~~</tt>~~ \|\| Maximum size (payload) of non-guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Non-guaranteed packets (aggregate messages) are used for repetitive updates like soldier or vehicle position. Increasing this value may improve bandwidth requirement, but it may increase lag.		\| <tt>MaxSizeNonguaranteed = 256</tt> \|\| {{hl\|256}} \|\| Maximum size (payload) of non-guaranteed packet in bytes (without headers). Small messages are packed to larger packets (aggregate messages). Non-guaranteed packets (aggregate messages) are used for repetitive updates like soldier or vehicle position. Increasing this value may improve bandwidth requirement, but it may increase lag.
	\|-		\|-
	\| <tt>MinBandwidth = 131072</tt> \|\| ~~<tt>~~131072~~</tt>~~ \|\| Bandwidth the server is guaranteed to have (in bps). This value helps server to estimate bandwidth available. Increasing it to too optimistic values can increase lag and CPU load, as too many messages will be sent but discarded.		\| <tt>MinBandwidth = 131072</tt> \|\| {{hl\|131072}} \|\| Bandwidth the server is guaranteed to have (in bps). This value helps server to estimate bandwidth available. Increasing it to too optimistic values can increase lag and CPU load, as too many messages will be sent but discarded.
	\|-		\|-
	\| <tt>MaxBandwidth = 200000 \|\| ~~<tt>~~UNKNOWN~~</tt>~~ \|\| Bandwidth the server is guaranteed to never have (in bps). This value helps the server to estimate bandwidth available.		\| <tt>MaxBandwidth = 200000 \|\| {{hl\|UNKNOWN}} \|\| Bandwidth the server is guaranteed to never have (in bps). This value helps the server to estimate bandwidth available.
	\|-		\|-
	\| <tt>MinErrorToSend = 0.001</tt> \|\| ~~<tt>~~0.001~~</tt>~~ \|\| Minimal error to send updates across network. Using a smaller value can make units observed by binoculars or sniper rifle to move smoother at the trade off of increased network traffic.		\| <tt>MinErrorToSend = 0.001</tt> \|\| {{hl\|0.001}} \|\| Minimal error to send updates across network. Using a smaller value can make units observed by binoculars or sniper rifle to move smoother at the trade off of increased network traffic.
	* Example: A unit 1km (distance d = 1km) from the player with MinErrorToSend = 0.001 (METS = 0.001) would send an update when that unit moves 50m (error value E = 50).		* Example: A unit 1km (distance d = 1km) from the player with MinErrorToSend = 0.001 (METS = 0.001) would send an update when that unit moves 50m (error value E = 50).
	* Formula: d = sqrt[(20E)/METS] ; 1000 = sqrt[(20E)/0.001] -> E = 50		* Formula: d = sqrt[(20E)/METS] ; 1000 = sqrt[(20E)/0.001] -> E = 50
Line 35:		Line 35:
	* When the error value (E) between the master copy of an object (whoever "owns" the object) and a client's perceived/simulated copy of the same object >= MinErrorToSend (METS), a network update message will be sent for it.		* When the error value (E) between the master copy of an object (whoever "owns" the object) and a client's perceived/simulated copy of the same object >= MinErrorToSend (METS), a network update message will be sent for it.
	\|-		\|-
	\| <tt>MinErrorToSendNear = 0.01</tt> \|\| ~~<tt>~~0.01~~</tt>~~ \|\| Minimal error to send updates across network for near units. Using larger value can reduce traffic sent for near units. Used to control client to server traffic as well.		\| <tt>MinErrorToSendNear = 0.01</tt> \|\| {{hl\|0.01}} \|\| Minimal error to send updates across network for near units. Using larger value can reduce traffic sent for near units. Used to control client to server traffic as well.
	* When using MinErrorToSend alone, for small values of distance (d) the frequency of high errors (E) would cause excessive network messages that are not necessary but could negatively impact FPS.		* When using MinErrorToSend alone, for small values of distance (d) the frequency of high errors (E) would cause excessive network messages that are not necessary but could negatively impact FPS.
	* Too large of a value for METSN can prevent timely desirable network update messages which can result in units appearing to "warp"		* Too large of a value for METSN can prevent timely desirable network update messages which can result in units appearing to "warp"
Line 48:		Line 48:
	};		};
	</syntaxhighlight>		</syntaxhighlight>
	\| ~~<tt>~~1400~~</tt>~~		\| {{hl\|1400}}
	\| Maximal size of packet sent over network. This '''can be set for both''' client-to-server and server-to-client(s) independently''! {{Feature\|important\|Only use in the case your router or ISP enforces lower packet size and you have connectivity issues with the game.}} ''Desync might happen if used '''MaxSizeGuaranteed/MaxSizeNonguaranteed values over the maxPacketSize'''.		\| Maximal size of packet sent over network. This '''can be set for both''' client-to-server and server-to-client(s) independently''! {{Feature\|important\|Only use in the case your router or ISP enforces lower packet size and you have connectivity issues with the game.}} ''Desync might happen if used '''MaxSizeGuaranteed/MaxSizeNonguaranteed values over the maxPacketSize'''.
	\|-		\|-
	\| <tt>MaxCustomFileSize = 1024</tt> \|\| ~~<tt>~~UNKNOWN~~</tt>~~ \|\| Users with custom face or custom sound larger than this size are kicked when trying to connect.		\| <tt>MaxCustomFileSize = 1024</tt> \|\| {{hl\|UNKNOWN}} \|\| Users with custom face or custom sound larger than this size are kicked when trying to connect.
	\|}		\|}

Arma 3: Basic Server Config File - Revision history

R3vo: Added note about String Number Formats and linked to the page

Lou Montana: Text replacement - "{{Table/A3ServerSetup}}" to "{{Navbox/A3ServerSetup}}"

Lou Montana: Some wiki formatting

Lou Montana: Text replacement - "{{ExternalLink|" to "{{Link|"

Lou Montana: Some wiki formatting

Lou Montana: Fix

Lou Montana: Text replacement - "\{\{hl\|([a-zA-Z0-9\. _"\\'-]+=[a-zA-Z0-9\. _"\\'-]+)\}\}" to "{{hl|c= $1}}"

Lou Montana: Text replacement - "([a-zA-Z0-9\. _"\\'=-]+)<\/tt>" to "{{hl|$1}}"

Lou Montana: Text replacement - "([a-zA-Z0-9\. _"\\']+)<\/tt>" to "{{hl|$1}}"

Lou Montana: Some wiki formatting

Lou Montana: Text replacement - "`([a-zA-Z0-9\. _"\\'=-]+)<\/tt>" to "{{hl|$1}}"`

Lou Montana: Text replacement - "`([a-zA-Z0-9\. _"\\']+)<\/tt>" to "{{hl|$1}}"`