Logo

@FschJgBtl323 http://forums.bistudio.com/showthread.php?183918-Dedicated-Client-Headless-Client-feedback-%28dev-branch%29&p=2833516&viewfull=1#post2833516 and http://forums.bistudio.com/showthread.php?149412-Arma-3-Headless-Client&p=2834945&viewfull=1#post2834945

Strange, we use two Debian 7 Rootservers. After first armaserver start with the -name=blabla parameter the profile folders are located there. Maybe a problem with permissions ?

The .local folder is in the user folder of the server (the one where your steam folder is located). In our case the user is called server, the location is home/server/.local/share/ , here you find the arma Profile folders. Use WinSCP to connect to your server for upload, editing... files, maybe easier to find the hidden folder.

Sorry Tankbuster, it´s for KI Player on Bluefor, a doll, a Fake Player, https://translate.google.de/?ie=UTF-8&hl=de&client=tw-ob#auto/en/Attrappe

No Tankbuster, like i wrote: so i opened the mission pbo and placed a dummy soldier in the editor, far away on a isle with no damage, movement or weapons. Now when i start domination and set the dummy soldier to ai player, the enemy always see me and fighting me like it must be. Without headless client the problem is gone too. Maybe there is a better solution for it, but i don´t know much about scripting. The Performance with HC is realy nice and i don´t have crashes with it (160 Enemies, Enemy Vehicles and Helicopters + 7 Players = 46-50 Server fps). Only "bad" thing is, on Domination start i must disable AI Players and only enable dummy player, other players can enable AI too. Better when Ai is disabled in mission, like it is in untouched version, but with a activated Dummy Player which is not visible on the map (or far away) and not visible in playerlist. So this fix is okay but not the best solution. BTW, your Domination XTRA is running every day on one of our Servers and we like it really much.:bounce3:

Yes, dedicated windows server.

Yes, without mods and unmodified mission, only ASM Servermonitor was running. Same Problem happens in Xeno´s Domination 3.08. Tried it today again. After dead i halojumped at maintarged and the enmies not moving, fighting ..., they can´t see me. Only the Civilians running around :).

I had following problem with domination on dedicated server with headless client. when i start domination and was alone on the server, first the enemy at the main target can see me and fight against me, when i die and halojump or teleport to mhq on main target or sidemission, they do nothing, i can stand in front of them, shoot them and they can´t see me. Only when i come back with a helicopter they shoot on it, but when i am on foot again they can´t see me ... With more players on the server the problem does not exist, so i opened the mission pbo and placed a dummy soldier in the editor, far away on a isle with no damage, movement or weapons. Now when i start domination and set the dummy soldier to ai player, the enemy always see me and fighting me like it must be. Without headless client the problem is gone too. Maybe there is a better solution for it, but i don´t know much about scripting.

The mission isn´t working with headless client connected and activated. there are no tasks, enemyspawn or loacations on map starting. Without or disabled headless client all looks fine.

which startparameters you use. is it loading the server.cfg, arma3.cfg with the connection settings, your profile ? startline must look like this ./arma3server -ip=yourIP -port=2302 -name=yourProfile -cfg=arma3.cfg -config=server.cfg or use a script http://forums.bistudio.com/showthread.php?186496-Arma-3-Dedicated-Linux-Directory-Layout&p=2840342&viewfull=1#post2840342 or look here https://community.bistudio.com/wiki/Arma_3_Dedicated_Server

here is a nice start script for linux which my son wrote for our server. when steam is installed, you can install, update, start and stop your arms Server with it (more parameters at the bottom of the script). create a file called a3start.sh and put the script inside. Edit it to fit your system parameters (red marked areas). you don't´need to put mods inside the script. only create 2 folders in the arma 3 server directory "mods" and "mods_off". All modfolders in the folder "mods" are activated when server starts. The modfolder´s don´t need a @ in front of name. To have a mod loading order, you can use a number in front of mod name like 01_cba 02_asrai 20_wonderfull_island1 21_wonderfull_island2 … 30_weaponmod … to deactivate, copy the modfolder to folder mods_off. (i do it with filezilla ftp client, cause we have a ftp server running with a link to the arma server directory) start parameter ./a3start.sh -update to install or update arma 3 server ./a3start.sh -start for server start ./a3start.sh -stop for server stop For fast start, stop, update … you can create aliase like a3start, a3stop, a3upd. Then you don´t need to go into script directory to start. #!/bin/bash # # armaserver: ArmA 3 Linux Dedicated Server Control Script by EviLSeeD #======================================================================= #======== CONFIGURATION PARAMETERS ======== #======== MUST BE EDITED MANUALLY TO FIT YOUR SYSTEM PARAMETERS ======== #======================================================================= ARMA_DIR=[color="#FF0000"]/home/server/steam/arma3[/color] IP=[color="#FF0000"]123.123.123.123[/color] PORT=[color="#FF0000"]2302[/color] CONFIG=[color="#FF0000"]server.cfg[/color] CFG=[color="#FF0000"]arma3.cfg[/color] NAME=[color="#FF0000"]yourProfilename[/color] PIDFILE=${ARMA_DIR}/${PORT}.pid RUNFILE=${ARMA_DIR}/${PORT}.run LOGFILE=${ARMA_DIR}/${PORT}.log SERVER=${ARMA_DIR}/arma3server MODDIR="mods" #dirs where to look for mods, seperated by space OTHERPARAMS=[color="#FF0000"]-nologs -nosound -world=empty[/color] #======================================================================= cd ${ARMA_DIR} SCAN=`find $MODDIR -mindepth 1 -maxdepth 1 -type d -exec echo {} \; | sort | tr -d "." | tr "\n" "\;"` MODS=${SCAN/%;/} #======================================================================= ulimit -c 1000000 case "$1" in start) if [ -f ${RUNFILE} ]; then $0 stop fi echo "Starting ArmA 3 server with following mods:" echo "${SCAN}" echo "go" >${RUNFILE} # launch the background watchdog process to run the server nohup </dev/null >/dev/null $0 watchdog & ;; stop) echo "Stopping ArmA 3 server..." if [ -f ${RUNFILE} ]; then # ask watcher process to exit by deleting its runfile... rm -f ${RUNFILE} fi # and terminate ArmA 3 server process if [ -f ${PIDFILE} ]; then kill -TERM $(< ${PIDFILE}) if [ -f ${PIDFILE} ]; then rm -f ${PIDFILE} fi fi ;; status) if [ -f ${RUNFILE} ]; then echo "ArmA 3 Server should be running..." else echo "ArmA 3 Server should not be running..." fi if [ -f ${PIDFILE} ]; then PID=$(< ${PIDFILE}) echo "PID file exists (PID=${PID})..." if [ -f /proc/${PID}/cmdline ]; then echo "Server process seems to be running..." fi fi ;; check) echo -n "ArmA 3 directory: ${ARMA_DIR} " if [ -d ${ARMA_DIR} ]; then echo "OK" else echo "MISSING!" fi echo -n "Server executable: ${SERVER} " if [ -x ${SERVER} ]; then echo "OK" else echo "ERROR!" fi echo "Port number: ${PORT}" echo -n "Config file: ${CONFIG} " if [ -f ${CONFIG} ]; then echo "OK" else echo "MISSING!" fi echo "PID file: ${PIDFILE}" echo "RUN file: ${RUNFILE}" ;; restart) $0 stop $0 start ;; update) $0 stop cd [color="#FF0000"]/home/server/steam[/color] ./steamcmd.sh +login [color="#FF0000"]YOURSTEAMNAME YOURSTEAMPASS[/color] +force_install_dir ${ARMA_DIR} +app_update 233780 +quit ;; watchdog) # this is a background watchdog process. Do not start directly while [ -f ${RUNFILE} ]; do # launch the server... cd ${ARMA_DIR} echo >>${LOGFILE} "WATCHDOG ($$): [$(date)] Starting server (port ${PORT})..." ${SERVER} >>${LOGFILE} 2>&1 -ip=${IP} -port=${PORT} -config=${CONFIG} -cfg=${CFG} -name=${NAME} -pid=${PIDFILE} -mod=${MODS} ${OTHERPARAMS} if [ -f ${RUNFILE} ]; then echo >>${LOGFILE} "WATCHDOG ($$): [$(date)] Server died, waiting to restart..." sleep 5s else echo >>${LOGFILE} "WATCHDOG ($$): [$(date)] Server shutdown intentional, watchdog terminating" fi done ;; *) echo "$0 (start|stop|restart|update|status|check)" ;; esac We use debian 7 on our root server with a Arma Server Linux installation and a Arma Windows installation under Wine.

and when you set your difficulty, change the file permissions to read only. On my server, everytime it starts, in domination the DCSlot (name of dominations hc client) was always overwritten and had no difficulty inside.

Moon_child, for linux you can find the PERF2 server files but Domination XTRA still not running with it. Why you don´t install a Arma 3 Server under Wine ? The performance is very good.

maybe this site can help http://erictgrubaugh.com/play/games/arma/installation-and-configuration-of-an-arma-3-linux-dedicated-server/

Always good to have a Wine installation too. Performance is very good and a headless client with Domination a must have. :)

take a look on my post here http://forums.bistudio.com/showthread.php?149412-Arma-3-Headless-Client&p=2834459&viewfull=1#post2834459 I only tested the mission with headless client.

@SpectreRSG check this http://forums.bistudio.com/showthread.php?183918-Dedicated-Client-Headless-Client-feedback-%28dev-branch%29&p=2833516&viewfull=1#post2833516 ---------- Post added at 23:36 ---------- Previous post was at 22:19 ---------- @Bohemia check this :) The linux server with headless client does not work properly. Running on debian 6 Server and headless client running on the same root machine. Test with Xeno´s Domination 3.08 and Domination XTRA 3.0 Test 1 Arma server (Linux) running with linux headless client connected. If Domination is started, only the Main Target is created, no Radio Tower, no Enemy Camps ... no Sidemission. On the main target are some enemies and vehicles spawned, they are not moving and they can´t see you (standing 1 meter in front of them). Server fps 45-50. Test 2 On Windows Arma Server (Wine) with Windows headless client connected and the same mission all runs fine. Server fps 45-50. Test 3 On Windows Arma Server (Wine) with Linux headless client connected, not running, same as Test 1. Server fps 45-50. Test 4 On Linux Arma Server with Windows headless client (Wine) connected, main target - radio tower ... sidemissions start is ok but enemy moving is bad. hanging, sliding, lagging (range was around 500m). Server fps 45-50. maybe it´s our older Debian 6, but the arma server without headless client runs fine. Can any one confirm the same ?

My headless client is running on the same maschine as the server and kicked me out all the time. Now i added the Internet Ip from the server in the server.cfg too, looks like this headlessClients[]={"127.0.0.1","5.175.245.45"}; I can connect to the server now without kick. Using this startline on linux ./arma3server -client -connect=5.175.245.45:2302 -nosound -nofilepatching -cpuCount=2 on windows arma3server.exe -client -connect=5.175.245.45:2302 -nosound -nofilepatching -cpuCount=2

Hi Champ, are you using Bohemia Arma 3 Tools from Steam? Use v2 signatures! https://community.bistudio.com/wiki/ArmA:_Addon_Signatures

Nice addon, but battleeye kicks me on our dedicated server. signature file is not ok.

@NicoandLuis maybe this server start script will help you: #!/bin/bash # # armaserver: ArmA 3 Linux Dedicated Server Control Script EDIT by EviLSeeD #======================================================================= #======== CONFIGURATION PARAMETERS ======== #======== MUST BE EDITED MANUALLY TO FIT YOUR SYSTEM PARAMETERS ======== #======================================================================= ARMA_DIR=[color="#FF0000"]/home/server/steam/arma3[/color] CONFIG=[color="#FF0000"]server_a3.cfg[/color] PORT=[color="#FF0000"]2302[/color] PIDFILE=${ARMA_DIR}/${PORT}.pid RUNFILE=${ARMA_DIR}/${PORT}.run LOGFILE=${ARMA_DIR}/${PORT}.log SERVER=${ARMA_DIR}/arma3server OTHERPARAMS="-ip=[color="#FF0000"]YOUR.SERVER.IP[/color] -name=[color="#FF0000"]YOUR_NAME_FOR_USERCONFIG[/color] -cfg=[color="#FF0000"]arma3.cfg[/color] -cpucount=4 -maxmem=2047 -nologs -nosound -world=empty" #======================================================================= #======================================================================= # Auto Addon loading # create 2 Folders in the Arma Root Directory called mods and mods_off # to activate: put your @mod folder in the mods folder and it will load automatically after restart, # you don´t need to add it to the server start parameters. # to deactivate: put it in the mods_off folder # for the mod loading order use numbers instead @ for your mod, like this # 10_cba # 11_asr_ai # ... # 20_island1 # 21_island2 # ... # 30_weaponmod1 # ... #======================================================================= cd ${ARMA_DIR} SCAN=`find mods -mindepth 1 -maxdepth 1 -type d -exec echo {} \; | sort | tr -d "." | tr "\n" "\;"` MODS=${SCAN/%;/} #======================================================================= ulimit -c 1000000 case "$1" in start) if [ -f ${RUNFILE} ]; then $0 stop fi echo "Starting ArmA 3 server with following mods:" echo "${SCAN}" # file to mark we want server running... export LD_LIBRARY_PATH=[color="#FF0000"]/home/server/steam/arma3/[/color]:"$LD_LIBRARY_PATH" echo "go" >${RUNFILE} # launch the background watchdog process to run the server nohup </dev/null >/dev/null $0 watchdog & ;; stop) echo "Stopping ArmA 3 server..." if [ -f ${RUNFILE} ]; then # ask watcher process to exit by deleting its runfile... rm -f ${RUNFILE} fi # and terminate ArmA 3 server process if [ -f ${PIDFILE} ]; then kill -TERM $(< ${PIDFILE}) if [ -f ${PIDFILE} ]; then rm -f ${PIDFILE} fi fi ;; status) if [ -f ${RUNFILE} ]; then echo "ArmA 3 Server should be running..." else echo "ArmA 3 Server should not be running..." fi if [ -f ${PIDFILE} ]; then PID=$(< ${PIDFILE}) echo "PID file exists (PID=${PID})..." if [ -f /proc/${PID}/cmdline ]; then echo "Server process seems to be running..." fi fi ;; check) echo -n "ArmA 3 directory: ${ARMA_DIR} " if [ -d ${ARMA_DIR} ]; then echo "OK" else echo "MISSING!" fi echo -n "Server executable: ${SERVER} " if [ -x ${SERVER} ]; then echo "OK" else echo "ERROR!" fi echo "Port number: ${PORT}" echo -n "Config file: ${CONFIG} " if [ -f ${CONFIG} ]; then echo "OK" else echo "MISSING!" fi echo "PID file: ${PIDFILE}" echo "RUN file: ${RUNFILE}" ;; restart) $0 stop $0 start ;; update) $0 stop cd [color="#FF0000"]/home/server/steam[/color] ./steamcmd.sh +login [color="#FF0000"]YOUR_STEAM_NAME YOUR_STEAM_PASS[/color] +force_install_dir ${ARMA_DIR} +app_update 233780 +quit ;; watchdog) # this is a background watchdog process. Do not start directly while [ -f ${RUNFILE} ]; do # launch the server... cd ${ARMA_DIR} echo >>${LOGFILE} "WATCHDOG ($$): [$(date)] Starting server (port ${PORT})..." ${SERVER} >>${LOGFILE} 2>&1 -config=${CONFIG} -port=${PORT} -pid=${PIDFILE} -mod=${MODS} ${OTHERPARAMS} if [ -f ${RUNFILE} ]; then echo >>${LOGFILE} "WATCHDOG ($$): [$(date)] Server died, waiting to restart..." sleep 5s else echo >>${LOGFILE} "WATCHDOG ($$): [$(date)] Server shutdown intentional, watchdog terminating" fi done ;; *) echo "$0 (start|stop|restart|update|status|check)" ;; esac name the startscript arma3start.sh or whatever you want. check the red marked areas in the script and change it for your Server. The script is also for stress-free mod loading (manual is in script). You can use this script for Arma 3 Server start, stop, update or (when not installed) for Server Installation. ./arma3start.sh -start ./arma3start.sh -stop ./arma3start.sh -update (for update und installation)

Here i have the same results as YXman. Linux server with hotfix from today 30-35 fps. Windows Server running with wine 50 fps. Same configuration and same mission (Patrol Ops 3). FPS before hotfix was around 10-15, loading time on Linux is much faster now.

Try this one for testing: -connect=5.175.245.45 -port=2334 -password=1234

Hi Major_Shepard, thanks for this nice tool. Strange that the ´Join Server´ future does not work, is it really a arma 3 bug ? Because when I enter this line -connect=myserverip -port=2333 -password=mypass under Launcher Options in the Additional Parameters field, i can connect directly to our server. Maybe the info helps for troubleshooting