20 minutes ago, CFIJose said:

That's incredible! You must be running your sim at low to medium settings. My important settings are at ultra. TOD from 50-300 with auto fps.

It depends on the airport & the AI traffic that you load. The FSLTL fleet has a higher Vram footprint than AIG. Some airports eat up Vram. A good example is Dreamflight KTEB. If you have it, test the Vram with and without the airport.

It's also the cumulative effect of all these airports and a major city. If the user enables everything it could lead to a slideshow or a CTD.

I run everything at HIGH settings with TLOD and OLOD at 250/200 respectively.

Too add, since adding 32GB to bring my rig up to 64GB (2 sticks total), I have seen a smoother sim with MS2020. I am running volanta, x2 Streamdecks and vpilot at the same time. 

I like what I'm reading about the added smoothness of upgrading to 64. Great job party people!

1 hour ago, CFIJose said:

I like what I'm reading about the added smoothness of upgrading to 64. Great job party people!

In preparation for MSSF 2024 I came across a good deal on another 32 GB RAM Kit so now I have 4 matching 16 GB sticks for a total of 64GB.

Currently, with MSFS2020 running, I also run two StreamDecks, Active Sky, Say Intentions, Navigraph Charts, the Steam app, AuthentiKit tuning app, Axis and Ohs, Map enhancement app, LSFG at X3 and FSLTL. MSFS2020 was smooth  with excellent frame rates with 32 GB of RAM and going to 64 GB made absolutely no difference whatsoever nor did I expect it to. I am also dubious about the need for 64GB in MSFS20204. Time will tell, I guess.
 

2 hours ago, Jure said:

Ok, so I am not imagining things. 🙂 Also went to 2x32Gb yesterday and this morning's flight out of iniBuilds' EGLL with over 100 AI seemed smoother than usual. Running ASFS, LittleNavMap, Volanta, Spad.next, AIG, FSHUDv.2

Yeah, I don't know if it is necessarily helping MSFS and by that I mean if we were only running a vanilla MSFS would going from 32-64 help, probably not but like me you run quite a few add-ons so I think that is where it is benefitting MSFS...  Hope that makes sense. 

17 hours ago, VeryBumpy said:

Won't having lots of Vram like 24Gig of a 4090 be more important than having lots of system memory?

Yes, way more important than system memory.

I'm not about to jump from 32 to 64 until I'm sure it is helpful. Orders from Amazon get here in 2 days or less. So if I ever need it, will arrive shortly. 32 GB Corsair cost me $78 last October, is now priced at $88, I guess prices going up.

Just realized my out of the box Alienware R10 setup is 2x16GB DDR4 2666 with CL 22 timing.  just bought a 2x32GB of Kingston Fury DDR4 3200 with CL 16.  

The timings and speed diff alone should be a nice boost. 

Now I'm just 32% less CPU and 27%less GPU than the "Ideal" spec with my 5900x and 3080ti

Everything else is Ideal. Hoping for decent VR performance as I picked up a Quest 3 a few weeks ago. If 64GB proves insufficient I can still grab another pair of the same memory for only 100 USD

4 hours ago, Sethos said:

Seems that also confirms that even in MSFS 2020, 64GB makes a difference. Lots of hitching in some of the scenes with 32GB.

Though it's curious that it's actually not using up the full 32GB, it's not even close to the limit and it's still causing lower performance and hitching. Wonder if there's a technical explanation for that, perhaps a bug that causes it to hit the page file unnecessarily or something?

Windows will manage memory and not allocate the entire RAM available to one application alone.  It will allocate only a percentage of what is available so if you have 64MB then there is more available to allocate and avoid paging sooner than if you only had 32MB available.

9 minutes ago, FlierHawk said:

Just realized my out of the box Alienware R10 setup is 2x16GB DDR4 2666 with CL 22 timing.  just bought a 2x32GB of Kingston Fury DDR4 3200 with CL 16.  

I hope you made sure that the memory that you purchased is compatible with your A10.  Alienware boxes tend to be quite finicky when it comes to RAM.

3 minutes ago, jaxgator said:

Windows will manage memory and not allocate the entire RAM available to one application alone.  It will allocate only a percentage of what is available so if you have 64MB then there is more available to allocate and avoid paging sooner than if you only had 32MB available.

I hope you made sure that the memory that you purchased is compatible with your A10.  Alienware boxes tend to be quite finicky when it comes to RAM.

Oh I fully understand RAM provision to an application but you won't convince me a guy running a benchmark has almost half the RAM provisioned to something else, compromising the entire benchmark. It barely uses 16-17GB while it shows massive hitching and awful 1% lows. That's half the RAM unused. That's unusual.

@Sethos I'm looking into my BIOS settings now and just re-read your previous posts:

Quote

Make sure your FCLK and UCLK are 1:1, i.e divisible by your memory speed or you're essentially just making your setup slower / higher latency by only overclocking the speed of your RAM. Just in general with the X3Ds, once you move past 6000MT/s, you might actually see a drop-off in performance as 6000 in a 1:1 setup is probably the absolute sweet spot of the X3Ds. You are much better off getting optimized timings at 6000MT/s, with FCLK at 2000 / UCLK 3000.

First off, to your other post using CPU-Z, for easier overview, you should give ZenTimings a try. Gives you a quick overview of what your timings are, speed, FCLK, UCLK and everything in between; https://zentimings.com/

So for 6000MT/s you want FCLK at 2000, UCLK at 3000, then it's all divisible by 6000. Then as linked in this thread as well, a lot of people like to use Buildzoid's timing, which work really well with my Hynix kits and gives you a good boost

Here's my BIOS:

ZenTimings:

I'm very unfamiliar with FCLK and UCLK. Would it make sense to do these BIOS changes?

Edited September 27, 20241 yr by Cpt_Piett

19 minutes ago, Cpt_Piett said:

@Sethos I'm looking into my BIOS settings now and just re-read your previous posts:

That should do it, at least have you running at 6000 MT/s, 2000 FCLK and 3000 UCLK. Then use the overhead from backing down from 6200, to improve your timings.

If you want to run 6200MT/s, just set your FCLK to 2066Mhz instead, 2066 x 3 = 6198, rounded up 6200. Then that's also 1:1

7 minutes ago, Sethos said:

That should do it, at least have you running at 6000 MT/s, 2000 FCLK and 3000 UCLK. Then use the overhead from backing down from 6200, to improve your timings.

If you want to run 6200MT/s, just set your FCLK to 2066Mhz instead, 2066 x 3 = 6198, rounded up 6200. Then that's also 1:1

Wow, I have been out of the PC building game for a bit but that is some really in depth knowledge!  Is this all specific to AMD or DDR5?  

Impressive stuff.  

18 minutes ago, Sethos said:

That should do it, at least have you running at 6000 MT/s, 2000 FCLK and 3000 UCLK. Then use the overhead from backing down from 6200, to improve your timings.

I was able to get 30-38-38-30 at 6000MT/s. At CL 28 the system wouldn’t boot. I tested with TestMem5 and it’s stable. Haven’t tried the sim yet.

Interestingly, even with a physical memory load of 98%, there's negligible page file usage.  

Edited September 27, 20241 yr by Cpt_Piett

Just remember, AMD only guarantees 5200 MT/s on the 7800x3d.