lastelement22
Member-
Content Count
5 -
Joined
-
Last visited
-
Medals
Community Reputation
10 GoodAbout lastelement22
-
Rank
Rookie
-
ARMA III on Linux servers via WINE
lastelement22 replied to Kindling's topic in ARMA 3 - SERVERS & ADMINISTRATION
I know what load distribution is. This server does not use multiple cores for AI processing. Using a headless client on the same machine is the workaround, to offload/distribute the AI processing to more CPU cores (assuming RAM isn't a limitation). Most people are running the HC on the same machine as the server. Regarding your second question: Yes, it can do that. I tested using a second machine to run the HC, and it worked fine. The HC and server connect via IP, just like a normal client. Please read this guide: http://www.reddit.com/r/arma/comments/16nl5x/a_quick_n_dirty_guide_to_headless_clients_for/ -
ARMA III on Linux servers via WINE
lastelement22 replied to Kindling's topic in ARMA 3 - SERVERS & ADMINISTRATION
Yup, it is set. "battleyeLicense=1;" is present in Arma 3/hc/Users/hc/hc.Arma3Profile (Made sure it was there, tried again same result.) EDIT: The solution ended up being to wipe out my .wine folder, and reconfigure winearch as 32 bit. Once it was re-installed on this architecture of wine, BattlEye Client had no difficulties staying connected once I did this. rm -rf ~/.wine WINEARCH=win32 WINEPREFIX=~/.wine winecfg -
ARMA III on Linux servers via WINE
lastelement22 replied to Kindling's topic in ARMA 3 - SERVERS & ADMINISTRATION
Yes, I have a separate key and steam account for the headless client. There is no duplicate client issue. The server kicks the HC after 15 sec or so because it is not able to communicate with the BattlEye client on the HC. The license agreement is accepted. The client console shows BattlEye start and run with the correct version. I am able to see the BattlEye client process start and run in top, and that process does not crash or hang before the server kicks the client. My Windows client has no issues staying connected, so the BattlEye server is fine. When BattlEye is not required by the server, the HC is rock solid. It stayed connected for 8 hours of stress testing and handled AI with no problems. So basically, why might the BattlEye client not be able to communicate with the server? EDIT: The solution ended up being to wipe out my .wine folder, and reconfigure winearch as 32 bit. BattlEye Client had no difficulties staying connected once I did this. rm -rf ~/.wine WINEARCH=win32 WINEPREFIX=~/.wine winecfg -
ARMA III on Linux servers via WINE
lastelement22 replied to Kindling's topic in ARMA 3 - SERVERS & ADMINISTRATION
I was able to get a headless client running via wine on the same machine as the server, and it works great! I loaded up 400 AI + town AI: the load was distributed and the server FPS kept up. However I have encountered an issue which I need help with. I am forced to disable server BattleEye to use the hc, or the server kicks the hc due to BattlEye client not responding. The BattlEye process is running, and the client reports the correct version etc in its console. Not sure what to do, does anyone have any ideas? Is there maybe a way to exempt its ID? EDIT: The solution ended up being to wipe out my .wine folder, and reconfigure winearch as 32 bit. BattlEye Client had no difficulties staying connected once I did this. rm -rf ~/.wine WINEARCH=win32 WINEPREFIX=~/.wine winecfg