2.5 Server Doctrine

The Fighting 99th Dedicated DCS Server.
Post Reply
User avatar
Squid
Major
Major
Posts: 169
Joined: 30 Jun 2015, 10:16
United States of America

2.5 Server Doctrine

#1

Post by Squid » 19 Dec 2016, 04:39

To our server and mission crew:
Good evening, What do envision our server running when 2.5 releases. Will we keep a rotation of missions (if possible) of both Nevada and Caucuses maps running? I ask because I miss the ship aspect and water aspect of the caucuses map. I don't know if they will allow a server to simply load a new whole terrain on the fly or if we'll have to stop the server and bring it back up to switch modes. I do hope the terrains inter-operate. If we still have to handle a rotation using triggers, than perhaps we can broadcast warnings that state the server runs Nevada missions from time to time.
Image

User avatar
TracerFacer
Colonel
Colonel
Posts: 1241
Joined: 24 Jun 2015, 10:25
Location: North Dallas Burbs
United States of America

Re: 2.5 Server Doctrine

#2

Post by TracerFacer » 19 Dec 2016, 15:37

Since DCS is completely undependable during a mission reload.. I'm not sure any mission rotation defined would even matter / work. It will likely crash before it loads a new mission. Couple that with the fact that DCS does not release the memory it was using for prior mission. Even if you go back to the main menu. i.e. If that instance had climbed to 12GB of ram usage - it would not reset with the loading of a new mission. It would just continue to climb until it eventually crashed. The server has 32 gb, but it crashes way before it even gets close to using that.

Perhaps when we have a true server feature we can script something. But depending on anything IN the active mission to load the next mission is going to fail more than it works.
Image

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests