4 hours ago, abennett said:

or are simply blind to them, or ignore them on purpose and just want to jump on the bandwagon of MSFS2024 is the greatest thing

Now that to me is amply disrespectful.  I don't have borked landings as you and some others describe.  I hope you/they get to the bottom of it as soon as possible.

I'm using SU3 and do experience some frame drops on approach, so far it's not been that bad - but there are caveats, I fly mostly GA into small airfields, I don't fly that often so my testing is limited.

2024 is a step forward in the following areas

Disk space

Loading times

Rocks and pebbles 

In every other case it's been a backwards step and a right abomination - imo 

 

1 hour ago, hanhamreds said:

In every other case it's been a backwards step and a right abomination - imo 

But you are still using it. And enrolled in the Beta. Which means you must still think its better than 2020? Otherwise ............... ?

Edited June 4, 20251 yr by St Mawgan

16 hours ago, abennett said:

If other users don’t have them, or are simply blind to them, or ignore them on purpose and just want to jump on the bandwagon of MSFS2024 is the greatest thing since sliced bread, then good for them. But they are very real and are documented by many users.

I have no doubt that the “stutters on final approach” is a very real problem that clearly affects many users in SU2 and beta SU3. But - it does not happen to everyone. It does not happen at all on my system. The question is: why? I have done many approaches at default JFK and LAX with the Aerosoft CRJ and PMDG 777F and 772, and there are no stutters or frame rate loss on final approach and touchdown whatsoever.

I don’t run at full 4K but at 1440 resolution. All graphics settings “high” except clouds, which are at “ultra”. TLOD and OLOD both 150. My system is reasonably powerful but not state of the art, with a 3080Ti GPU and 10900K CPU.

I do have “fauna” set to off but everything else is enabled except AI traffic.

If you run out of VRAM momentarily (common when loading up an airport on approach), that can produce stutters … so can a million and one other things from settings, to scenery, to any other add-on, or even streaming of data from MS servers.  

If one is an FPS chaser, then the change in frame time will be much more noticeable say when running 120Hz monitor, you run 100 FPS then drops to 40 fps vs. 60Hz monitor, you run vsync 60 FPS and drops to 40 fps.

Suggest you monitor/log VRAM/FPS/RAM/CPU to file at the same location/airport on approach and see if that reveals anything (several tools to do this from Afterburner/RTSS, nVidia native, AMD native, Intel PresentMon).  Intel PresentMon will monitor more accurately as it’s not limited to 100ms sample rate.

34 minutes ago, JRBarrett said:

The question is: why? I have done many approaches at default JFK and LAX with the Aerosoft CRJ and PMDG 777F and 772, and there are no stutters or frame rate loss on final approach and touchdown whatsoever.

Yep, why? This suggests there is nothing fundamentally wrong w/ the performance-related elements in 2024 else no one would report what you and I others experience.  Last eve after dark flew the Fenix 320 into JFK and nary a stutter anywhere and the rate was maintained at 50FPS-native save a few drops to 48 obscured enough by Gsync during taxi to avoid stutters.  And you know well some to many of those posts re this issue indeed have to do w/ VRAM on board, high levels of TLOD, weak hardware, etc.  Apparently not all but again, all very different scenarios for sure and would range from that 90fps drop to 10fps to drops much less severe that have people chiming in.

2 hours ago, hanhamreds said:

In every other case it's been a backwards step and a right abomination - imo

I find the sky vastly more plausible in 2024 than 2020.  Not always 'prettier', but matching real world visuals more.  I don't miss the canopy of METAR haze over every big airport and city in 2020.   On top of that seasonal changes are a nice plus as is heightened detail on the ground, smoother road traffic.  I am stunned by the quality of detail from on high now flying over the Colorado Plateau recently including lighting changes.  This makes 2024 superior for airliner use as well as GA.  The EFB really has some fabulous capabilities, typically put down by comments in the thread:  love the built-in charts for arrival, importing Simbrief is a snap even in default birds and even though high end airliners come with their own it's nice to have a useful EFB for default planes, three of which I use.

 

18 minutes ago, CO2Neutral said:

(several tools to do this from Afterburner/RTSS, nVidia native, AMD native, Intel PresentMon)

Might you know how I can find out which core(s) a specific process is running on?  I've searched and not found something to do this with!  I'm curious about one utility I use with both MSFS sims and it causes my CPU fan to run high even after the sim is out of the picture.

10 minutes ago, Noel said:

Yep, why? This suggests there is nothing fundamentally wrong w/ the performance-related elements in 2024 else no one would report what you and I others experience.

A lot of LOD and scenery objects were modified/upgraded for SU2. My guess is there is one or two objects that are not optimized properly and can tank FPS as a result. I have experienced this slowdown exactly once for a few seconds on one of the landing challenges (I'd need to go through them again to remember which one). Probably a lot of variables that add up to whether this issue happens or not.

5 minutes ago, Noel said:

Might you know how I can find out which core(s) a specific process is running on?

The only way I know how to monitor this with any degree of accuracy is via Visual Studio 2022 and having the source code available and running from the IDE/Debug.

You can try Process Lasso to set thread affinity, but that doesn’t always work pending the executable code and its reliance’s … Process Lasso comes with some overhead.  IMHO, it’s better to leave the OS to manage the threads along with chipset drivers provided by AMD/Intel.

I know in P3D, setting Affinity could be a benefit, but that was done internal via .cfg settings.  Don’t get me wrong, Process Lasso might help some older PCs running older chipsets using older version of Windows.  But for more modern applications/games/sim etc., I would suggest keeping Win11 updated along with chipset drivers.

As far as fan running at high RPM … is there any core activity and high temps at the time?  What are you using to control fan speed … temperature source?

1 hour ago, CO2Neutral said:

I know in P3D, setting Affinity could be a benefit, but that was done internal via .cfg settings.  Don’t get me wrong, Process Lasso might help some older PCs running older chipsets using older version of Windows.  But for more modern applications/games/sim etc., I would suggest keeping Win11 updated along with chipset drivers.

As far as fan running at high RPM … is there any core activity and high temps at the time?

I use PL to assign MSFS 20/24 to CCD1, the CCD using L3 cache, plus the 2 other fastest cores on CCD2, and all other processes go on to the remaining 4 cores on the 9900X3D.  For some weird reason this utility does not seem like it should be nearly as demanding as are the sims, and yet the fans spin fast until it's shut down.  So yes it's some/one of the 4 other cores that have high activity until it's shut down.  I contacted the Dev who says it's not happening to him, so it's one of those things, just like the landing issue described in this thread, that affects some and not others.  He's suggesting to try changing the audio driver which I haven't done yet but will.

5 minutes ago, Noel said:

and yet the fans spin fast until it's shut down

You didn’t answer my question … what are you using to control fan speed?  And what temperature source is driving the metric the fan(s) use?  And finally how many fans and which fan?

I had a PSU that ran the fan at 100% until I discovered there was a eco mode switch … since the PSU fan is not control by anything other than the PSU it took me a while to discover the problem.

19 hours ago, CO2Neutral said:

You didn’t answer my question … what are you using to control fan speed?  And what temperature source is driving the metric the fan(s) use?  And finally how many fans and which fan?

I had a PSU that ran the fan at 100% until I discovered there was a eco mode switch … since the PSU fan is not control by anything other than the PSU it took me a while to discover the problem.

The CPU fan control works fine, modulates with demand.  I'm using MSI Center's controller.

In MSFS 2024 catastrophic fps drop at TO and landing, today with the default TBM, unusable (but it happens with the liners too). Almost all the Inibuilds/Asobo Airbuses and the B737max have the wing flex asymmetry syndrome. The question should be what's missing from MSFS 2020.

Edited June 5, 20251 yr by Claudius_

9 hours ago, Noel said:

The CPU fan control works fine, modulates with demand.  I'm using MSI Center's controller.

Ok, so how many fans do you have and which one(s) are “spinning fast until shutdown”?  Are you using multiple fan controlling software and/or EFI?

The Noctua NH-D15 G2 has two fans.  I have case fans but it's only the CPU fan that spins fast when this utility runs.  If I shut only it down, the fans slow down so are much quieter.  If I shut MSFS down, no change.  Or anything else, no change.  Something about that app is demanding and TM shows sometimes as high as 36% CPU utilization when it's operating.

TBH I only wonder why a utility that should not be anywhere near that demanding and yet it's behaving as it if is CPU wise.  Despite this the sim performs very well.  Maybe PL has helped some there.

Edited June 6, 20251 yr by Noel