I wanted to share my recent findings and ask for advice. After weeks of tweaking, I finally managed to make MSFS 2024 somewhat stable — but I still face a major issue after landings. Here’s what I’ve done so far:
• I capped the framerate at 30–40 FPS.
• Enabled DLSS Frame Generation (3x).
• Running TAA anti-aliasing.
• Settings are mostly High and Ultra.
• Configured my Ryzen 9 9950X3D to use the 3D V-Cache cores specifically for MSFS.
I am using an RTX 5090, 64GB DDR5 RAM, and resolution 3440×1440.
With these tweaks, things are generally smooth:
• Stable frame times at 10–20 ms latency during taxi, takeoff, cruise, and even descent.
• Frame pacing is acceptable, and FPS stays steady.
• Overall, the sim finally feels “flyable.”
The problem starts after touchdown:
• Latency drops significantly once I land and start taxiing.
• FPS also dips slightly, but the main issue is the loss of smoothness due to inconsistent frame times.
• Even when FPS seems okay, the sim feels choppy and less responsive after landing.
This happens consistently, and I can’t figure out why.
I’ve spent weeks stabilizing my setup, but this post-landing latency drop ruins the overall experience.
Is there something specific about MSFS handling after touchdown? Could it be related to terrain or AI traffic loading near airports?
Any recommended tweaks or insights would be much appreciated.
You have the best of the best system and still have issues. I am running a 2080ti on a 6 year old machine and don’t have many issues. I think something else might be going on and not just the sim.
I’m curious - why do you keep creating new threads about your Ryzen 9 9950X3D, RTX 5090 and performance issues? It seems like all of them are about the same underlying problem - your poor performance in MSFS 2024. It would make more sense to keep everything in one thread so people can actually help you more effectively.
I’m also wondering why, with such top hardware, you’re relying on FG? I’ve got weaker hardware myself - a Ryzen 7 9800X3D, RTX 4090, 64GB and I don’t play with FG.
And honestly, there’s no need to keep tweaking your Ryzen - it should already work well, since recent BIOS and Windows 11 updates improved how this CPU works. Tools like Process Lasso are unnecessary at this point. The more you tweak, the harder it becomes to find the real solution - you’ve probably already lost track of what’s actually causing poor performance.
Start your testing with an empty Community folder. Fly the Cessna 172 Skyhawk G1000 over Manhattan. Make sure all traffic is completely off - both on roads and water (also static aicraft) and disable fauna as well. Focus on testing this scenario and don’t create 50 threads
I have no idea why my perfomance is bad but this thread is about latency loss after landing and seems i already fixed main issues I hope, but latency and fps after landings is still here. Why am i playing with FG? Because without FG i only have maximum 50-60 frames and it does not make more - I have no idea why (GPU is not loaded by the way). No smootles and no good experience at all. Why all games and especcialy 2020 run good on this setup? Maybe because they all are well optimized or something like this. I tried to work with Lasso because people from the forum gave me some advices about it. I tried today without lasso - it’s almost the same but audio stutters came out totally i hope. Is MFS 24 works okay right now? Nope - whatever I do It is still with freezes stutters and latency and fps dropes. No idea what to do with all this mass.
And for a game like MSFS that is plenty. Professional sims all run on 60 fps. I never understood why people want more because there are no fast moving objects in the sim.
It’s been a while back, but we did some extensive tests on FPS at an event. Two systems, one locked at 50 fps, one on 100 (very basic scenery). We asked people simply to tell is which was which. Everybody was sure they could see the difference, but in the end the answers turned out to be statistically random.
For smooth gameplay 60 FPS is enough. In my opinion, simulation smoothness is more important than chasing 140 FPS. I’d rather have a stable 60 FPS without stutters than 140 with stuttering.
Limiting FPS to, for example, 60 also means less stress on the GPU - less stress results in lower temperatures not only for the GPU but also for the CPU, and overall better efficiency.
It’s also worth mentioning that if you, for example, cap FPS at 60 in NCP, the input lag will (or should) be lower compared to leaving the FPS uncapped.
It’s important not to cap FPS below the refresh rate range of your monitor panel. For most Full HD and 2K panels, the lower limit is 48Hz, so for example, capping at 30 FPS is not recommended. A 30 FPS cap makes sense on 4K monitors, since most of them have a lower limit of 30Hz. Of course, you should always check the lower refresh rate limit of your panel to be sure.
In general, you don’t need 140 FPS for flight simulators - I really don’t understand this obsession with chasing FPS. MSFS 2024 is not a shooter, it’s a simulator.
I don’t really get your point. If other games run fine on your system, then don’t chase the rabbit - it makes no sense.
Test the sim without extra programs - if other games and even MSFS 2020 run fine on your setup, then stop looking for problems on your side. It’s the MSFS 2024 developers who need to fix the performance, not you.
Man, I completly agree with everything. Btw Lasso really not needed now (thanks for the advice), without him it’s more stable. But the main point is I have latency drops (with fps drops) after every landing. And if on a320/737 it’s almost okay and I can taxi without big stutters and A350 from INI in completly unflyable. Every camera move, every camera switch in my cockpit causes stutters with latency drops (it
appeares almost every flight). MFS2020 does not have anything like this. I can start new flight after I have parked at the gate. Now in MSFS24 I need to close my sim and only this can fix high latency and fps drop.
P.S. screen attached (when I starting a flight latency is usually green, sometimes yellow with no sttuters and red lines).
The thread below is what you should read. People with all kinds of hardware (including yours) are reporting this very issue there.
The fault does not lie with your setup, it is a bug which has already been confirmed by Asobo and will most likely be fixed during the SU4 beta phase. You may wish to consider joining the upcoming beta phase if this is a game-breaking issue for you.
I see you’re not really reading what people write to you. I told you to test with the default Cessna without traffic but you’re testing other aircraft with traffic enabled. If something is wrong with the INI A350, then report it to them. I also suggested not to chase the rabbit: if MSFS 2020 works fine, then stop stressing about MSFS 2024. It’s simply not a polished sim right now - it’s full of bugs, so many you can’t even count them. Someone already shared a link to one of these known issues. So again - stop chasing the rabbit. MSFS 2024 is not ready yet
Just enjoy MSFS 2020 and wait for updates to fix 2024.
