Memory Exceeding 16GB

I'm not sure what the normal usage is for this map;

But it's defiantly off the charts in terms of ram usage. I'm not really sure what's causing it. I've tried to flip a few settings in the options page, with no joy. I have the terrain setting to Low, tried reducing the visibility range to high and preload radius to below 60k. I ran into this issue previously before with Caucasus map, but I was running 12 GB and bumped myself up to 16 GB RAM. What gives with the insane ram usage?

I've ran into 1 BSOD so far, but I'm mainly crashing during mission. Multiplayer is usually fine, as long as I don't come to close to an AV8B...it'll just..lock up for 15+ seconds..:joystick:

It defiantly seemed more stable a few days ago, but progressively gotten worse. [Purchased this map 2 Days ago]

What's the recommended configuration for this map for my set-up? Any good tips to look out for to keep this issue in check?

I have the exact same problem - I turned all of my settings down - textures to medium and terrain to low. For me the preload radius didn't make too much of a distance. Actually, after a few minutes, it was using up 15.5GB of my 16GB RAM while barely touching my CPU.

I took some advice and downloaded Process Lasso which helped distribute things a bit more. It also offers the ability to "trim" RAM back if it's using too much. There are some further tips on how to use it here. Now, RAM gets to 13.5 or 14GB sometimes but rarely makes things unplayable like it did before.

Still, I'd rather like to find out what caused the issue in the first place. Absolutely no problems with memory on the Caucasus and NTTR maps. I really hope some more Persian Gulf optimization will be incoming.

Why would you expect a fix to increasing game system requirements?

Optimisation of system usage is likely to be helped with the planned standalone server and Vulkan updates.

As for the map, it is what it is. Either turn down your settings or look at more Ram.

provided log

https://forums.eagle.ru/showthread.php?t=219605

Selecting page file size to 'system managed' in Windows 10 solved all my crashing issues in DCS. For the record I've got 16GB.

Why would you expect a fix to increasing game system requirements?

Optimisation of system usage is likely to be helped with the planned standalone server and Vulkan updates.

As for the map, it is what it is. Either turn down your settings or look at more Ram.

Surely there is still something wrong when some people are using 99% of their memory on PG and all of the other maps are running fine, whether it’s 16 or 32gb.

I have PG. Yes it uses more, but NOT dramatically more, certainly not enough to call it a Bug (IMO).

Sukebe, if u have 70mins available u may load my track and monitor your ram usage, everything in cockpit view only, VR if possible, lets see if its system related

my specs, i74771,32gb ram, 1080ti, ssd, Rift

I just updated my DCS world and tried it again. Still the same buggy broken unplayable, unoptimised game!

Rain, did you download and give Process Lasso a try? I still have the same problem and it's helped a lot. Still not perfect but the PG map is playable at least. Frustrated that I still even have to use if with 16GB but it's worth a shot.

Necessary files for a PG multi mission:

2018-09-11 19:43:20.500 ERROR SOUND: can't alloc memory for 'effects\aircrafts\fa-18\f404ge_startnoise': 409664 frames, 2 channel(s)

2018-09-11 19:43:20.549 ERROR SOUND: can't alloc memory for 'effects\aircrafts\fa-18\f404ge_rpm1': 367091 frames, 2 channel(s)

2018-09-11 19:43:20.561 ERROR SOUND: can't alloc memory for 'effects\aircrafts\fa-18\f404ge_rpm2_front': 416466 frames, 2 channel(s)

2018-09-11 19:43:20.571 ERROR SOUND: can't alloc memory for 'effects\aircrafts\fa-18\f404ge_rpm2_side': 501418 frames, 2 channel(s)

2018-09-11 19:43:20.587 ERROR SOUND: can't alloc memory for 'effects\aircrafts\fa-18\f404ge_rpm3_front': 484728 frames, 2 channel(s)

2018-09-11 19:43:20.603 ERROR SOUND: can't alloc memory for 'effects\aircrafts\fa-18\f404ge_rpm3_side': 498764 frames, 2 channel(s)

2018-09-11 19:43:20.614 ERROR SOUND: can't alloc memory for 'effects\aircrafts\fa-18\f404ge_back': 373650 frames, 2 channel(s)

2018-09-11 19:43:20.624 ERROR SOUND: can't alloc memory for 'effects\aircrafts\fa-18\f404ge_shutdown': 1235578 frames, 2 channel(s)

2018-09-11 19:43:20.634 ERROR SOUND: can't alloc memory for 'effects\aircrafts\engines\enginege': 222325 frames, 2 channel(s)

2018-09-11 19:43:20.646 ERROR SOUND: can't alloc memory for 'effects\aircrafts\engines\rotorch53': 317368 frames, 2 channel(s)

2018-09-11 19:43:20.675 ERROR SOUND: can't alloc memory for 'effects\aircrafts\a-10\apu\apustart': 465790 frames, 2 channel(s)

2018-09-11 19:43:20.684 ERROR SOUND: can't alloc memory for 'effects\aircrafts\a-10\apu\apuend': 575475 frames, 2 channel(s)

2018-09-11 19:43:20.740 ERROR SOUND: can't alloc memory for 'effects\aircrafts\a-10\apu\apu1': 501253 frames, 2 channel(s)

2018-09-11 19:43:20.749 ERROR SOUND: can't alloc memory for 'effects\aircrafts\a-10\apu\apu2': 485044 frames, 2 channel(s)

2018-09-11 19:43:20.775 ERROR SOUND: can't alloc memory for 'effects\aircrafts\a-10\apu\apu3': 373909 frames, 2 channel(s)

2018-09-11 19:43:20.785 ERROR SOUND: can't alloc memory for 'effects\aircrafts\a-10\apu\apu4': 242506 frames, 2 channel(s)

2018-09-11 19:43:20.800 ERROR SOUND: can't alloc memory for 'effects\aircrafts\a-10\apu\apu5': 201494 frames, 2 channel(s)

2018-09-11 19:43:20.808 ERROR SOUND: can't alloc memory for 'effects\aircrafts\a-10\canopyopen': 424137 frames, 2 channel(s)

2018-09-11 19:43:20.827 ERROR SOUND: can't alloc memory for 'effects\aircrafts\a-10\canopyclose': 283920 frames, 2 channel(s)

2018-09-11 19:43:20.843 ERROR SOUND: can't alloc memory for 'effects\weapons\gau8cannonlow': 137309 frames, 2 channel(s)

2018-09-11 19:43:20.854 ERROR SOUND: can't alloc memory for 'effects\aircrafts\engines\sa342engine': 88194 frames, 2 channel(s)

2018-09-11 19:43:20.870 ERROR SOUND: can't alloc memory for 'effects\aircrafts\engines\sa342rotor': 583643 frames, 2 channel(s)

Then log ended, DCS silently crashed with 16GB RAM and 12GB of pagefile

the old 8GB of pagefile was 98 percent good for medium Caucasus and Nevada missions even with other programs running. These huge pagefile usage is very bad!

Ugh, that looks pretty frustrating. Could we get some information from the devs about whether those of us who purchased the Persian Gulf map and are having problems will now have to upgrade to 32GB RAM or if some kind of optimization is incoming?

I think you/we can just keep dreaming about optimisation, it will not happen, not in the nearest future. The day they released Persian Gulf they changed the system req. page because they realised its heavily unoptimised and broken. I haven't flown in DCS for months now. Maybe over a year because of how bad it is at performance, stutters, connection to the servers, disconnects, CTD's, memory leaks basically an all round broken and unoptimised game.

I can't help but think that:

- the latest OB does feel a little more "solid" in it's frame rate. Not sure what they've done

- ED do plan to introduce our standalone server. That would imply that they've got it to run independently of the graphics engine, and that there's a good probability of us being able to off load more tasks to another CPU core

- We know (as Wags has told us), that Vulkan is in development and coming for DCS

As, you post does seem a little unduly negative.

Just an observation I tried the PG map last night and it's performance still seems very sluggish with Rift VR, also the detail and visible range and just clarity seem somewhat poorer than NTTR (which BTW is still the best map VR performance wise!)

Okay with PG loaded basic free flight mission I had 11GB RAM used with a further 21GB assigned to pagefile with some 300MB actually committed and 52GB RAM available. (Yes I do have 64GB of RAM)

I've just upgraded from 16 gb to 24gb and what a huge difference its made. Before mp was locking up all the time and taking forever to load the terrain after switching back from the f10 map. Now everything is smooth without any freezes and my fps are improved too.

Will this be fixed in the near future or is the new minimum system requirement for the Persian Gulf map now 24GB Ram?

As much as many don't like it, 16GB is a thing of the past in DCS, same as HDD.

The System Requirements reflect it too, it's no secret and no fanboyism, it's actually official. I still wonder why many just cannot accept facts.

If you force your system to Hardpage Faults every now and then due to too little RAM, no wonder things stutter & crash, coupled with a PF on a HDD people ask for trouble everytime they want more than the basics from DCS.

Will this be fixed in the near future or is the new minimum system requirement for the Persian Gulf map now 24GB Ram?

A "fix" means that ED thinks that something is not working as planned/expected.

As such, we should be awaiting EDs comments either way.

I dont think RAM usage will go down anytime soon, it only knows one way since they left Floppy Disc restrictions and use Suites to write code. That is what an old programmer told me..and I think he's damn right.

People want new maps, higher LOD, more pixels, higher grade Radar, Ground Radar, dynamic weather and what not else.

We got most of it delivered from ED by now, now do your part and match your end to get the dream a working dream.

It says "8GB low graphics setting", "16GB for heavy missions"

"16GB high graphics settings", "32GB for heavy missions".

I got massive lags with med settings FHD in a mission with three aircrafts and one ground unit (so not a heavy mission).

If 24GB are needed, please ED make it the officiall min. requirement.

Two month ago 16GB worked fine with Persian Gulf missions.

My rig:

i7 2600K @ 4.4Ghz

16GB

GTX 970

Samsung 850 512GB SSD

My motherboard can only take up to 16GB and I was hoping to wait another year or two before upgrading my system. Hopefully they can either make this official or fix it. As was said before, many users are getting good perfomance in the Caucasus and Nevada. Surely the Persian Gulf needs some optimization. The Caucasus was the same - stuttery and RAM intensive when it first came out but then it got much better after a few updates.

i tested this with 128gb ram, no change, still stutters in the trk i provided

PG was perfect smooth for me when it got released, now not anymore

Persian Gulf is still in beta, so there is hope for a fix.

Persian Gulf is still in beta, so there is hope for a fix.

Persian gulf for me is stuttering since last 2 updates. Before it was smooth as silk