I found that the key to avoiding copious out of memory errors and CTDs with the new FS Labs Concorde (unless you have 64GB of physical RAM) is something I've cast nary a second thought to for many years--a sufficiently large paging file.

I tried probably 20 times to get the Concorde to load in P3D v5.4, while observing the working set memory allocation explode past 32GB and trigger CTD after friggin' CTD.  Haven't ever seen this happen before in the 64-bit environment.

Anyway, I had my page file size set pretty low (2048-4096 MB) as nothing has really challenged the VAS beyond the ample 32GB of RAM in the system.  But alas, 32GB turns out to be insufficient to accomodate the monster-size virtual working set space the Concorde is grabbing, particularly at startup.  Bumped the page file size up to 4096-32768 MB and the beast finally loaded.  Working set space for P3D has so far topped out north of 36GB here, with others reporting as high as the mid-40 GB range.  Keep in mind this working set number is the size of P3D's virtual address space, not the actual amount of RAM in active use while flying--active paged RAM usage appears relatively reasonable once the initial load-up is done...around 10GB of active pages loaded in RAM while sitting on the ground at Flightbeam's Dulles with a fair bit of AIG traffic.  Doesn't seem to be hitting performance from what I can see so far.

I can confirm that it will load. The commit is still around 24GB which is rather mind-boggling, but it's progress.

Cheers!

With v5.3HF2 and 32Gb RAM I’ve not had any crashes yet. Usage went up to 31500Mb using RTSS. I leave Windows to manage the page file.

16gb Here and, while it does take a *very* long time to load, I have more or less managed to load it successfully every time. I've my page-file left as default. So at least it can scale to a certain extent based on the physical memory in your system, seems like something that could very much do with some optimisation though.

Edited August 19, 20232 yr by SimeonWilbury

Just downloaded it, I'll see if my 64GB DDR5 would hold it.

Or if I'll be the one OOM with all it's systems and procedures.

Edit:

Just made a little C&D to local pattern, not clean system (lots of website, apps etc..) 43G on RAM and 71 G on System Commit, wow.

However I still only got 20~FPS in VC, while 50+ in other views, is that normal?

Edited August 19, 20232 yr by C2615

I had the same problem a while back: KIAD to EDDM in the A330, and as soon as I reached Britain's coast - OOM. Don't remember doing so, but it turns out I had set my page file too small. Also 32 GB, and IIRC, the size of committed memory was almost twice that.

Is this a programming issue which consuming insane amounts of memory?  I don't have any other apps which do this.  So far this addon is a hard pass for me till the memory situation gets tamed.

6 minutes ago, Skywolf said:

Is this a programming issue which consuming insane amounts of memory?

It sure seems that way. If they were just memory-mapping files on disk into the virtual address space, it would cause the working set to increase but not actually use the swap file (since the data is already on disk). It seems like they're allocating a tremendous amount of memory, but for what?

Cheers

Completely absurd there's a genuine concern about going OOM in the last half of 2023, in a 64-bit simulator. You'd think we were finally past that point and developers had enough experience to not let a single addon completely saturate your RAM like that. It's shameful.

2 hours ago, Sethos said:

Completely absurd there's a genuine concern about going OOM in the last half of 2023, in a 64-bit simulator. You'd think we were finally past that point and developers had enough experience to not let a single addon completely saturate your RAM like that. It's shameful.

You’re talking as if this is a widespread problem. Reading through the topics over at FSL it isn’t. I have 32Gb of RAM and it peaked at 31.5 but crucially the sim continued running.

Maybe the size of the page file is the issue as Bob alluded to. I’ve left my settings alone and no problems.

Using the page file is just substituting disk space for RAM, which is very inefficient and slow.  I can't believe a flightsim plane consumes so much memory and resources.

Dave

They’ll sort it out! Calm down! 😉

1 hour ago, Ray Proudfoot said:

You’re talking as if this is a widespread problem.

Excessive memory usage appears to be a widespread problem. Simulator crashes depend a great deal on one's swapfile configuration.

Cheers

47 minutes ago, Luke said:

Excessive memory usage appears to be a widespread problem. Simulator crashes depend a great deal on one's swapfile configuration.

Cheers

I don’t see excessive memory usage as a problem because it’s only a temporary thing whilst the HP computer is starting up. It drops to 15Gb or so soon after. Leave the swap file alone. Let Windows manage it.

As Ray said, may as well let Windows manage the swap file settings. I must admit I haven't even thought about tweaking the settings in my last couple of PCs.