Johnny_Rico

You should be OK, the issues seem to be with Asus Z370 boards My gigabyte one works great at the advertised 3866 speed my RAM is rated at

Thanks for the replies guys It would be good to get ED to do another mass multiplayer test in debug mode, the kind they HAD to do with the wepaons.dll bug fixing Or alternatively give us better logging so we can send them data which they can use to make MP better ED .... Help us to help YOU

Good god, thats sure looks pretty

Normal week nights is about 15-20 on havoc Busy weekend is 20-30 (max player is set to 30 at the moment) ALso agree this started to be an issue after 1.5.6

How many players do you normally have on average ?

thanks for confirming what I thought

Thanks for the input So to re-cap List 1 default way DCS saves files List 2 file after DAWS has modified it DAWS and DCS can handle both versions

It has to write different data for each file type due to DAWS changing things I have a test version done , awaiting feedback from tester

+1 good idea

Noticed this several times over the last month or more Actually had fraps running when it happend (by luck I guess) Here is a capture of what was happening in an MP session when the LAG issue happened

is it on your local LAN or on the internet ? def port is always 10308

thanks for the info open&save the DAWS's saved file in the mission editor before launching the mission. ^ yep that is exactly what I do (needs to update mission file before loaded into MP server

so list 2 is what is the mission file inside the miz after DAWS has done its processing with it ?

hmm I have never used DAWS but I got contacted by Neon who said my script would not work with DAWS missions normal mission file data for wind section ["wind"] = { ["at8000"] = { ["speed"] = 0, ["dir"] = 0, }, -- end of ["at8000"] ["atGround"] = { ["speed"] = 0, ["dir"] = 0, }, -- end of ["atGround"] ["at2000"] = { ["speed"] = 0, ["dir"] = 0, }, -- end of ["at2000"] }, -- end of ["wind"] DAWS mission file provided to me same section mission["weather"]["wind"] = {} mission["weather"]["wind"]["at8000"] = {} mission["weather"]["wind"]["at8000"]["speed"] = 7 mission["weather"]["wind"]["at8000"]["dir"] = 273 mission["weather"]["wind"]["atGround"] = {} mission["weather"]["wind"]["atGround"]["speed"] = 3 mission["weather"]["wind"]["atGround"]["dir"] = 270 mission["weather"]["wind"]["at2000"] = {} mission["weather"]["wind"]["at2000"]["speed"] = 5 mission["weather"]["wind"]["at2000"]["dir"] = 264

everytime I see another one of these threads I am so glad I never bought Asus mobo

I got a DAWS mission file from Neon and have modified my script to work out if it is a DAWS mission then write the new weather values back to the DAWS mission differently than a normal mission file Assuming that the format of how the weather is stored in the DAWS mission file does not change this will most likely work ok

If you had a non dell PC I would say Overclock your CPU in BIOS You could buy a realy good GPU eg nvidia 1080 or 1080TI and that will boost things a bit But to to honest I would start saving up for a new PC if I were you

yes the update for this is out already for windows 10 other versions of windows will get it tuesday

indentical speed/vendor might not matter I had 2 x 4G on an old PC Bought 2 x 4G , exact same speed/vendor/model They would not play together one set or the other but not both at same time so good luck to you

good luck getting your money back on your CPU

it probably wont work

not worth it , better with M.2 mine benched close to the one listed above

command line options would be better if you wanted something like this eg dcs.exe -normandy would load dcs and prep the normandy map for use

YMMV But what I would do is to benchmark system as it is now Then replicate the test again after applying the patch and see how it performs

users / saved games / dcs / config / serverSettings.lua see if it lives there ?