jaxgator

I would take a look at Event Viewer after the error is generated. Perhaps you can acquire a little more detailed info as to what is causing your issue.

I'm not really certain on your question. Are you asking where the DLSS file is located? I am unsure about that. If you are asking where the tool I use to swap DLSS files (DLSS Swapper) is located, it's an executable that can be found here.

Not sure if this has been brought up or discussed yet but my 2024 performance was not up to par with my 2020 performance. Granted, the game is new and there would probably be some trade-offs but I expected at least similar performance with similar settings. I did not experience this. It was quite choppy compared to my 2020 version with is rock steady at 60 fps. Then I recalled that I needed to swap my DLSS file on 2020 whenever any update occurred because it would revert to a lower version. I checked the 2024 version and lo' and behold, it was using version 2.4.12.0 (on my machine anyway). I swapped that version out with current version 3.8.10.0 and sure enough, I started to see a lot smoother performance in 2024, similar to 2020. Just thought I would pass this info along to possibly help any others that might be seeing a performance drop between 2020 and 2024.

4GB VRAM (for 1080P) is the minimum spec while 8GB (for 1440P) is the recommended spec.

I took note of the EFB in the Grand Canyon preview and was very excited. I do not have subscriptions to anything, MSFS or otherwise. If Navigraph offered a one time payment, I would consider it depending on cost but no subscription for me. After showing the EFB in more detail in this video, I think it may be one of the best features, for me at least.

None here. I am going to wait to see how much individual planes from the higher tiered versions cost before I decide which version I want. While there are more detailed airports, there are not many planes that I want in the higher tiered versions. If the individual planes are rather inexpensive, I will just buy the Standard version and then purchase those planes that I am interested in from the higher tiered versions. On the other hand, if the individual planes are rather expensive, naturally, I'll just go ahead and purchase the higher tiered version that includes the plane(s) that I want.

@Sethos Just an update on my memory timings. After adding an additional fan to keep the memory cooler (as I thought was the issue) I ended up with the following. I couldn't tighten tRCDWR/tRCDRD any lower as my PC wouldn't POST. I have yet to try and get tRP any tighter. I also have not tried to disable PDM since not POSTing when I tried it before. My BIOS would not let me go any tighter on the tFAW setting. 20 was the lowest setting in BIOS. Almost 5 hours on absolut without any errors so I am pretty pleased with that. I also adjusted voltages a bit and think that helped get these tighter timings. Do you see anything else I might try to tighten in my timings?

Yes, I believe that is the current official build. However, they are still in the process of rolling it out to all users through Windows Update. I had to go grab the iso to get it installed.

FS 2024 does not support DX11, it will only support DX12.

This is exactly what I was thinking. Because there is more available ram, more is allocated which allows for more of the resources being downloaded to go straight to ram versus the page file. If those resources are instead on the page file, a hitch occurs when they are paged into ram. Just a guess on my part though.

Doesn't clearing the rolling cache within the sim do the same? I keep rolling cache off myself so don't know. I wonder if it is also clearing nVidia cache files as well because that will also give a performance boost. I'll have to see if I can find the .BAT file and take a look at what it is doing. Edit: Ok, yeah, it's doing what I thought. It is deleting both the MSFS rolling cache file as well as the nVidia DXCache and GLCache files. I typically delete the nVidia cache files manually and the MSFS rolling cache file in game (when I used to use it) but can see how this little .BAT file would be of use as it's just one double-click and all cache files are deleted.

It's not dropping to 50 TLOD on the ground because you have the + box (next to TLOD Min) checked. Uncheck that box and it should give you your 50 TLOD on the ground. Checking that box tells AutoFPS to give you more than your minimum if it can.

I don't know about new airports but here is an extensive list of 2020 airports (credit JetWash1023 on MSFS official forum) that should be ported over to 2024 with a Google Maps locations link (credit masdeca on MSFS official forum) as well. Edited to format text in quote as copy/paste did not work as I expected.

Yup, I believe Asobo knows this and that is the reason for the "Ideal" specification. If one doesn't run a lot of supporting apps alongside MSFS they will be just fine with 32GB.

And there ya go. MSFS is using 16.6GB of memory. The other 20.4GB is being used by other apps.

His image is showing entire system memory usage because he is on the Performance tab. A better depiction of how much memory MSFS itself is consuming is to use the Processes tab and then click the Memory column to sort descending as shown here. Don't be fooled by my low memory usage in MSFS as I was only on the main page.

Agreed. Asobo currently has dynamic LOD in Xbox but it is very poorly implemented and doesn't have enough user flexibility as AutoFPS does. If they don't improve it for the PC version, it will essentially be useless.

Yeah, I'm thinking my case doesn't have enough fans and this is a heat issue. I just reset to use only EXPO profile and am running new tests. So far, so good. Thanks for the suggestion on resetting to EXPO profile, test, adjust a few timings, test, etc.

I am getting errors in MemTest5 on every setting I have tried except for the default one on my first run. I have tried absolut, Extreme and am just got done running DDR5 Ryzen3D and received 3 errors in Test 2 on that. I haven't had any issues in Windows and ran MSFS for a 3 hour flight yesterday without issue. Does anyone know what "Error in Test 2" means? I found the following on overclock.net on a post about MemTest5 but it says it applies to default MT.cfg (no longer exists) and 1usmus_v3.cfg (have yet to try).

Apparently, the power down mode issue I was experiencing was not some one-off case. There are many others experiencing it as well as shown by the following Reddit thread:

Don't feel bad. I couldn't either. lol I didn't take a screenshot but completed the test which took a little over an hour and 45 minutes without issue. I will apply the changes mentioned by Sethos and give it another shot later.

Saw your post on my phone and the memtest was only 20 minutes in so I shut it down. Yup, you were right that I had rev 1.3 so I grabbed that latest version of BIOS and installed it. No change. When I tried to save and exit BIOS after changing only the memory power down mode, BIOS locked up and froze. Just going to live with it enabled. I don't think it would have any affect when I am using the PC, or would it? One other question: When running the memtest, should I not be doing anything else on the PC? You know? Like maybe browsing the web. I wouldn't think so but thought I'd ask anyway. Thanks again fellow flier.

As you probably already saw, I ran into issues tinkering with the voltages so reset everything and then after re-applying the timings changes, did nothing with the voltages. For some reason, I seem to have issues when disabling power down mode. BIOS would freeze sometimes as soon as I disabled it. When it didn't, I would get Windows infinite boot loops with the blue screen and sad face emoji. It's currently enabled as I am afraid things will go haywire again if I enable it. I thought about updating BIOS. I am currently on version FA2 but can't find any information about that version anywhere. The current version is F32b for "(rev. 1.0/1.2) rev. 1.3 rev. 1.1" X670 boards on their website but I don't know how to determine what my version is. I guess I will leave it enabled for now. Going to run the TestMem5 now as suggested. Again, thanks for all of your help Sethos!

No, I do not. I tried making these changes and ran into all kinds of problems. Took me a couple of hours to get it all straightened out. Ugh! All good now. Whew.

I use PerfMon to monitor page file. Start > type "perfmon".