Fool

Thank you once again Rarek running great here -> [FourDegrees]

.9 may make this obsolete but just in case it helps here's a crash log from last night after 11 hours of play:

I imagine we could start a whole other thread trying to figure out these settings but currently I'm using the ones below. The server has 100Mbps up and down. *** EDIT *** OK with 40 players the server dropped to 11FPS but the mission seemed totally playable and ran fine all night, I've been told that below 15 the server is considered overloaded but I could't see any issues with it. Thanks again Rarek this version seems very stable.

Thanks Rarek, at least that stops me scouring the internet for a solution.

Hondo - I've started revisiting the bandwidth optimization settings for the server and it looks to be helping things. Had around 35 fps last night but admittedly there were only 20 or so people on at the time. I think it's going to be trial and error to find the best settings though, there's so much incomplete or contradictory information on the correct settings.... The good news is that the missions is definitely much more stable and ran for 20 hours yesterday and only went down when the server blue screened (related to something else I have running). One problem I haven't been able to find an answer to though is that I've written a little .net windows service that monitors the Arma server process, when it inevitably does crash it just restarts the Arma service. Problem is once the server starts up again it's in an "openwaiting" state and needs a player to actually log in before the mission will start. The mission rotation settings look fine and as soon as a player joins they are dropped straight into Annex & Invade but until then the server looks as though it isn't running a mission. Does anyone know a way to start the mission running at launch?? I'm sure I had this working on a previous iteration of the server.

Hi - Just wanted to let you know our experience with the new version. Had it running for 18 hours yesterday before a crash, for pretty much 11 hours of that we had 40 people logged in. That's a huge improvement for us over the last version which seemed to crash every 20 mins Weirdly when it did crash it was 6:00 am and I don't think anyone was logged in. Yeah we're getting exactly the same behavior even though CPU usage on the box is usually only around 35% and there's tons of RAM and bandwidth free - if anyone has any ideas on that i'd like to know too. Anyway thanks very much for all the hard work chaps looking forward to v3