Mitissa

It has a LOT to do with how much is being processed and Liberation adds a lot into .miz file that will cause this. All of the settings have an impact like culling distance, adding infantry beside vehicles on the front-line, etc. There is one thing I've tried so far Aries that might help you specifically because you're running the server on the same machine that you're playing on. We're going to need two windows running in the background to start with. One being Task Manager, the other being Resource Monitor (RM). You can open the RM through the task manager using the link in the lower-left of the 'Performance' tab in the Task Manager. Once you launch your DCS SERVER, alt-tab back to the RM, highlight DCS.exe, and take note of which CPU it is using as well as the PID. This'll be easy to see because DCS only uses one processor at the moment (single-threaded). For this example, my server file is running on CPU 3 looking at the graphs running down the right side and the PID of 3168: Okay, so we made a mental note that it is CPU3. Now let's launch the game itself. Once you're loaded in (at the main menu, not the server you're playing on), alt tab back out and head back to the Task Manager. You'll now see TWO DCS.exe's which is perfectly fine, but may be confusing which is why we made a note of the PID earlier. The one with the PID from earlier we're not going to touch, it's staying on CPU 3. We want to right-click the other one and go to 'Set Affinity'. This essentially lets us tell DCS which processor we want it to use. At this point you can pick any CPU you want that is not 3, so for yucks on mine I told DCS it can use anything but CPU 3. And then that's it! Alt tab back into the DCS.exe that you're actually playing on and now your Server and Game are using two different CPU's and they won't consume each other's resources. Keep in mind this only free's up the CPU assignment, you will still be sharing OTHER resources like RAM. This won't fix your problem but it's likely to buy you more than 90-minutes of flight time you're getting now. As for the Liberation missions themselves, they're likely going to be packed with fillers that bog us down until the Multi-threading is finalized and in open beta. You can however cut down on consuming shared resources by changing some things in the Mission Generator. It'll remove some realism but if it's between 'real' and '5 frames per second' I'll take a hit to my realism. Smoke Generator Spacing - Jack that number up. It doesn't change the quality of smoke but the quantity. Your front line will still look like a warzone but you may only have 6 pillars of smoke instead of 12. Generate Infantry sqauds alongside vehicles - I kept this on since I have 64Gb of RAM in my rig, but that's another massive resource-sink. Disable to save resources for where they're needed. Generate carcasses - Just like the two above, you'll take a hit to realism by removing the dead bodies from previous missions. So the mission you're currently flying will be unaffected and frankly once your front-line moves up you really aren't going to need to see the old bodies anyway. Culling Distance - This is another resource-saver regardless of what rig you're running. Basically Liberation is saying "I'm going to place tanks and buildings all over the map, but I'm not going to generate them or give them life unless you're within' the range below". The distance is the radius from each 'base' in Liberation. This can be a carrier, an air field, a FOB, the front-line... so the smaller the distance the less the CPU has to divert movement commands to. I have seen others suggest un-checking 'Moving ground units' but that completely eliminates the point of Lib maps. If the units don't move, neither does the front-line, so turn after turn is just going to be 'remove what was killed'. Hope this helps a bit Aries and anyone else who's frantically waiting for Multi-thread support to finish!

Okay update and closing this but I wanted to post in the event someone else ran into the issue. My brother is the one hosting the VM for me to use so we both remoted in and he monitored resources while I flew so we could get real-time results. The issue is that DCS doesn't use multi-threading yet so the CPU (despite not running at 100% total) is grinding one core into the ground at 100% but none of the other CPU's are doing anything. The issue will self-resolve once ED is able to release Multi-thread support but until then I'm just going to have to run missions locally. Thanks to everyone that read and replied (or messaged me on Discord), but this particular issue is at the mercy of ED's devs.

The only .lua file I've edited outside of the standard Beta Server install is the MissionScripting.lua below. The instructions for DCS Liberation state this is required to export the state.json file which carries data from one mission to the next. Basically it said to comment out the majority of lines. All the other .lua files have remained unchanged --Initialization script for the Mission lua Environment (SSE) dofile('Scripts/ScriptingSystem.lua') --Sanitize Mission Scripting environment --This makes unavailable some unsecure functions. --Mission downloaded from server to client may contain potentialy harmful lua code that may use these functions. --You can remove the code below and make availble these functions at your own risk. -- local function sanitizeModule(name) -- _G[name] = nil -- package.loaded[name] = nil -- end -- -- do -- sanitizeModule('os') -- sanitizeModule('io') -- sanitizeModule('lfs') -- require = nil -- loadlib = nil -- end

I'll share whatever info I can gather I would just need to know what files. Thanks for the assistance ahead of time Pravus!

Hey DCS Server Admins! I wanted to pick your brain(s) if possible because I've run into an issue hosting a dedicated server that both works and doesn't work at the same time. I first noticed the issue when I would fly low-resource Liberation maps. I'd take off, complete roughly a half-hour of mission and then I would start to notice aircraft just stopping mid-air. It was akin to a lag-spike but the communication to the server remained unaffected. After roughly a minute or so I would find myself still flying in the direction I was but all the aircraft around me started flying backwards (I'm assuming to sync what's on the server vs what's on my end). Seconds later I'd be a crater and I'd press 'Tab' to look at the action log where it says I was downed by a Manpad or another aircraft. Regardless of how complex or simple the mission is, these 'skips' still occur... so onto the things I've tried! So again, I'm thinking latency issue... so I remote connected to my dedicated server/VM and noticed every few minutes the DCS Open Beta server window will go to a 'Not Responding' state for a few minutes then return just to repeat the process a few minutes later. During these moments I checked the task manager and CPU workload is roughly 40% and Memory consumption is close to 40-50% used. The DCS.exe task itself would also go back and forth from running to 'not responding' just like the server window does. So if it isn't DCS workload (running out of resources) then the next thing to try is the Event Viewer. I opened up the event viewer and I saw hundreds of 'info' and 'warning' messages but no actual errors under any of the sections (Application, Security, etc.). If it's not an event then maybe it's in the DCS logs themselves. My first response was "Oh I bet the server is trying to process everything (which would cause massive slowdown because there's no video card on the VM) however judging by the logs above it IS running --norender --server so that isn't an issue either. Running a ping to the server from my flight PC returns a ping of 12ms so I know it isn't that either, and running a speed-test I'm getting 100+ Upload and 350+ Download so it isn't bandwidth. I checked all my open ports using telnet and just basic online port checkers and I'm able to hit the server on 10308, 10309, and 8088 without issues. So at this point I'm really lookin' for help from anyone willing to assist. If it isn't system resources, ping/latency, or an application error I'm completely out of guesses. Thanks ahead of time gang! dcs (1).log

Learned an important lesson today. When searching for DCS/Eagle Dynamics forums is would behoof you to not search "ED Forums"... my co-workers won't look me in the eyes anymore.

Thanks to both of you for the help. After seeing unknown's screen shots it's clear something was wrong on my end cause all of my custom missions looked like pic 1 regardless of how I modified the old system. Following Iron's advice I uninstalled and did a full purge of everything DCS except my .mizes and re-installed. I'm now able to get the weather effects working correctly so it's either a skin/mod/lua that was messing up and Steam's *cough* "repair" didn't pick up on it. Thanks again gang!

I haven't tried a full re-install which may be the next step, I have however used the repair feature in Steam (I'm running Steam Edition, sorry I should have put that earlier). It's also possible that I'm not explaining correctly. I uploaded two screen shots from my ME. The one titled 'NewWthr.png' is obviously the 2.7 System. There's Temperature, Cloud pattern, and the Base altitude. The old one 'OldWthr.png' is what I have to do in order to get the old weather system to populate (Base/Thickness/Density/Precipitation). Since the only way to get the old-system to show up I have to set the Preset to 'Nothing'. If 'Nothing' is the pattern I launch the game and there aren't any clouds regardless of the 'classic' options I pick. It feels like it's a step backwards, less customizable. Are you saying your OldWtrh version will let you modify weather patterns like you used to? NewWthr OldWthr

I've had this happen several times Ryan. It has to do with the way the AI deck-crew are 'triggered'. Similar to how triggers in the Map Editor work (IE: Aircraft won't start until X-amount of time), the deck crew follow a pre-determined set of rules and they aren't able to conflict them. What is happening, is the deck crew are given a command for 'Incoming craft landing' and they do not leave that command until the deck is clear of landing aircraft. So from a programming standpoint Aircraft radio'd in to land --> Trigger 'landing' crew Aircraft trips the wire, stops, and taxi's to parking (to be accurate the command is actually run when the hook of the landing craft comes up) --> Trigger 'Launch' crew From that perspective there are dozens of instances where something can go wrong and the only resolution is a server restart. Take this example below: F14 is 10-miles out flown by AI. F14 begins approach which triggers the 'Landing' state for the deck crew. F14 runs out of fuel / gets shot down / has to go around it never completes the last switch which is 'raise the hook, taxi to parking' so the deck crew are still under the impression that there is an aircraft coming in. On occasion (especially w/ the shot-down scenario) the Radio --> Ground Crew --> Request Launch will trigger the 'Launch' status for the crew but there are several situations where this will kick the crew out of the loop. If you want to test it / screw around with your friends, radio in to the carrier that you're inbound. Once you choose 'Commencing' the crew switched to 'landing' mode. Then simply fly around the carrier in a pattern and your friends will never be able to launch * Edit: It's still a bug, don't get me wrong. Just explaining what the AI are thinking.

So I'm an individual that plays almost exclusively single-player. I have horrific anxiety on Multiplayer games so needless to say the Mission Editor and I are very intimate. With version prior to 2.7, controlling the weather was pretty straight forward. Wind direction, cloud density, cloud elevation and thickness, Rain/Snow/Temperature... with 2.7's system you either use one of the presets (Broken 1-7, Overcast 1-3 etc.) but you are no longer able to fine-tune the weather patterns you want. I've tried applying a preset and then switching back to the pre-2.7 system (IE: Change preset to 'Nothing' and you'll get the old weather system). The old weather system only partially exists because the cloud-settings you're choosing under 'Nothing' apply t o clouds that aren't there. 'Nothing' = Null, so no matter what I can't put in weather effects that I want. Currently my only option is to choose one of the pre-set cloud or weather conditions, or enter in my own temp/density/precipitation on a map that won't spawn clouds. I see tons of posts about issues with the new cloud system (Rain drops on the canopy seems to be the biggest one which has already been reported) but I haven't found one addressing the Mission Editor's limitation. Any input the community or ED has would be awesome (Maybe I'm just missing something). Cheers.