reV wrote:
thansk for the heads up,
but afaik the repos arent connected to these settings.
my best bet is that he ticked and than unticked the battleye button.
this will cause a3s to set the executable to the 32bit default arma3.exe
from what ive tested, i have several problems when i set the executable to arma3_x64.exe (it wont be registered by steam or shadowplay and stuff)
when i use the battleye exe it will be recognized and also launches the 64bit executable (so i stick with that, even we dont use it)
Even if you don't use Battleye on the server, it will still randomly block certain .dlls sometimes. I get this a s**t on certain days when I'm modding, it will block a different ACE dll each time I load until I get mad an disable it.