Just spent the last few days upgrading to FS2024 from FS2020. Just tried to do my first flight and im faced with very poor performance. FPS on the ground is not bad. 40-60 unless I panned the camera. In-flight, however, the sim tuned into a total slide show. Saw FPS as low as 8. Never had any problems in 2020 with this system. Any help appreciated. 

AMD Ryzen 7 9800X3D, RTX 5080, 32GB DDR5

 

Edited December 22, 2025Dec 22 by james42

Well, your screenshot seems to be the INIBuilds A350 which I believe is know to be a FPS killer. Try another AC and see what happens. 

Do you really have the monitor plugged into the 5080 and verified that you use the 5080? This looks like using the iGPU to me...

32 minutes ago, AnkH said:

Do you really have the monitor plugged into the 5080 and verified that you use the 5080? This looks like using the iGPU to me...

Yes, monitor definitely plugged into the 5080. 14 FPS with frame generation on. 

Try turning down some settings and try again. Ultra-high settings are way more aggressive in 2024 then they were in 2020.

3 minutes ago, Bigmack said:

Try turning down some settings and try again. Ultra-high settings are way more aggressive in 2024 then they were in 2020.

I have nothing on ultra apart from off screen terrain pre-caching. Everything else is either high or medium. 

15 minutes ago, james42 said:

I have nothing on ultra apart from off screen terrain pre-caching. Everything else is either high or medium. 

Is your Community folder pretty busy w/ perhaps a conflicting addon?  Even though DevMode says you're GPU limited the Main Thread is being hammered severely.

https://chatgpt.com/share/694987c8-da48-800d-87eb-15c875008f80

Edited December 22, 2025Dec 22 by Noel

Are you running out of RAM?

Copilot says:

In FS2024’s FPS overlay, peakallocmem refers to the peak memory allocated by the simulator during your current session—it’s essentially the high watermark for memory usage.

Here's how that works:

• The Developer Mode Rendering overlay not only shows FPS, but can include live statistics like AllocatedMem or peakallocmem. These indicate how much memory (RAM) the simulator has allocated at any point. [forums.fli...ulator.com], [forums.fli...ulator.com]
• For example, forum crash reports often include lines such as AllocatedMem=15733903360, which means the simulator allocated approximately 15.7 GB of RAM at its peak before shutting down. [forums.fli...ulator.com]
• So the metric you see on-screen labeled peakallocmem shows the maximum memory allocation—helpful for tracking memory usage spikes in real-time during gameplay or testing.

Why It Matters

• Performance monitoring: If you encounter stutters or low FPS, seeing a high and sustained peak memory usage can signal that you’re hitting memory limits and stressing system resources.
• Troubleshooting: Knowing the peak allocation helps narrow down issues like memory leaks or inefficient content (e.g., ultra-high-res textures or heavy add-ons).

With my system which is quite similar i have around 60-90 fps in that situation (with DLSS "quality").

There is definitively something wrong on your system.

All drivers up-to-date? Nvidia 591.59?

CPU cool?

Yes, what @Noel said. Did you empty your Community folder? Don't use any add-ons at all. Just use one of the default planes, like the Cessna 172 G1000. Don't use the iniBuilds A350 as @lehbird said.

Report back and let us know.  This is how to pinpoint problems in the software development, by using the process of elimination (once you figure out what is causing the problem, you can fix it and use the iniBuilds A350 again).

Edited December 22, 2025Dec 22 by abrams_tank

To "empty" the Community folder, just rename it. And then create a new Community folder that is empty. This way takes only a few seconds to do. 

I predict OP problems will all disappear when community is emptied. I'm also the guy who yesterday on Hangar Chat predicted the days will now get longer. (It was solstice yesterday, LOL).

Because emptying Community just rescued me. I had stutters briefly approaching airports and fps interruptions when taxiing. And while flying, short 1/2 second pauses from time to time which caused spikes in the Developer Mode FPS readout CPU color. 

The strange thing is that all the folders in community are planes (about a dozen of them). 

All these issues completely disappeared after cleaning community. I'm locked at 60 fps (V-synced locked at 1/2 monitor rate which is 30. And then Nvidia Smooth Motion exactly doubles that to 60). So that RTSS fps digit readout is a bright orange 60 the whole flight. It never briefly goes to say 59 on approach or anything like that.

Before cleaning community, it would drop to maybe 27 for a second or two while taxiing along at Gaya Heathrow. Now it's pegged at 60, just like it used to be before this issue popped up.

I have no clue to why a plane that I'm not even flying in community causes these issues. 

 

Just ran a few tests. 

First test, I loaded up the INI A350 on the runway at KMIA and left it there for around 15 minutes. Everything started off fine. After around 10 minutes, my mainthread started to take a serious hit, which brought the sim to its knees.

Second test, frame generation off, empty community folder, default 172 on the runway at KMIA. Sim remains stable, no FPS hit.

Now, I've installed the INI A300 and introduced it to the same scenario. Been sitting here for 20 minutes. Slight FPS hit. But no mainthread issues.  

I've come to the conclusion that the A350 and frame generation are the sources of the problem. As soon as frame generation is enabled, the mainthread takes a massive hit. No matter what the aircraft. GPU drivers are fully up to date. Why would frame generation be causing such issues?  

 

 

  

Edited December 22, 2025Dec 22 by james42

Redundant. 

 

Edited December 22, 2025Dec 22 by JonathanC

Your fps counter clearly shows the problem: you almost over the GPU VRAM budget ( see the yellow message ), because your settings are too high and you are close to VRAM exhaustion and when that happens, the performance drop is dramatic.

Try running at High instead of Ultra, then try raising individual settings but keep the memory well within limits. Use a dense airport.

Edited December 22, 2025Dec 22 by virtuali