User manual

F4-BMS 2.0 Technical Manual
13 MULTIPLAYER ENHANCEMENTS
BMS contains some MP tweaking that should extend multplayer experience. There were found
some leftovers from previous debug and testing which ment that packets were dropped instead
of being send to players. Also some tweeking with the packet size has been made.
This section explains these tweeks and how to enable/disable them.
13.1
TCP/IP MAXIMUM TRANSMISSION UNIT SIZE (MTU)
In all previous versions of Falcon 4, the TCP/IP MTU packet size was default set to 500 which
ment that packet sent between players never exceeded that size even if the messages was
larger. Since Windows 98 SE the use of bigger TCP/IP packets has been possible and therefore
we introduce the –MTU switch. With this you are able to control what size you will use for MTU.
For example. –MTU 1514 in the commandline for Falcon would triple the amount of data in each
packet and save packets send between players. (Initial testing only allowed 750 as a max value).
If you do not receive a commit button you will need to reduce the size.
Make some test to see what size that gives best multiplay between players and make sure all
players uses the same MTU size.
One new configuration variables has been added to the falconbms.cfg:
set g_bF4CommsMTU 1
One new commandline switch has been added:
-MTU XXX (where XXX is the maximum size of packet)
The MTU switch will only be active if the configuration variable g_bF4CommsMTU is equal 1.
Otherwise it defaults to 500 in MTU size.
13.2
DISABLE PACKETS LOSS
Some leftovers (forgotten) code that simulated drop of packets can now be disabled. This means
that all packets will be sent to players but it also increases the data transferred.
One new configuration variables has been added to the falconbms.cfg:
set g_bF4CommsKillPL 1
65