Community Update #26

Linux Server Update The open beta v.7 of the BF1942 dedicated Linux server is available on the usual distribution site: http://bf1942.lightcubed.com. Or you can grab it right here from our own download page.

this is an incremental update to the earlier release and you will need both to install the server. To install the update, change directory to the directory where your bf1942 game is located and untar the update file, this will overwrite the files that need to be updated.

Filename: bf1942_lnxded-1.4-ob7up.tar.bz2 MD5 sums: 5df2e3719104ac7ee44a1f4b26a56784 bf1942_lnxded.dynamic afbd28c4f02a8a82387ca2e557dd8805 bf1942_lnxded.static Version: BF1942 (Ver:52283/Wed Jun 25 16:29:27 CEST 2003) Release date: 2003-06-25 Release status: Pure bug fix release for OB6. Comment: Shipped with symbol table intact to produce stack traces.

Changes: - Linked with dynamic curses to avoid SIGILL on Intel machines. - Hostname lookup failure no longer a fatal error - Removed nearly all references to gettimeofday()--uses RDTSC instead. - Timing code around main loop reworked - Compiled with i586 optimizations instead of i686 - game.listPlayers format now includes IP address again - Fixed remote console hanging the game - Added server name to status monitor. - Allows changing of GameSpy/ASE ports via ServerSettings.con. - Fixed start.sh script for ldds that write message to stderr. Compiled with different optimization settings to improve performance. - The game.sayAll console command is now available. - game.listPlayers gives ip addresses in the correct order - The status monitor leaves more room for the server name. - Added frame simulation stats to status monitor for beta purposes.

Known Issues: There doesn't seem to be a way to change the ASE port with our current copy of the ASE SDK. It will always bind to port 14690. A small pause can be observed in the server while loading, this is normal and needed by the TSC calibration code. The server can use a lot of CPU running under certain Linux kernels. This can be avoided by recompiling the kernel removing unused features, but it is not yet clear what is causing the bug. SMP kernels can cause the server to use a lot more CPU than what it it really should be using; the only known workaround is to use a non-SMP kernel. People are also reporting success with the development kernels (the 2.5.x series), which is only recommended for the daring.

This Weeks Featured Secret Weapon: The Flakpanzer IV Wirbelwind