Dwarden 1125 Posted September 9, 2011 (edited) Dowload: Direct: ftp://downloads.bistudio.com/arma2.com/update/a2oa-server-1.59.85663.tar.bz2 CRC32: 9194D33C MD5: CA84264442F0ACF33529C6DE1BAC06F4 SHA-1: F5FC75BCC13B622E335F34113EF2BD5522FB89C3 ftp://downloads.bistudio.com/arma2.com/update/a2oa-server-1.59.84426.tar.bz2 CRC32: 4BC95D8A MD5: 8FF543322BF5A1008FAE21AFBC812EDD SHA-1: 69975430F7A893C6E6637E88F30C0E7A98D0AA87 Note that it requires Arma 2: Operation Arrowhead data to be updated to version 1.59 first in order to run properly. 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.59 =============================================================== Copyrigt © 2010 Bohemia Interactive Studio. All rights reserved. For more information please visit http://community.bistudio.com/wiki/ArmA:_Dedicated_Server 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.59.84216 beta linux : http://forums.bistudio.com/showthread.php?t=124498 Edited October 21, 2011 by Dwarden linux server update Share this post Link to post Share on other sites
maddogx 13 Posted September 9, 2011 Presumably this beta once again requires all the latest 1.60 beta patch data. Share this post Link to post Share on other sites
Vixente 10 Posted September 9, 2011 Nice. Going to test it right now. THANKS Share this post Link to post Share on other sites
eddieck 10 Posted September 9, 2011 Does this fix the yellow icon? Share this post Link to post Share on other sites
sickboy 13 Posted September 9, 2011 Does this fix the yellow icon? Someone should try and confirm Share this post Link to post Share on other sites
eddieck 10 Posted September 9, 2011 Someone should try and confirm Just checked and it doesn't. (Also, I was able to run it with the standard 1.59 content.) Share this post Link to post Share on other sites
UnNamedRUS 10 Posted September 9, 2011 On this version of the server began to throw out with such message 2:48:59 Player [K'n'D]comrade EZHOff: Signature check timed out 2:48:59 Player [K'n'D]comrade EZHOff disconnected. 2:48:59 Admin [K'n'D]comrade EZHOff logged out. Share this post Link to post Share on other sites
Reezo 45 Posted September 9, 2011 A patch for which I thank you, again. Share this post Link to post Share on other sites
Fireball 16 Posted September 10, 2011 (edited) On this version of the server began to throw out with such message2:48:59 Player [K'n'D]comrade EZHOff: Signature check timed out 2:48:59 Player [K'n'D]comrade EZHOff disconnected. 2:48:59 Admin [K'n'D]comrade EZHOff logged out. Seems to be the regularCheck issue I experience. http://dev-heaven.net/issues/24104 But it was already in last build, the issue. Does anyone know if the build shortly after 1.59 release had the issue (I had regularcheck off, until recently, to test)? Edited September 10, 2011 by Fireball Share this post Link to post Share on other sites
nomad_man 10 Posted September 12, 2011 (edited) disregard, not tested on out end yet! Edited September 12, 2011 by nomad_man Share this post Link to post Share on other sites
PreedSwe 18 Posted October 11, 2011 I can't get this version to run at all... Warning Message: '/' is not a value Warning Message: Resource RscDisplayNotFreeze not found Warning: preNLOD format in object Very old object loaded. Warning Message: Bad file format (è–)). WATCHDOG (24487): [Tue Oct 11 09:22:19 CEST 2011] Server died, waiting to restart... I had to revert to 1.59.79548 Share this post Link to post Share on other sites
Vixente 10 Posted October 11, 2011 I can't get this version to run at all... Warning Message: '/' is not a value Warning Message: Resource RscDisplayNotFreeze not found Warning: preNLOD format in object Very old object loaded. Warning Message: Bad file format (è–)). WATCHDOG (24487): [Tue Oct 11 09:22:19 CEST 2011] Server died, waiting to restart... I had to revert to 1.59.79548 Do this: http://forums.bistudio.com/showpost.php?p=2016021&postcount=11 and avoid any capital letters within all the path to your Arma 2 folder ( e.g. /home/user/Desktop/arma2 will give you troubles, but .../desktop/arma2 shouldn't. That was my case. ) Share this post Link to post Share on other sites
Dwarden 1125 Posted October 21, 2011 new 1.59.85663 build for testing released Share this post Link to post Share on other sites
Fireball 16 Posted October 21, 2011 While starting, I noticed this in the logs: Failed to load TextureHeaderManager from file "ca\animals_e\texheaders.bin" - failed to open the file. (many iterations) Full log here: jail:~/a2oa-server# ./arma2oaserver start Starting ArmA 2 server... jail:~/a2oa-server# nohup: redirecting stderr to stdout jail:~/a2oa-server# tail -f log.2302.txt WATCHDOG (37786): [Fri Oct 21 13:49:46 CEST 2011] Starting server (port 2302)... Item str_disp_server_control listed twice /bin/cat: /proc/cpuinfo: No such file or directory Failed to load TextureHeaderManager from file "ca\animals_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\animals_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\ca_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\ca_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\characters_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\characters_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\l39\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\l39\texheaders.bin" Failed to load TextureHeaderManager from file "ca\misc_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\misc_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\missions_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\missions_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\modules_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\modules_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\mp_armory\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\mp_armory\texheaders.bin" Failed to load TextureHeaderManager from file "ca\plants_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\plants_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\roads_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\roads_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\rocks_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\rocks_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\signs_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\signs_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\structures_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\structures_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\takistan\data\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\takistan\data\texheaders.bin" Failed to load TextureHeaderManager from file "ca\tracked_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\tracked_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\takistan\data\layers\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\takistan\data\layers\texheaders.bin" Failed to load TextureHeaderManager from file "ca\desert_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\desert_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\weapons_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\weapons_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\wheeled_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\wheeled_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\zargabad\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\zargabad\texheaders.bin" Failed to load TextureHeaderManager from file "ca\air_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\air_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\air_d_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\air_d_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\air_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\air_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\ca_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\ca_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\characters_d_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\characters_d_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\characters_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\characters_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\characters_w_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\characters_w_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\data_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\data_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\shapur_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\shapur_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\structures_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\structures_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\missions2_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\missions2_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\missions_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\missions_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\missions_pmc\data\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\missions_pmc\data\texheaders.bin" Failed to load TextureHeaderManager from file "ca\plants_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\plants_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\provinggrounds_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\provinggrounds_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\roads_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\roads_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\tracked_d_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\tracked_d_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\tracked_w_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\tracked_w_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\weapons_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\weapons_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\weapons_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\weapons_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\wheeled_d_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\wheeled_d_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\wheeled_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\wheeled_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\wheeled_w_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\wheeled_w_baf\texheaders.bin" 13:51:02 Dedicated host created. 13:51:05 BattlEye Server: Initialized (v1.122) 13:51:05 Host identity created. But the server runs fine so far, will update on other issues later. Share this post Link to post Share on other sites
byteslam 10 Posted October 22, 2011 While starting, I noticed this in the logs: Failed to load TextureHeaderManager from file "ca\animals_e\texheaders.bin" - failed to open the file. (many iterations) Full log here: jail:~/a2oa-server# ./arma2oaserver start Starting ArmA 2 server... jail:~/a2oa-server# nohup: redirecting stderr to stdout jail:~/a2oa-server# tail -f log.2302.txt WATCHDOG (37786): [Fri Oct 21 13:49:46 CEST 2011] Starting server (port 2302)... Item str_disp_server_control listed twice /bin/cat: /proc/cpuinfo: No such file or directory Failed to load TextureHeaderManager from file "ca\animals_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\animals_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\ca_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\ca_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\characters_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\characters_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\l39\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\l39\texheaders.bin" Failed to load TextureHeaderManager from file "ca\misc_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\misc_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\missions_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\missions_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\modules_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\modules_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\mp_armory\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\mp_armory\texheaders.bin" Failed to load TextureHeaderManager from file "ca\plants_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\plants_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\roads_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\roads_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\rocks_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\rocks_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\signs_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\signs_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\structures_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\structures_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\takistan\data\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\takistan\data\texheaders.bin" Failed to load TextureHeaderManager from file "ca\tracked_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\tracked_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\takistan\data\layers\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\takistan\data\layers\texheaders.bin" Failed to load TextureHeaderManager from file "ca\desert_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\desert_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\weapons_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\weapons_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\wheeled_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\wheeled_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\zargabad\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\zargabad\texheaders.bin" Failed to load TextureHeaderManager from file "ca\air_e\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\air_e\texheaders.bin" Failed to load TextureHeaderManager from file "ca\air_d_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\air_d_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\air_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\air_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\ca_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\ca_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\characters_d_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\characters_d_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\characters_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\characters_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\characters_w_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\characters_w_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\data_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\data_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\shapur_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\shapur_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\structures_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\structures_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\missions2_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\missions2_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\missions_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\missions_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\missions_pmc\data\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\missions_pmc\data\texheaders.bin" Failed to load TextureHeaderManager from file "ca\plants_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\plants_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\provinggrounds_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\provinggrounds_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\roads_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\roads_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\tracked_d_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\tracked_d_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\tracked_w_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\tracked_w_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\weapons_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\weapons_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\weapons_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\weapons_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\wheeled_d_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\wheeled_d_baf\texheaders.bin" Failed to load TextureHeaderManager from file "ca\wheeled_pmc\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\wheeled_pmc\texheaders.bin" Failed to load TextureHeaderManager from file "ca\wheeled_w_baf\texheaders.bin" - failed to open the file. Failed adding texture headers from file "ca\wheeled_w_baf\texheaders.bin" 13:51:02 Dedicated host created. 13:51:05 BattlEye Server: Initialized (v1.122) 13:51:05 Host identity created. But the server runs fine so far, will update on other issues later. Same for me...due to the beta ArmAOA parts maybe?? Share this post Link to post Share on other sites
Fireball 16 Posted October 22, 2011 (edited) Same for me...due to the beta ArmAOA parts maybe?? Well, maybe, but it's not supposed to do it. I transferred the current's beta data to the server, so if it's that, then it's doing something wrong. ---------- Post added at 11:40 PM ---------- Previous post was at 10:57 PM ---------- Another thing: Does anyone also experience http://dev-heaven.net/issues/24104? Edited October 22, 2011 by Fireball Share this post Link to post Share on other sites
zwiebacksaege 10 Posted November 5, 2011 Hi there.. by the way my first post here :-) running this beta on fedora 12 x64 and have to notice that it uses nearly half the bandwidth than other DS versions before. very nice. Share this post Link to post Share on other sites
totalboffin 10 Posted November 10, 2011 Does this beta linux build still only use one cpu core? I've been struggling to get my linux dedicated server to access more than one cpu core. But I was using the official linux server version so far? the -cpucount parameter didn't seem to make any difference on the official build? Share this post Link to post Share on other sites
eddieck 10 Posted November 10, 2011 Does this beta linux build still only use one cpu core? I've been struggling to get my linux dedicated server to access more than one cpu core. But I was using the official linux server version so far? the -cpucount parameter didn't seem to make any difference on the official build? One CPU core for AI and another for other tasks. The AI thread will usually run at 100% usage, even on a Sandy Bridge CPU. The Windows server is the same way IIRC. Share this post Link to post Share on other sites
Banshee 9 Posted November 11, 2011 Dwarden, do you need more feedbackto fix the bugs? If not, when can we expect a new beta to test? Share this post Link to post Share on other sites
Dwarden 1125 Posted November 11, 2011 Dwarden, do you need more feedbackto fix the bugs? If not, when can we expect a new beta to test? i will see what i can do to get 1.60 beta build for linux server Share this post Link to post Share on other sites
Banshee 9 Posted November 11, 2011 Thanks, aprechiated. :) If it's out, we'll implement it onto our testserver. Share this post Link to post Share on other sites
nomad_man 10 Posted November 11, 2011 If you guys want coredumps and specific crash locations for the binary i can feed that in as well: [1484157.658647] server[15450]: segfault at 248 ip 00000000084c7b83 sp 00000000fff429d0 error 4 in server[8048000+1025000] [1526617.287341] server[25823]: segfault at 19 ip 000000000889af2a sp 00000000ff9d38b0 error 4 in server[8048000+1025000] [1804774.073924] server[5918]: segfault at 0 ip 000000000864b511 sp 00000000ffe04ae0 error 4 in server[8048000+1025000] Share this post Link to post Share on other sites
PreedSwe 18 Posted November 17, 2011 Going to test this build today, we have issues with people losing connection and getting disconnected randomly by BattlEye ALOT... Running the last official(I believe) non-beta 79548.. Which version is the most stable on linux? I'd rather have some AI glitches(we dont really have AIs in our mission that do much) than having people disconnected by BE every 5 minutes... ---------- Post added at 11:02 PM ---------- Previous post was at 10:58 PM ---------- Oh and is there a better way to get the beta files than Six Updater? Its giving me 85598 will that work with this beta version of the server? Share this post Link to post Share on other sites
sickboy 13 Posted November 17, 2011 The betas on SU awaits Jayarma2lib support, you can grab the latest beta from; http://www.arma2.com/beta-patch.php Can also host it on a custom repo for the players; http://six.dev-heaven.net/wagn/Six_Updater+CustomRepos_Setup But the latest has really 1.60 as version number and won't work with the linux 1.59, the build on SU does :). Share this post Link to post Share on other sites
