Search the Community

NOTE: This is for the STEAM EDITION. After playing Arma 3 for a while (quite long), i wanted to go back to Arma 2 and also I44 for a while, but I was having problems getting the DLCs to show properly, and a few error messages to go away. After trial and error, I manage to find the problems. Problem that I got and was solved(Can't remembered the exact message but the gist of it): Application Load error 5:00000065434 (If I remembered the error properly) MISSING STRING!!! Application/Game cannot be found. You installed the DLC, but it shows the LITE version of the DLC in your expansions menu. (This is actually due to though you installed the game in Steam, the content itself has not been integrated in Arma 2 directory which is why you need to run the DLC itself from Steam) Here Goes: 01. Install Arma 2 02. Run Game 03. Install Arma 2 Operation Arrowhead 04. Run Arma 2 Operation Arrowhead 05. Army of Czech Republic should start installing to A2OA. 06. Install Arma 2 British Armed Forces 07. Run Arma 2 British Armed Forces 08. British Armed Forces should start installing to A2OA. 09. Run Arma 2 Private Military Company 10. Private Military Company should start installing to A2OA. 11. Game should run with all DLCs properly. (Sequence of DLCs no longer matters after OA installation; Just make sure that you run the DLC from Steam first before running with other lanuchers or even OA itself. That means running the game British Armed Forces on Steam and not the Arma 2 or Arma 2 OA from Steam, for e.g.) For me, I use withSix to run my mods after that. Running the game first is just a way to initialize the running of some of the required installations. Hope this is useful to anyone having any problems on Arma 2 Steam. PS: If you manage to solve your problem from my instructions, do drop a reply so I can see that this topic is being useful. Thanks! :D

I bought the new Creator DLC S.O.G Prairie Fire. I also rented an Arma 3 game server from Nitrado. How do I get the DLC on the server now? I saw there is a folder named "vn" in which the DLC is stored. Do I just have to load it onto the server and can then just start playing? Mods always have "@" in front of the name. This is then uploaded to the server and activated. How's that with SOG Prairie Fire?

https://steamcommunity.com/sharedfiles/filedetails/?id=1453853092 Has anyone done this yet? If so how did you go about it and what was the outcome?

I need help with a script, Will there still be any way to download this script here? https://forums.bohemia.net/forums/topic/77374-improved-bullet-cam-script/ The Original Download Link Does Not Open.

UPDATE MAY 2018: Guide has been updated for 1.0.4 PINEAPPLE Hi All, This guide will address a Windows platform install from start to finish. The guide is accompanied by a download that includes all the necessary files you will need to setup your own server. You can also find the individual download links within the guide's pdf. Download Includes: EXILE SERVER INSTALLATION GUIDE V1.0.4.pdf Steam Installer MySQL Installer Vcredist Installer DirectX Installer Pbo Manager Installer Notepad++ Installer Server Launch Files DOWNLOAD https://www.dropbox.com/sh/pvmk6gvx2kci9ry/AAAwAovQk8hP1ZlH80daE_T4a?dl=0 UPDATED VCredist (Extract and run bat file as admin) https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/ Edited October 7, 2018 by kuplion My Way to install and update Server ! Server Install

I've run into an issue since the update for the Tanks DLC where my game downloads, then tries to validate and install the update but whenever it gets to the end of the install I get hit with an error such as "An error occurred while updating Arma 3 (corrupt content files) : F:\Program Files\steamapps\steamapps\common\Arma 3\Expansion\Addons\vegetation_f_exp.pbo". The exact error changes every time but it always seems to be in \Addons. I have tried several things such as restarting steam, restarting my pc, clearing download cache, verifying the integrity of my files, changing the download region to SEVERAL different regions, changed network/internet, and restarted network/internet. The only thing I can possibly think of at this point is to entirely re-install Arma 3 including all DLC and I believe mods as well. If this includes mods I'll be looking at a several hundred gigs I'll need to redownload which I am obviously not too excited about especially with my current download speeds. So that's the reason I'm here I'm hoping I can find some other solution other than completely re-installing everything and help if that doesn't fix my issue either. Complete rundown of what happens: My game downloads the 15.2GB update, goes through a validating period and then goes to installing which lasts up until about two-thirds of the loading bar is filled it then gradually increases the time up until "more than a year" (I originally thought this was pretty funny), and then if I have the "Launch game as soon as it's ready" checked it will spit me out an error like the one given above or just goes back to the validating stage if I don't have it checked. Error: An error occurred while updating Arma 3 (corrupt content files) : F:\Program Files\steamapps\steamapps\common\Arma 3\Expansion\Addons\vegetation_f_exp.pbo Many of the attempted fixes were found here https://help.steampowered.com/en/wizard/HelpWithAppError/?appid=107410&error=13 I haven't tried everything but I have tried about all of the ones that are reasonable.

I'm prepareing for Tac-Ops DLC, so I bought an SSD drive for arma3. I want to reinstall the game to this new drive. My basic plan is easy: uninstall arma3 by Steam client and install arma3 by Steam client on the new drive. But arma3 has a lot of config and setting and save and init file all over my PC. And I don't want to lose data. 1. I didn't change windows settings, so My Documents and AppLow folders stay on the original drive. 2. When I uninstall arma 3 by steam client, is it delete the saves at My Documents? Do I need to make a backup before uninstall? 3. When I uninstall arma 3 by steam client, is it delete the graphical settings and the custom keybindings? Do I need to make a backup before uninstall? (if yes, where are those files?) 4. When I uninstall arma 3 by steam client, is it delete the launcher defaults (eg, how many core in my CPU, how many RAM I want to add the exe)? Do I need to make a backup before uninstall? (if yes, where are those files?) 5. When I uninstall arma 3 by steam client, is it delete the mods (both workshop and 3rd party downloads)? If I made a backup, workshop will recognize those and not start to redownload the huge ones? 6. What I forgot to backup? What I will lose if I reinstall? Please help me in this!

SLASS - Seelenlos Arma 3 Server Script short: slass Tested on Ubuntu 16.04 (Xenial) Visit us on TS3: ts3.seelenlos.eu?port=9987 | seelenlos.eu | seelenlos on Steam (c)2017 by seelenlos License: GNU GPLv3 GitHub: SLASS ## General This script will greatly ease the installation and management of three Arma3 servers including mods from the Steam workshop.</br></br>This is not a one-click-get-a-server script. Its usage is simple, but do yourself a favor and read this manual BEFORE you begin. Really. Basic knowledge of the linux command line usage is assumed. ## What it does The seelenlos Arma 3 Server Script - installs three arma3 server instances on Linux - saves precious storage by using symlinks (about the space for one installation is needed) - implements the instances as services in the OS - restarts the servers if they crash - provides diagnostic commands on the running servers - installs Arma3 mods from the workshop - provides a central config file where you can specify an individual mod set for each server - differentiates between mod, servermod, and clientmod - manages the *.bikey files in dependency of the loaded mods for each server instance - provides a central mission repository for all instances - creates meaningful servernames for the server browser depending on the loaded mods - reconfigures the servers upon each restart according to the config files - can be used to update Arma3 and the mods by a single command - provides a simple way to have an almighty admin and a maintance user, who can update/install mods, and add missions, but not fumble around in the important scripts ## How it works ### Basic Structure The script will generate a master installation (a3master), that will never be started. Using symlinks, it will build three server instances out of this master installation. The instances are later run as a system service (SysVInit). The whole set of server files, including the mission repository (mpmissions folder) and *.Arma3Profile is being shared among the instances, but the instances use individual config files. A script will manage the mods and their keys to load for each server instance. Individually for each instance you can set: - (part of) the config file - the mods to use including their keys - the servername All instances will share - the Arma3-files and mod files (update all instances at once) - the *.Arma3Profile - basic config settings - a common logfile folder ### What happens on installation You begin by putting the script folder installer into an arbitrary folder on your system. Upon start, the script will then establish an Arma3 installation inside that arbitrary folder. Depending on you installation path, it will build individual config and script files for your server, install steamcmd, set the required file ownerships and rights, and install the servers as a system service. The installation finishes with an update of Arma3 and the mods. Refer to the file doc/folder_struc.png for a general overview where to find the files and what they do. ### What happens on update File ownership in a3master will be reset to avoid issues from remote upload of mission files etc. The server instances are then stopped, and an update (or install, if not already there) of Arma3 and the mods is performed. After the update, the file rights in a3master are reset, all mods are renamed to lower case (avoids issues with crashing mods on linux) and the folders of the instances are cleared and rebuild. Finally, the severs are booted back up. ### What happens on start/restart On start, all config files are newly read in to consider possible config edits. The config file modlist.inp defines the mods to load, individually for each instance. Depending on that config, the server name and the startup options (-mods= ) are build. Then the script will generate the config file for the respective instance, and copy the individually needed set of .bikey - files into its keys folder. Logfiles older than {deldays} (servervars.cfg) will be deleted, a new logfile will be written. Afterwards, the instance will boot, being monitored by a watchdog process. The watchdog reboots the server if it crashes. The watchdog is also active if the server stopped externally, i.e. you can issue the #shutdown command ingame to read an updated server config. ## Installation ### 1. Prerequisites - ensure you have the root password for your machine at hand - create an arbitrary folder for the servers, we suggest /srv/arma3/ - copy the script folder "installer" in that folder, e.g. /srv/arma3/installer - open the file install.cfg inside the folder "installer", change the user informations therein to your wishes. The users can be created by the script, or manually before you start the installation; refer to the commands in ./installer/adddelusr.sh on how to do so. They will have the following functions useradmin - Is owner of the files in the server folder, can add/delete/modify files and manage servers. You can use your normal user account with sudo privileges for this. Make sure he is in grpserver (see below). userlnch - Is the owner of the server process once fired up. For security reasons, he should not be able to get a shell nor become root. Use strong Passwords for both users anyway, never hand them out! A server with web access is not a toy! grpserver - a user group in which both preceding noted users must be, preferably as initial-group. Add additional users to that group, to allow them to make basic maintenance of the gameserver (update, mod/mission install, restart, cfg changes) - prepare the server config files in ./installer/rsc a3common.cfg - master config file containing settings common for all server instances. a3inidi.cfg - template config file containing individual settings for each server instance. After installation, three individual copies of this file will exist, edit them if needed. basic.cfg - loaded as -cfg file by the server process servervars.cfg - config file setting additional options for the server executable, normally you don't need to edit this - determine the mods to install, to do so edit ./installer/rsc/modlist.inp. The file has seven columns: I. shortname of the mod II. steam-app-id of the mod; if the mod is not in the workshop, insert the word local III. mod type; use mod if the mod is to be loaded by server and client (key and mod is loaded), e.g. ACE cmod if the mod is only to be loaded client side (only mod is loaded), e.g. JSRS smod if the mod is only to be loaded by the server (only key is loaded), e.g. ace_server IV. to VI. contains a binary key 0/1 selecting if the mod is to be loaded on server #1/#2/#3 VII. is the name of the mod included in the servername for the server browser; Type "xx" if do not want the mod to appear in the server name for the server browser; see also the example file in ./installer/optrsc/ prepserv.sh - defines the server names, among other stuff. Edit the entry hostname_base="Generic Arma3" and the entrys " hostname id1=' Server 1 |' " to " hostname id3=' Server 3 |' " to your wishes. The final server name will be composed as Hostname_base+hostname_idx+Modlist, e.g. "Generic Arma3 Server 1 | SLT, ACE" Edit more of the file to break it ... - Make sure that you have the steam login of a user with arma3 and the mods being stated in "modlist.inp" subscribed at hand. ### 3. Start Installation - ensure the file ./installer/a3install.sh is executable for your current user (chown , chmod 744) - run ./installer/a3install.sh, confirm continuation request - decide, if you want the users to be created, see above - the script may ask you to install some packages named like lib32..., those are needed by steamcmd - consider saving or immediately applying the commands printed on the prompt (visudo, ln) in another console; refer to the Usage-Update section below - confirm the begin of the download, or choose to download later by issuing the update script (see below). - The login into steam may fail on the first try, because you are probably logging in from a machine unknown to steam. In this case the script will freeze at the line "Verifiying Login-Data...". Abort the script by pressing Ctrl-C in that case. Then start /srv/arma3/steamcmd/steamcmd.sh and enter the guard code received per mail. Refer to the steamcmd manual on HowTo, or see below. Afterwards restart the update process by issuing sudo /srv/arma3/scripts/runupdate.sh. runupdate.sh from now on will always be the file to start in order to update arma3 or install a mod. - when you see app_update 233780 validate arma3 is being downloaded, be patient - when prompted, you may copy missions and non-workshop mods into the ./a3master folder - note the output on screen. If the installation of mods ...workshop_download_item ... fails with timeout, abort the update process with Ctrl-C. This will happen if you download a large mod for the first time and the download takes long. The download attempts are cumulative, so each time you run the update, you make progress. For RHS for instance i needed to run the script 5 times. The issue is a bug in steamcmd. ### 4. Done Put at least one mission into mpmissions and Enjoy Arma3! You may delete the installer folder now. ## Usage ### 1. Manage Servers The servers are implemented into your system as system services. You manage them by issuing the command sudo service a3srvX OPTION Replace X with the number of the server and OPTION with start - you guess it stop - ahem...well restart - Does a restart. If you have many big mods loaded, this command may fail because the server takes to long to stop. Just issue stop and after a short wait start again. status - prints the service status log - prints the serverlog onto the prompt in realtime as it is written, abort with Ctrl-C Update the servers and mods by running sudo /srv/arma3/scripts/runupdate.sh. The script will then download/update A3 and the workshop-mods registered in modlist.inp. You may want to add the line %{grpserver} ALL=NOPASSWD: /usr/sbin/service a3srv[1-3], {a3instdir}/scripts/runupdate.sh to the sudoers file with visudo to avoid the system asking for the password. This is a must if you want to enable other members of the group that do not have root permissions (i.e. the maintance users) to issue the commands. Replcace {grpserver} with your groupname and {a3instdir} with your installation path. You will also need to execute the command ln -s /home/{useradmin}/Steam /home/{userupdate}/Steam for each user you want to enable to run the update script. Run the command as the user {userupdate}. Replace {useradmin} and {userupdate} with the respective user names. The command will create a symlink of the Steam cache folder into the home directory of {userupdate}. This forces steam to use only one repository of cache files for all users, preventing several issues. ### 2. Install mods For workshop mods: Ensure you have the mod subscribed for the user you wish to use for the update. Write an entry for the mod to install into modlist.inp as described in the installation section. Run an update. For non-workshop (i.e. local) mods: Put the mod into /srv/arma3/a3master/_mods/ and copy the .bikey file (if one is needed) in a respective folder ./_mods/@modname/keys. Set the file owner and permissions like the other mods have it. You may alternatively run an update to let the script set the permissions. Write an entry for the mod to install into modlist.inp as described in the installation section. Reboot the respective server to load the mod. In both cases, ensure the .bikey file (if one is needed) is in a folder ./_mods/@modname/keys, if you observe problems loading the mod. Otherwise the script won't find it. ### 3. Edit server configs Thats simple: Edit what you need to, and restart the corresponding server. ## Appendix ### I. Enter Steam Guard code - run /srv/arma3/steamcmd/steamcmd.sh; make sure you run this command as {useradmin} or a {userupdate} for whom the ln command has already been applied - enter login USERNAME - enter the guard code - enter exit

I'm having difficulty with using the downloadable Community Kit. Where do I place the zip files / how do I import? And as a followup question to the above, is there a common place where people can upload/download player-made scenarios for the Eden Editor? Any assistance would be appreciated.

Okay after updating to 1.68 now battleye wont work. I already tried reinstalling the game. What else can I do? Can't seem to find any client downloads in Battleye's website.

Hello everyone I know that i am relatively new on the forums, however i thought i make a thread on how to install a Dev Branch version of the Arma 3 Server since that has been a total nightmare for me. I don't know how many people actually intent to test the server part of this, however i think it might be useful if someone is in the same situation as me. The two main ways to install an Arma 3 Server version are using Steam and SteamCMD. I will go through both of these and explain my experience with them. Steam Lets get this out of the way right now, as far as i can tell there is not way to actually install the "Arma 3 Server" stand alone version in the Development Build. When you do try to install it in development build you only get the current build with a performance build. The way to do this would be as follows: In Steam go to "Tools" and find the Arma 3 Server. Right click it and chose "Properties", now go to the tab "Betas" and enter the Code "CautionSpecialProfilingAndTestingBranchArma3". (This will however NOT install a x64 Version or the new build) You do however get a Arma 3 Server in the dev build when you simply install the normal Arma 3 game and you will therefore also get an x64 version of the Server if you put it into the dev build. (I admit this had eluded me at the beginning) Wiki link to the Dev branch passwords: https://community.bistudio.com/wiki/Arma_3_Steam_Branches#Arma_3_Server SteamCMD This one works however it is a bit of a shot in the dark since it only works sometimes. First you have to keep in mind that there are two ID's for this one for "Arma 3" and one for "Arma 3 Server". As we have just determined the latter is not actually included in the Dev build so we need to make sure to use the correct ID if we want a x64 Server. Check out these two pages showing the IDs: Arma 3: https://steamdb.info/app/107410/ Arma 3 Server: https://steamdb.info/app/233780/ If you know nothing about SteamCMD then the most simple way i can explain it is like this. You download SteamCMD at the link provided below and unpack the file into the folder where you want it installed. (Something like C:\SteamCMD) when you start it up it will download some files and install itself into the directory. SteamCMD Download: https://steamcdn-a.akamaihd.net/client/installer/steamcmd.zip The next thing you want to do after it is installed is login, use the following command for that: login YourSteam@Email.com YourSteamPassword Type in the SteamGuard key you just revived in your Email inbox The next command will be what installs the game, here we are going to use the ID for the Client version since that is what installs the server dev version. app_update 107410 -beta development validate From experience this will install the game in the none dev version and i have no idea why. However when i delete the install after this and run the exact same command again then it will install the correct dev version with the x64 Server. You can check the download right after you started it, look in the following folder if you have installed it where i suggested: "C:\SteamCMD\steamapps\downloading\107410\" The game .exe files are one of the first thing downloaded so if there are no x64.exe files present then it is downloading the wrong version. If so then just kill the program, delete the folder and run the same command again. There is way more detailed information about SteamCMD and how to install an Arma 3 Server. I encourage you to check out the following if this is something that you are interested in: How to install an Arma 3 Server: https://community.bistudio.com/wiki/Arma_3_Dedicated_Server How to install SteamCMD: https://developer.valvesoftware.com/wiki/SteamCMD Steam authentication failed I know that people have had problems with the dev build especially with the latest build that has resulted in a lot of people getting the above error. The SteamCMD version is supposed to be a stand alone version that works without steam, however that part is broken at the moment. I have not gotten my Arma 3 SteamCMD version to work however i have found a workaround. Install Steam on your Server/Computer and install the Arma 3 Server version in profiling.(Pretty much the first step i explained that doesn't work for x64) After that you can cheat a little and copy the version you downloaded from SteamCMD and put it into the same directory as the one you just downloaded with Steam. Make sure that the folder is called exactly the same as the one installed by Steam and don't overwrite it just rename the old one or delete it. Make sure Steam is closed while doing this. I know that doing this is a bit redundant since you could simply run the version that you have installed through Steam, i just wanted to show that the version downloaded by SteamCMD is in fact working however it requires you to have steam running in the background. (I am sure this will be fixed soon) Anyways, i hope this helps someone somewhere out there. Feel free to ask any questions you might have i will be happy to help.