Closed FieldGeneral1 closed 2 years ago
Interesting that it reports Initializing the HC1 as a player. Could you also include the launch parameters you are using to start up the HC session?
We have two hcs running successfully against a public MF server and didn't run into this issue. Only difference is Windows 2016 iirc.
-profiles=C:\arma\profiles -client -connect=127.0.0.1 -port=2312 -name=HC1 -mod=vn;@CBA_A3;@TFRB;
@FieldGeneral1 Make sure you are starting the Arma3server.exe, not Arma3. Additionally, are you attempting to run a headless client on the same OS as the Arma 3 Server?
arma3server.exe -client -connect=xxx.xxx.xxx.xxx -password=yourpass
Iv had this issue, however the work around I am using is to start the server and mission, connect the HCs then kick them (they should reconnect again automatically) then use #restart via the chat
FYI my servers are hosted by armahosts
Closing as this has been fixed
Describe the bug The headless client connects to the server but gets kicked from the mission during initialization.
Here's the log on the headless client
Here's the log on the server
To Reproduce Start a headless client to connect to a dedicated server Start the mission with headless client joined Headless client has endMission occur on it ~30 seconds after leaving map screen
Environment (please complete the following information): Version: v0.65.03 Map: Cam_Lao_Nam Windows Server 2019
Additional mods: CBA and TFAR
Time the bug occurred: 12:38:53