Jump to content
Sign in to follow this  
Dwarden

ARMA 2: Operation Arrowhead - Linux Server beta 1.60.93400

Recommended Posts

Download:

ftp://downloads.bistudio.com/arma2.com/update/a2oa-server-1.60.93400.tar.bz2

ftp://downloads.bistudio.com/arma2.com/update/a2oa-server-1.60.93400.tar.bz2

mirror:

-

CRC32: 0F949B9C

MD5: 94271591134BE09855793483654F3C27

SHA-1: 290C06A70EE2B1773F846AD111E8FA859E35211F

Last fix:

* recent crashfixes (as for windows, were crossplaform)

* channel disabling support as for windows

*changes and tweaks from windows branch including for netcode

*some crashes and issues across all platforms

previous fix:

*resolved crash on custom face textures (please verify if custom faces work in MP)

*[89964] Fixed: Linux servers were never green in server list.

older fix:

*resolved long loading times (this time it should work :) )

*resolved issue with "Failed to load TextureHeaderManager" , no need use -noTexHeaders commandline parameter!

Warning: This is 1.60 branch release

Note that it requires Arma 2: Operation Arrowhead data to be updated to version 1.60 first in order to run properly.

ideal to combine with latest OA beta client:

Please provide us with feedback to this topic.

* this version brings linux in sync with actual windows server improvements and ai/mp fixes ...

Arma 2: Operation Arrowhead - Linux Standalone Server 1.60

===============================================================

Copyrigt © 2010 Bohemia Interactive Studio. All rights reserved.

For more information please visit

http//community.bistudio.com/wiki/ArmA:_Dedicated_Server"]http://community.bistudio.com/wiki/ArmA:_Dedicated_Server[/size[/url]]

Installation instructions:

==========================

1. Following programs must have been installed on your Linux-box:

tar, gcc. Optional: md5sum (for setup integrity check)

1a. On some verions of Linux (this was reported for RedHat 9

and Gentoo linux 2.4.20) the NSCD deamon must be installed to

run ArmA 2 server successfully. Caching of DNS would be sufficient.

2. Copy the whole "ArmA 2 Operation Arrowhead" directory from Windows

to some Linux-directory (arma2arrowhead). DON'T DO ANY DATA CONVERSIONS

(even "dos2unix" translation of text files is not necessary).

Example: you can use PKZIP (WinZip, PowerArchiver, etc.) on

Windows and "unzip" on Linux.

Don't use upper case letters in the ArmA2 directory name

(/home/bob/arma2arrowhead will be good, /home/bob/ArmA2ArrowHead

may cause some troubles).

ArmA2 directory should contain subdirectories "Addons", "Bin",

"Campaigns", etc.

3. Copy the "server-x.xx.tar.gz" (x.xx is version number) file into

the arma2arrowhead directory. Unpack and install it with commands:

arma2arrowhead$ tar -xjf server-x.xx.tar.bz2

arma2arrowhead$ ./install

Watch the messages - they will inform you whether your installation

is successful.

4. Dedicated server can be started in foreground:

arma2arrowhead$ ./server

Or in background:

o$ nohup ./server > out.txt 2> err.txt &

[1] <pid>

5. Running server can be stopped by executing:

$ kill -s SIGINT <pid>

Where <pid> is process-id of mother server thread (printed out in

"nohup" command).

6. ArmA2 ArrowHead server has a feature: command-line parameter

"-pid=<pid_file>". It causes creation of <pid_file> with

PID of root ArmA2 process. If IP port specified in "-port=<nn>"

parameter is busy (in usage), ArmA2 will terminate immediately

and <pid_file> won't be written..

7. The "arma2server" script is provided for automatic server

start/restart/status query/etc. Please be sure to edit

CONFIGURATION PARAMETERS in lines 12 to 18 !

After this is done, install (hard-link?) the script into

"/etc/rc.d/init.d/arma2server" file. After that it can be managed

by "chkconfig" (see info/man).

previous thread about 1.60.93167 beta linux :

Edited by Dwarden

Share this post


Link to post
Share on other sites

One player had connection problems and crashed several times. In fact we all got red chain for several seconds (30+) but server didn't go down AFIK. Not checked logs yet, but will report any "unusualities", or if it was just that players "bad night".

As before, server shows green (without password), but with mods, custom faces work in MP.

Server shows yellow and perform badly with latest beta client (no problems with 87580).

Gonna check logs to see if it's my fault....

Share this post


Link to post
Share on other sites
One player had connection problems and crashed several times. In fact we all got red chain for several seconds (30+) but server didn't go down AFIK. Not checked logs yet, but will report any "unusualities", or if it was just that players "bad night".

As before, server shows green (without password), but with mods, custom faces work in MP.

Server shows yellow and perform badly with latest beta client (no problems with 87580).

Gonna check logs to see if it's my fault....

Same here. Connection problems, kicks from battleye ( corrupted memory #1 ) and client crash in one case. Tested with latest supported beta at the time which was 93348.

Will test today ( later ) with last beta - 93398, and standard 87580 and will report back.

Edit: Rpt here looks weird...

Edited by _MaSSive

Share this post


Link to post
Share on other sites

I have same issue. Battleye corrupted memory #1 when I start linux ArmaOA server, both Beta: v1.60.9340 & Official: v1.60.87589

Battleye client is 1.56

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×