killswitch

Current version: 1.0.1pre2 (build 196) This release is intended for users of all three variations of Arma 2 - the original ArmA 2, ArmA 2 Operation Arrowhead and ArmA 2: Combined Operations. Now comes in only one mod folder, @CBA_CO. You no longer need to load up to three different mod folders. Just load @CBA_CO Key Changes 1.0.1 requires ArmA II 1.62 beta build 100697 or later. (Get the latest ArmA II betas from here) This means that on Linux dedicated servers, you must copy the addons and dta beta game data folders from Expansion/beta/Expansion on your Windows computer into expansion/beta/expansion on the Linux server and edit the start script (arma2oaserver) to look something like this: OTHERPARAMS='-cpucount=2 -beta=expansion/beta;expansion/beta/expansion -mod=@cba_co;@other;@mods;@go;@here' Documentation Full documentation is available at DevHeaven The issue changelog is available here Download The addons, manual, functions reference and complete sources are included in the release. See here (Download page) CBA_CO_v1.0.1pre2.zip CBA_CO_v1.0.1pre2.7z Important: If you play with the current, official, non-beta ArmA II OA/CO 1.62 patch, you must use the previous 1.0.0 version: CBA_v1.0.0pre10.zip CBA_v1.0.0pre10.7z This version still needs you to load at least two and possibly three mod folders: ArmA II: -mod=@CBA;@CBA_A2 ArmA II: Operation Arrowhead -mod=@CBA;@CBA_OA ArmA II: Combined Operations -mod=@CBA;@CBA_A2;@CBA_OA

@ProGEEK and others: updated Linux toolset available on Maverick Applications (6.48) NOTE: yesterday's 6.47 was no good - it was crashy and useless. Get 6.48.

No one from CBA can fix the PwS issue, whatever that issue might be. Please let the PwS team know that there's an issue, though. I'm sure they would like to help.

The forum you posted this in ("Arma 3 - Troubleshooting") is for problems with the core game without addons. The actual problem you are experiencing is due to the server managers having a very old, very outdated version of CBA loaded (1.1.23 is over a year old). The solution is for the server manager(s) to update CBA.

What database? CUP and CBA do not have database features. What's a "bambi character"? The Arma 3 core game does not have deer. Try the server with only CBA and CUP and see if a stock BIS MP mission works. If that works, it is probably a compatibility issue with the other addons the server uses and/or a specific mission where "bambis" and database connectivity are used. Please describe the setup in more detail and add link to a .RPT file output from the server where the issue occurs.

Could you publish that on the GitHub releases page, please? ( https://github.com/michail-nikolaev/task-force-arma-3-radio/releases )

The reason for marking it as "deprecated" should be read as "not recommended since it may break in MP" for the reasons you noted - with BI's remoteExec*, server owners have a way to determine what's allowed and what's not. The intent with deprecating things in CBA is to nudge people towards using stock game features where possible. It is not our intention to remove or disable functonality in CBA unless absolutely neccessary.

That looks fine and the server has started OK. (When it says "Connected to Steam servers" the startup has finished OK) The S_API_FAIL message is probably due to the server not running the Steam GUI client. If you are kicked from the server, it's due to some other reason.

I'm scratching my head here, wondering what it could be... On the server, in the Keys folder, do you have any other .bikey files other than a3.bikey and cba_2.4.1.160606.bikey? If so, is one of the other keys one of the older CBA .bikey files? (Try removing it) Is the server a Windows or Linux server? If Windows server, is the server installation from the dedicated server package (Steam/Library/Tools/Arma 3 Server, not a full client installation from Steam/Library/Games/Arma 3)? Are you on the stable (1.60) branch or one of the devel/RC branches or perhaps the old 1.58 branch? Is the server and client on the same branch (for example, the normal, stable branch)?

You'll have to comb through the mod folders you're loading. Add this to the startup parameter of the client and/or server and check the RPT after startup: -checkSignatures The log should have entries similar to this if everything is OK: Signature tests for C:\Games\Steam\steamapps\common\Arma 3\@CBA_A3\addons\cba_arrays.pbo.cba_2.4.1.160606-b8145500.bisign PASSED! Look for any lines with signature tests that fail (or tests that pass for CBA addons not signed by the 2.4.1 bikey) If you only see CBA 2.4.1 tests and they all pass, the problem is not with CBA.

Addon 'cba_ui' requires addon 'A3_Ui_F_Data' This is caused by CBA 2.4.0. Solution: update to CBA 2.4.1.

Actually, the root cause of that is CBA 2.4.0 where that dependency snuck into cba_ui. If the affected players upgrade to 2.4.1, that particular error will disappear. They ought to upgrade their A3 installations too, of course... :-)

I cannot reproduce this. With a client and server running "-mod=@CBA_A3" and the 2.4.1 files and key, CBA shows up green in the server browser. I can connect and play just fine. Launching either the client or server with the "-checkSignatures" startup parameter tells me that the files are signed correctly - all addons in CBA 2.4.1 pass the signature check both on the server and the client. Make absolutely sure that you remove all(*) old CBA addons and replace them with the new ones. (*) Perhaps you have a set of older CBA addons in some mod folder somewhere that's used when the signature problems occur.

Ok. This thread is about CBA for Arma 3, not the unsupported AiA addon collection. Please look at the CUP project, which is the continuation of AiA.

It is how it works currently, but I suspect it shouldn't, since it is confusing. Added to the issue list: https://github.com/CBATeam/CBA_A3/issues/322

https://dev.withsix.com/projects/mikero-pbodll/files Current version: 0.5.39

That's an operating system limitation - run the command "ulimit -a" and check the value for "open files". I bet it's 1024. Raise the limit for max open files using ulimit -n. For example: try this ulimit -n 2048 before starting the Arma 3 server.

< ASM for Linux > --------------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || ArmA Server Monitor (ASM) was created by Fred41 to monitor Windows ArmA 2 or ArmA 3 game servers: Arma Server Monitor (very small but useful) ASM for Linux is the same thing for Linux Arma 3 servers. It consists of a shared library, asmdll.so that is called from Arma 3. a small application, armaservermonitor that runs as a service on the game server. REQUIREMENTS ASM.pbo and ASM.ini from from Fred41's GitHub page A working Linux Arma 3 server. The 32-bit runtime libraries for GNU clib and Gnome GLib 2. DOWNLOAD Current version, 0.5, can be downloaded here Mirror: here. MD5 checksum e721fc7a18ba41719283ca1e5bd0a5bf armaservermonitor-0.5-bin.tgz INSTALLATION There are more detailed instructions here: Wiki - Arma Server Monitor for Linux The quick start instructions are: Download ASM.zip from Fred41's GitHub page and extract that to your Arma 3 server directory Remove ASMdll.dll Change the names of the files from ASM.zip to all-lowercase letters. Download the binary release of ASM for Linux from here and extract that somewhere. Copy armaservermonitor and asmdll.so to your A3 server directory. Move ("cd") into the A3 server directory and run the ASM service in the background: ./armaservermonitor -s &>asm.out & Start the A3 server with the @asm mod folder loaded. You can do this using the -serverMod launch parameter: -serverMod=@asm(Alternatively, you can put asm.pbo into the A3 addons folder) From your Windows machine, connect the ArmaServerMonitor.exe GUI client to your A3 server. Start Arma 3 and join the Linux A3 server. Start a mission. Now observe the runtime stats of the Linux A3 server in the Windows GUI app. MULTI-SERVER INSTALLATION If you run more than one Arma 3 game server on a machine, follow the instructions above for the first server instance. For the other game servers, you will only need to install asmdll.so and the asm.pbo addon into these servers' installation directories. Start the ASM service only from the first server instance. When A3 server #2, #3 and so on are started, they will report to the single ASM service running from server #1:s directory. CHANGELOG 0.1 Aug 29, 2014: First release 0.2 Dec 19, 2014: Fixed: hung server-side instances would make the client receive garbage data. 0.3 May 09, 2015: Show asmdll initialization in the Arma server log output: 2015/05/09, 9:08:08 "ASM.fsm started" asmdll: reading settings from ./asm.ini asmdll: extension loaded asmdll: init successful, pid 20012, using slot 0 0.4 Nov 18, 2015: Fixed erratic CPS calculation that caused the glitchy graph in ArmaServerMonitor 0.5 Feb 14 2015: asm renamed to armaservermonitor, various bug fixes Bug reports are welcome, either here, but preferably on the project issue tracker here

New version, 0.5 released. Highlights: ASM binary renamed from "asm" to "armaservermonitor" Various small internal fixes and improvements Download links in the first post of this thread.

From piecing together what you write in the other thread, the crash/CBA-related error message occurs when you try to start a hosted MP game. See https://forums.bistudio.com/topic/187264-include-file-xcbaaddonsmainscript-macroshpp-not-found/#entry2965649 for a possible solution to this. @Imperium: the issue is being worked on and CBA will be changed to behave like vanilla.

Try this: 1) Make copy of the Arma 3 MPMissions folder (C:\Program Files\Steam\steamapps\common\Arma 3\MPMissions) somewhere safe. 2) Delete all files from the Arma 3 MPMissions folder (C:\Program Files\Steam\steamapps\common\Arma 3\MPMissions) 3) Start Arma again 4) Try to launch a hosted LAN MP server and see if it works without crashing If that works, you have a MP mission file that does this in the description.ext (or a file included in description.ext): #include "\x\cba\addons\main\script_macros.hpp" ...for some unknown reason. The fix is to find and remove that mission.

Needed: description of the exact steps to reproduce this. What "certain items"? Submit a mission file that works fine with vanilla A3 but not with CBA and describe *exactly* how to reproduce the issue.

The warnings can be removed by setting the key down handler to an empty string "" instead of an empty code snippet {}: ["Revo's Mine Detector","key_insertBattery","Insert Battery",{call Revo_fnc_insertBattery},"",[DIK_F8,[false,true,false]]] call CBA_fnc_addKeybind; Next, the errors appear to be due to Revo_fnc_insertBattery - try calling that function like this in the editor debug console: tmp = call Revo_fnc_insertBattery The last line of Revo_fnc_insertBattery is an integer assignment of this form: Revo_mD_batteryTime = 20; If I add this to the end of the function, the errors disappear: nil :huh:

Those are not errors - it is diagnostics output from the BIS_fnc_addStackedEventHandler calls that CBA does. It is visible because of allowFunctionsLog being set in the mission's description.ext.

No, not unless the hotfix causes a problem that wasn't there before. We have had no such reports (yet).