25 minutes ago, TacomaSailor said:

 

win 11 25H2  Sim 1.6.34.0

I am having very poor performance at an airport (any airport) which in the prior sim session (same day) I had excellent performance.  

For example empty Community folder KBFI (Boeing Field, Seattle) with Asobo Baron G58 cold and dark on a GA medium ramp.  

Sim starts at 60 FPS (FG and sim locked at 30).  If I stay out of cockpit and pan around I see a steady 60FPS.  Enter  cockpit, turn on systems, start engine, CTRL+Z and pan - the frame rate drops to 1 or 2 and sometimes freezes for 15-seconds.  Return to cockpit and frame rate slowly climbs to 60.  Move view outside again and poof! back to one or NO FPS.   If I let the sim sit for several minutes the frame rate climbs to 60 and stays there.  But, as soon as I try to start taxing - FR goes to 1 again.

Changing sim settings to LOW - no increase in frame rate.

The VRAM usage stays below 95% (~11 GB) and the CPU usage, for each processor, never exceeds 30%.  When the frame rates is less than three I find every thread in the sim is in a wait except for Main which is using about 1% of the CPU.

Stop sim and restart it, with the exact same scenario as above - FPS never deviates from 60.

This happens at many airports and makes SU4 less than enjoyable or even useable. 

Did not have this problem in the last couple SU 4 Beta updates

exactly on my end too the case. Build .34 is a stutter mess with high FPS fluctuations (from 90 drops to 45 or 30 and spikes up to 90 again...
ASOBO messed up a superior build .33 after the beta ended. How they come to this glorious idea? UNbelievable.
Build .31 and .32 where SUPERIOR stable with steady constand high FPS

9900X3D

5090 RTX

64GB RAM

So no release number? How do I know what version I have? 

23 minutes ago, RobJC said:

So no release number? How do I know what version I have? 

Said the same thing on the 1st page of the thread. Evidently, there's no concern.

1 hour ago, 0stones0 said:

Said the same thing on the 1st page of the thread. Evidently, there's no concern.

Simple answer: 

If you are playing MSFS 2024 (and aren't in the beta), you are on the latest release version. The server simply does not allow you to play with an old version. The only exception is if you are literally in flight when the new version launches .. it does not shut down the sim. 

But the very next time you launch it, it will NOT work till you update it. Also remember that MSFS 2024 (unlike 2020) can be and is silently updated by the Microsoft Store as well.

So even if you don't see a download, if you know that an update has been released at lets say 8 AM Monday, and you start your sim at like 10 AM Monday (giving a couple hours for the files to update across the world and so on), and it works.. you are on the latest release version and the Store updated it in the background. 

You simply cannot play 2024 with an older version once the new one has released and is fully available.

Same logic in the Beta stream - you will always be on whatever latest beta is released. You cannot stay back on a older release version, no matter how much you want to 🙂

Edited December 16, 2025Dec 16 by JonathanC

And if you want to check - just start the sim, and do Alt-Enter. Then you will see the version number in the window title. 

1 minute ago, JonathanC said:

Simple answer: 

If you are playing MSFS 2024 (and aren't in the beta), you are on the latest release version. The server simply does not allow you to play with an old version. The only exception is if you are literally in flight when the new version launches .. it does not shut down the sim. 

But the very next time you launch it, it will NOT work till you update it. Also remember that MSFS 2024 (unlike 2020) can be and is silently updated by the Microsoft Store as well.

So even if you don't see a download, if you know that an update has been released at lets say 8 AM Monday, and you start your sim at like 10 AM Monday (giving a couple hours for the files to update across the world and so on), and it works.. you are on the latest release version and the Store updated it in the background. 

You simply cannot play 2024 with an older version once the new one has released and is fully available.

Same logic in the Beta stream - you will always be on whatever latest beta is released. You cannot stay back on a older release version, no matter how much you want to 🙂

How is a software team in 2025 not able to put release numbers on builds? JFC. 

1 hour ago, RobJC said:

How is a software team in 2025 not able to put release numbers on builds? JFC. 

? They do. Every build has a release number. 

I don’t think you’re discussing this to get a solution, so I’ll step away and let you discuss this with someone else. 

5 hours ago, RobJC said:

How is a software team in 2025 not able to put release numbers on builds?

really, how stupid must they be. let the avsim users help out. 🤣

I start MSFS always via the Xbox tool.

21 hours ago, JonathanC said:

? They do. Every build has a release number. 

I don’t think you’re discussing this to get a solution, so I’ll step away and let you discuss this with someone else. 

Please step away. 

17 hours ago, turbomax said:

really, how stupid must they be. let the avsim users help out. 🤣

I start MSFS always via the Xbox tool.

I get the homerism, but is it that hard to put it in the release notes section? I mean, they somehow figure out how to do it 50% of the time. 

I've found that there are a bunch of stutters initially, and I've had to reboot two or three times necessary something hasn't been right with the stock aircraft - missing nav data, unable to three managed modes on the stock A320, etc. There's also the annoying things like KPHL is apparently showing a bunch of general aviation parking at the terminals.