It might be worth checking out what files are being opened by each server using a utility like "Process Explorer" or "handle.exe".
Is "-mod=expansion\beta;\expansion\beta\expansion;" supposed to be "-mod=expansion\beta;expansion\beta\expansion;" ?
FireDaemon causing service crashes
- Edge100x
- Founder
- Posts: 13127
- https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
- Joined: Thu Apr 18, 2002 11:04 pm
- Location: Seattle
- Contact:
-
- This is my homepage
- Posts: 439
- Joined: Sat Sep 04, 2010 10:20 am
- Location: Cologne, Gemany
- Contact:
Re: FireDaemon causing service crashes
The Arma2 OA beta patches are best integrated with the -beta=Expansion\beta;Expansion\beta\Expansion startup parameter.
There is a difference between the -mod and -beta command,
http://community.bistudio.com/wiki/Arma ... Parameters
But otherwise, did you sepperate the arma2oaserver.exe executable files and folders for each different server, or are you using one .exe folder structure?
There is a difference between the -mod and -beta command,
http://community.bistudio.com/wiki/Arma ... Parameters
But otherwise, did you sepperate the arma2oaserver.exe executable files and folders for each different server, or are you using one .exe folder structure?
-
- This is my homepage
- Posts: 439
- Joined: Sat Sep 04, 2010 10:20 am
- Location: Cologne, Gemany
- Contact:
Re: FireDaemon causing service crashes
Another idea would be to check if your BattlEye configuration is interfering in some way, if you have enabled BattlEye and I don't thinks that the beta is causing any problems here. It is running stable as far as I can tell (which does not have to mean much of course
).
Especially the mpeventhandlers and the publicvariable may cause a few problems if they are not adapted for the particular mission. Try to run a "standard" Arma mission, or turn off BattlEye for a test and see if this affects the server stability.

Especially the mpeventhandlers and the publicvariable may cause a few problems if they are not adapted for the particular mission. Try to run a "standard" Arma mission, or turn off BattlEye for a test and see if this affects the server stability.