Arma 3 Mission Maker Guide

Mission Maker's Guide

Running the TAK Server

This guide assumes that i have already understood the player's step by step to use ARMATAK, especially for helping newcomers as the mission maker. In order to fully run ARMATAK, you must have already configured a TAK Server (i highly recommend you to use OpenTAKServer) instance correctly. It's not a easy job for newcomers to the TAK environment but i always try to give a light on it. Check if your desired map is already supported by ARMATAK, if not, you can help to integrate it

3Den Editor Setup

Assuming that you already have your OpenTAKServer, OG TAK Server or whatever instance up and running, connect your ATAK/WinTAK/iTAK to test the connection between your device, the communication between the ARMATAK Socket and the TAK Server os done using a TCP Connection (at least for now), remember to check if it`s enabled, now here is a arma 3 side stepguide:

1. Open the mission in the 3den Editor and go to the Modules tab.
2. Select the "Team Awareness Kit -> ARMATAK CoT Router" to your scenario
3. Place it anywhere on the Map, in the current state of this project, there will be no different behavior on the location, this module will transmit every linked unit or vehicle connected to it, just remember to link the units, not the groups.
4. Double Click on the module icon to fill your TAK Server instance informations with address (without any protocol like http as preffix) and the port number (default for TCP is 8088, only TCP is supported for now), pay attention on it, if you are using a dedicated server, be sure to add a address reachable by the dedicated server, if the machine running the Arma 3 Server is the same as the one running the TAK Server instance, insert localhost on it, if the TAK server and Arma 3 Server are in different local network it must be the external ip address, etecetera...
5. If everything is ok, when you start your scenario you will get this message on the top right corner and the markers will be showed in the real map location for every module linked entity on the session, player units will stop being sent by the serverside armatak module when the unit player connects his EUD to the clientside module (to avoid duplicated markers), but it's up to the player to connect his EUD to the TAK Server and configure group side, role and callsign.

Zeus Setup

1. Using Zeus, use the CoT Router module, it will ask for the TAK Server and used port (remember that it must be a unsecure TCP connection), you should get a "Connected to Socket" message.
2. Use the Mark Entity module on the entities you want to mark, be aware that groups are not allowed, you must select each unit, vehicles or static props are allowed.
3. Same advise about user's EUD connected is applied.

Tips

• Both FreeTAKServer and OpenTAKServer won't work well with many markers sent by a single connection, errors are expected, test your mission a few times.
• OpenTAKServer link with ARMATAK won't output 2 CoTs with the exact same callsign and id, soo after the game session ends is recommended to purge the open tak server data on the web ui and restart it.
• There is a severe change that the socket will disconnect in long time persitent missions, and the player/server admin will have to manually restart the server using the CoT Router zeus module, i am working on it.

if you are facing problems, or want some help, please join our Discord and let's check this out.