Jump to content


  • Content Count

  • Joined

  • Last visited

  • Medals

Community Reputation

8 Neutral

About Arghbra

  • Rank
    Private First Class

Recent Profile Visitors

284 profile views
  1. Hi Flax, I figured out what caused this problem. The port to which FAST is connected is not released from the list of server firewalls.
  2. Check if the ports are different for each server and if the MOD's listing is correct.
  3. Arghbra

    Workshop problem

    How did you accomplish the ArmA 3 folder change? Was it a program or did it simply drag to another directory? Open ArmA's laucher, click options, mod's options tab, and then check ArmA's watch folders and the folder where the mod's are. This can solve. Good luck
  4. Hello again Flax! A simple idea (I think): put in the MOD's tab, the number of MOD's marked in the session (server only, Player Required Mod's, HC reuired Mod's). Thanks for the beautiful Project.
  5. Flax, I did a test with the HC's and there was a "problem": I put the server set on port 2492 and set up 2 HC's on it. When the HC's started, they were both connecting to port 2302 (ArmA standard).
  6. Hello, Flax! I would like to give some suggestions for FAST2: 1-) In the MOD tab, there must be a mod counter marked in each session. 2-) There is a possibility to create a master profile for default settings (server password, difficulty settings, extra parameters) and when a new profile is being created, it is asked if the administrator is interested in loading the default profile. Thanks again!
  7. Hi Flax, my english is very, very poor. Thanks for the invitation to the discord but I think that here in the forum I will be able to explicate better (using google translator) kkkkkkkkkk This is the server, and FAST 2 open. Server name: Zona de Combate - Treinamento And in the ArmA laucher the server appears like this: Note: The other 2 instances of ArmA servers that appear in the photo are on the same server. Lauched using TADST Thanks for help and sorry for bad english
  8. Hello Flax! I had a small "problem": the server name configured in the Settings tab on Server Name did not appear. Instead, the full name of the PC appeared (which is configured in Windows Server). Name configured on server: Zona de Combate - Treinamento Any setup made wrong by me? Congratulations on the program! Is perfect
  9. Great @Rebel Man sorry for forum rules. My group realy love this map!
  10. @rekkless, @eric963, @Flax We have been having this problem for over 1 week but the mod's are updating normally.
  11. Negative @Dedmen but we kept the 2 instances installed on the server because we noticed a better performance in our structure when we used arma3server_x64.exe from the Arma Client installation for the Headless Client function. And we did not use the Linux version of the server (only 1 person had full knowledge to manipulate the distro). I still appreciate the response!
  12. Hello everyone! Many servers administrators already use / used the benefits of the Headless Client in your missions. So, they probably faced several errors such as: HC that does not connect, connects and get kicked, connects and stays with an hourglass, without working (for this I have not seen any solution until the present moment, and we think we have a solution). After several tests in 2 different environments (a Windows 10 professional server - a test server - and our main server machine – windows server 2016) we discovered something that can help everyone with the problem of the hourglass HC. Administrators often use programs to manage their servers, such as SteamCMD, TADST, FLAX, and usually install an instance of Arma3Server (to use as the main server instance). Some also installs an ArmA 3 client to help with HC configuration. So far so good, but the catch is the moment that we keep the steam logged on the server (we usually leave online the steam that have the ArmA 3 client purchased). We saw that the HC worked flawless in our test server and the main server suffered with the hourglass HC. So, what we notice different on the 2 environments was (in addition to the versions of windows): * The test server always has a steam logged that does NOT have the ArmA3 client installed and, the main server, the steam logged in HAVE an ArmA3 client license. So we changed the main server environment to verify if this was the problem: * We started our main server with a Steam account that does NOT have the ArmA 3 Client, but only the Arma3 Server. Therefore, we conclude that the HC work properly when the steam account on TADST or FLAX is different that are running on server, when you start the HC instance (this prevents Steam ID conflicts and errors). We hope this information helps the ARMA 3 server administrator who use HC. Greetings from CCT – Comunidade de Combate Tático Brasil, a Brazilian Arma Community since 2009. Portuguese version: Olá a todos! Muitos já utilizam/utilizaram os benefícios do Headless Client para o servidor. Portanto, devem ter se deparado com diversos erros como: HC que não conecta, conecta e leva kick, conecta e fica com uma ampulheta (este até então, sem solução simples, pelo o que pesquisei até o momento). Depois de diversos testes em 2 ambientes diferentes (um servidor com Windows 10 profissional - este sendo um server de testes - e o servidor principal do nosso clã - windows server 2016) descobrimos algo que pode ajudar a todos com o problema da ampulheta no HC. Os administradores costumam utilizar programas para gerenciamento dos seus servers, sejam manuais ou automatizados (SteamCMD, TADST, FLAX) e costumam instalar uma instância do Arma3Server (para utilizar como a instância principal do servidor) na máquina. Como já vi em alguns post, alguns instalam o ArmA 3 client para utilizar o executável do arma3server no HC. Até aqui tudo certo, mas a pegadinha está no momento que mantemos a steam logada no servidor (costuma-se deixar a steam que possui a versão do ArmA 3 client comprada aberta no servidor). Verificamos que no servidor de testes o HC funcionava perfeitamente e no principal existia o problema. Então, analisamos o que havia de diferente nos 2 ambientes que utilizávamos (além das versões do windows): * O servidor de testes sempre está com uma steam logada que NÃO possui o ArmA3 client instalado e, no servidor principal, a steam logada POSSUI uma licença do ArmA3 client. Então mudamos o ambiente do servidor principal para verificar se o que foi constatado realmente fazia diferença: * colocamos na steam instalada no servidor principal uma conta que NÃO possui o ArmA 3 Client, mas apenas o Arma3 Server. E ao executar a missão que possui o HC, o HC funcionou perfeitamente. DESSA FORMA, CONCLUÍMOS QUE PARA O HC FUNCIONAR CORRETAMENTE, A STEAM LOGADA NA MÁQUINA DO SERVIDOR DEVE SER DIFERENTE DA CONFIGURADA NO TADST, NO FLAX OU MESMO NA STEAMCMD (MESMO QUE NAQUELA CONTA NÃO POSSUIA UMA LICENÇA DO ARMA 3), POIS ASSIM A STEAM E O BATTLEYE NÃO ENFRETARÃO CONFLITOS DE ID ENTRE O EXECUTÁVEL DO ARMA 3 SERVER E O EXECUTÁVEL DO HC. Esperamos que isso ajude os administradores de servidores de ARMA 3 e que usam o HC. Saudações da CCT a todos.
  13. Hello Flax and everyone! Flax you could just create a manual command for the automated symbolic link process that the program already does. So the user would put the original link from where (or where) the download was made ..... I intend to use own steam to download the MOD's (for download speed and because even in large download's steam does not lose connection like steamCMD) The syntax for creating the dynamic link for those in trouble now is: mklink / D <LINK> <ORIGINAL FOLDER>
  14. Hello again Tankbuster! My clan uses ACE Pointing (if you use ACE, I suggest setting it) is much more interesting than Tactical Point. I found this video on YouTube right on time (the video is not my own, nor do I know the owner / responsible) :
  15. @Tankbuster Sorry for the delay in replying, I still do not use the FLAX program to start the server. Precisely because of the initial problem of the MODs are not listed in the laucher (the mod's were functioning as serverside). In this case I still work with TADST. I'm going to try some tests on the backup and warning server.