From e1d01b8f8fce268185667d8caabdbee1f35106d5 Mon Sep 17 00:00:00 2001 From: Valmo Trindade Date: Tue, 23 Jul 2024 19:26:54 -0300 Subject: [PATCH] expanded readme file --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 9c63ab0..ef4eb21 100644 --- a/README.md +++ b/README.md @@ -12,6 +12,8 @@ If you read the Project concept, there is a obvious limitation on using ARMATAK: Another thing to consider is that each dedicated server also generates a FreeTAKServer instance, and the whole TAK environment is developed to give information for the client, not remove information, so by using ARMATAK, that points to a single FTS instance, you have to assume that every user will be displayed on the TAK platform, even the ones on the other side, and the other side will can connect just by using the same address as the dedicated server, i wish i can have a different approach that could make possible using ARMATAK on PvP sessions, but that is what we have for now. +The TAK ecosystem have a slow learning curve (so does Arma), some channels i recommend is The TAK Syndicate, Dirty Civilian and TRex Labs to start learning, i don't think it's the perfect tool for situation awareness, but is the best tool we have publicly available right now, just remember that you must focus on data feeds, packages, planning and map editing tools, that is what you will use on ARMATAK addon. + ## Getting Started 1. Add ARMATAK to the Mod Preset of your mission.