valmojr/armatak
1
0
Fork 0
mirror of https://github.com/valmojr/armatak.git synced 2026-06-13 15:23:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

Added zeus setup to mm guide

Valmo Trindade
2025-05-24 15:11:00 -03:00
parent a4dd3afeb3
commit a7ccca7f24
1 changed files with 11 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
Arma-3-Mission-Maker-Guide.md

@@ -2,9 +2,9 @@
## 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](https://docs.opentakserver.io/)) instance correctly. It's not a easy job for newcomers to the TAK environment but i always try to give a light on it.
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](https://docs.opentakserver.io/)) 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](https://discord.com/channels/1261763286064562226/1262521841822470165), if not, you can [help to integrate it](https://discord.com/channels/1261763286064562226/1335297747435393146/1335297747435393146)
## In Game Setup
## 3Den Editor Setup
Assuming that you already have your OpenTAKServer, FreeTAKServer or USG TAK Server 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:
@@ -14,20 +14,19 @@ Assuming that you already have your OpenTAKServer, FreeTAKServer or USG TAK Serv
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, etecetera...
5. If everything is ok, when you start your scenario you will get this message on the top right corner and the marker will be showed in the real map location for every module linked entity on the session.
## 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.
### Tips
* Both FreeTAKServer and OpenTAKServer won't work well with many markers sent by a single connection, errors are expected, test your mission many time.
* TAK Server link with ARMATAK won't output 2 CoTs with the same callsign, soo after the game session ends is recommended to purge the server data and restart it.
* I am really trying to bypass this, but 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 script
```sqf
"armatak" callExtension ["tcp_socket:start",[<your_tak_instance_address:port>]];
```
* 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 same callsign, soo after the game session ends is recommended to purge the server data 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
if you are facing problems, or want some help, please join our [Discord](https://discord.com/invite/svK64PCycU) and let's check this out.
## Known Issues
* Both the WebSocket for connecting into SIMTAK and the TCP Socket for connecting into a TAK Server won't work if you had a previous game session opened, in order for the sockets to work, it must be runned once when game starts, soo after leaving a game session, restart your Arma 3 server or client if the socket didn't work properly.
* It is highly recommended to purge all data on the TAK Server (OpenTAKServer, FreeTAKServer or even OG TAK Server) after every game session to avoid callsign conflicts.
* Sometimes the WebSocket for connecting into SIMTAK and the TCP Socket for connecting into a TAK Server won't work if you had a previous game session opened, in order for the sockets to work, it must be runned once when game starts, soo after leaving a game session, restart your Arma 3 server or client if the socket didn't work properly.