Using TADST to create Headless Client

[flighttime95 1]

Is there a tutorial out there on how to create a headless client with TADST?  I know there is a setting within TADST to check, but I have had no luck in creating a headless client when enabling that setting.  

 

Is the setup process for a headless client the same when using TADST?  I have followed the same steps by editing the server.cfg with the IP Addresses of the local and headless client (127.0.0.1 for the HC and then my own IP for the local) I created a batch file with instructions to start and create the headless client (from Monsoons  HC Guide).  I then start the dedicated server with TADST and then run the batch file but the headless client is not created and does not connect to the server/mission.  I am running KP Liberation missions by the way.  Any tips or suggestions?

[Bruce King 2]

I'm interested in this as well.

[damsous 329]

Hello, i just find your topic, its simple launch your server with TADST, check the HC box (do not change the IP leave it as default) after open your arma 3 launcher, in paramater (advanced) scroll down to host and check Launch as Headless client wait few second and you will see the HC connecting to your server.

 

Just launch the HC with the same server modlist and everything will be fine.

[Rawshark 11]

On 13/08/2018 at 5:14 AM, damsous said:

Hello, i just find your topic, its simple launch your server with TADST, check the HC box (do not change the IP leave it as default) after open your arma 3 launcher, in paramater (advanced) scroll down to host and check Launch as Headless client wait few second and you will see the HC connecting to your server.

 

Just launch the HC with the same server modlist and everything will be fine.

Hi sorry to ask but in TADST the HC section has two options; HC IPs and Local Clients IPs. If you are hosting the server on one computer and playing on a different computer do you still leave the IP as default (127.0.0.1) in TADST for both IPs or do you have to change anything? 

Thank you

[damsous 329]

If the HC is on the same machine (server+HC) leave it as default, but you need to create a shortcut with the same arma3server.exe you use with TADST, rename your shortcut for exemple Myheadless, add the line in target field -client and your good.

 

TADST will add the right line in your TADST_config file : (local host) your HC should connect to the server.

 

If its not work or you you use an other machine for your HC overwrite this line in your TADST_config file

headlessClients[]={127.0.0.1};
localClient[]={127.0.0.1};

 

by

 

localClient[]={127.0.0.1,127.0.0.2,127.0.0.3,127.0.0.4,127.0.0.5,127.0.0.6,127.0.0.7,127.0.0.8,127.0.0.9,127.0.0.10,127.0.0.11,127.0.0.12,127.0.0.13,127.0.0.14,127.0.0.15,127.0.0.16,127.0.0.17,127.0.0.18,127.0.0.19,127.0.0.20,192.168.0.1,192.168.0.2,192.168.0.3,192.168.0.4,192.168.0.5,192.168.0.6,192.168.0.7,192.168.0.8,192.168.0.9,192.168.0.10,192.168.0.11,192.168.0.12,192.168.0.13,192.168.0.14,192.168.0.15,192.168.0.16,192.168.0.17,192.168.0.18,192.168.0.19,192.168.0.20,192.168.0.21,192.168.0.22,192.168.0.23,192.168.0.24,192.168.0.25,192.168.0.26,192.168.0.27,192.168.0.28,192.168.0.29,192.168.0.30,192.168.0.31,192.168.0.32,192.168.0.33,192.168.0.34,192.168.0.35,192.168.0.36,192.168.0.37,192.168.0.38,192.168.0.39,192.168.0.40};
headlessClients[]={"192.168.0.1","192.168.0.2","192.168.0.3","192.168.0.4","192.168.0.5","192.168.0.6","192.168.0.7","192.168.0.8","192.168.0.9","192.168.0.10","192.168.0.11","192.168.0.12","192.168.0.13","192.168.0.14","192.168.0.15","192.168.0.16","192.168.0.17","192.168.0.18","192.168.0.19","192.168.0.20","192.168.0.21","192.168.0.22","192.168.0.23","192.168.0.24","192.168.0.25","192.168.0.26","192.168.0.27","192.168.0.28","192.168.0.29","192.168.0.30","192.168.0.31","192.168.0.32","192.168.0.33","192.168.0.34","192.168.0.35","192.168.0.36","192.168.0.37","192.168.0.38","192.168.0.39","192.168.0.40","127.0.0.1","127.0.0.2","127.0.0.3","127.0.0.4","127.0.0.5","127.0.0.6","127.0.0.7","127.0.0.8","127.0.0.9","127.0.0.10","127.0.0.11","127.0.0.12","127.0.0.13","127.0.0.14","127.0.0.15","127.0.0.16","127.0.0.17","127.0.0.18","127.0.0.19","127.0.0.20"};

 

That should work