I'm having low FPS and stuttering issues as well with a pretty high end system, though I've managed to make it better.

My specs:

RTX 5080
i9-14900KF
64 Gigs Ram
OLED 240Z 45" monitor - running it at 3440x1440

Settings and Tweaks

I moved everything from Ultra to High.  This improved performance quite a bit.

AutoFPS

DLSS and Frame Gen enabled

240 refresh rate

Performance

Anything above 10,000 feet is golden (100+ FPS)

Most airports I'm fine on taxi, take-off and landing, but busy areas (e.g., around Seattle area during peak times) and I get the stuttering and FPS can go as low as 10

Still getting way to many 20 FPS runs on taxi and ground to my liking

Observations

VRAM definitely has a big impact on performance.  Before tweaking my settings I was seeing VRAM usage at 97% and unplayable stuttering (5080 is a 16G card). Not sure if a combination of setting adjustments or updates by MS, but now seeing 70-85 and better performance.

CPU and GPU wattage draws and heat look pretty normal (CPU is watercooled).  CPU rarely reaches 70, and GPU kinda all over the place but doesn't get to 70 ever so I think I have some OC and wiggle room there.  Wattage draw combined from CPU and GPU is in the 300-350 range but sometimes spikes to 400.

Questions/Comments:

What settings are you guys using for autoFPS?

I feel like some planes perform better than others.   Getting good results in the Wilga but the default Vision Jet seems to have more FPS issues, but this is anecdotal.

Following the thread for troubleshooting advice.

 

 

 

 

14 hours ago, Cpt-Harry said:

I’ll find out which of my CPU threads are the strongest or act as the MainThread, and with Process Lasso I’ll bind MSFS 2024 only to those.

You can use Ryzen Master to assign MSFS' to the #1 and #2 fastest cores on your 9800X3D and use maybe 2 of your 8 cores to assign to all other Active Processes in Process Lasso.  I've read the 'main core' in 2024 does not commit to only one core, though I see Core0 (called 1 on Ryzen Master) being used heavily even though it's not ID'd as the fastest or second fastest core, but I sense we're splitting hairs there as the diff between cores won't be that much.  Here w/ a dual CCD CPU I have MSFS' set to use all 4 of the fastest cores + 4 others  (0-5 + 8, 10), and assigned all other processes to 4 of the lesser cores (7,9,11,12).  I tried closing off Core0 to MSFS thinking it might force it to use Core1 but alas Core0 continued to get more utilization most of the time despite that--but System stuff runs on it as well.  

 

Edited April 1, 20251 yr by Noel

7 minutes ago, WolverineHusky said:

Observations

VRAM definitely has a big impact on performance.  Before tweaking my settings I was seeing VRAM usage at 97% and unplayable stuttering (5080 is a 16G card). Not sure if a combination of setting adjustments or updates by MS, but now seeing 70-85 and better performance.

 

 

 

I was disappointed when I saw amount of ram on 5080, and 5090 is out of my range. It's still much more ram than the 10G on my 3080 though so worth consideration.

12 minutes ago, WolverineHusky said:

Most airports I'm fine on taxi, take-off and landing, but busy areas (e.g., around Seattle area during peak times) and I get the stuttering and FPS can go as low as 10

Is that without FG? In any case, it is quite low. I use AutoFPS to handle TLOD, which has the largest impact on CPU load. At the biggest airports, TLOD can go as low as 50 in order to maintain my target FPS. 

12 minutes ago, WolverineHusky said:

VRAM definitely has a big impact on performance.  Before tweaking my settings I was seeing VRAM usage at 97% and unplayable stuttering (5080 is a 16G card).

MSFS2024 can use a LOT of VRAM. If you get unplayable stuttering, more VRAM is probably used than your GPU can deliver. AutoFPS should prevent this from happening with the in-built VRAM overflow protection. Other than that, you could try without Ray traced shadows - that draws a considerable amount of VRAM. 

12 minutes ago, WolverineHusky said:

What settings are you guys using for autoFPS?

I set a TLOD Min of 100 and Top of 200. I prefer the FPS Cap method and lock FPS to a value I can reach most of the time with my hardware. For me, that value is a little above 60 (I use ATC addons and lots of AI traffic which is very heavy on the CPU). 

The "reduction settings" in the latest test builds do also help a lot in tight situations by reducing things like e.g. ray traced shadows and cloud/tree quality (and much more). I have a lot of success with those. 

25 minutes ago, Cpt_Piett said:

 

Do you believe there is little to no 'hit' (that for example might be picked up as a small spike with CapframeX) when these changes are made during runtime?  I thought I had seen some of that with DynamicLOC in 2020 when flying over western Europe esp east Germany. 

24 minutes ago, Noel said:

Do you believe there is little to no 'hit' (that for example might be picked up as a small spike with CapframeX) when these changes are made during runtime?  I thought I had seen some of that with DynamicLOC in 2020 when flying over western Europe esp east Germany. 

Yeah, I don't notice anything negative as a consequence of AutoFPS changing various settings. 

But come on - a small spike on the frame time graph? I do get that all the time in various aircraft with or without AutoFPS. To get rid of those I'd probably use all my waking hours tweaking...

Quote

5 hours ago, Cpt_Piett said:

Is that without FG? In any case, it is quite low. I use AutoFPS to handle TLOD, which has the largest impact on CPU load. At the biggest airports, TLOD can go as low as 50 in order to maintain my target FPS. 

MSFS2024 can use a LOT of VRAM. If you get unplayable stuttering, more VRAM is probably used than your GPU can deliver. AutoFPS should prevent this from happening with the in-built VRAM overflow protection. Other than that, you could try without Ray traced shadows - that draws a considerable amount of VRAM. 

I set a TLOD Min of 100 and Top of 200. I prefer the FPS Cap method and lock FPS to a value I can reach most of the time with my hardware. For me, that value is a little above 60 (I use ATC addons and lots of AI traffic which is very heavy on the CPU). 

The "reduction settings" in the latest test builds do also help a lot in tight situations by reducing things like e.g. ray traced shadows and cloud/tree quality (and much more). I have a lot of success with those. 

 

 

Thank you for this!  I will do some adjustments based on your advice.

Yea, I was disappointed in the 16 ram for the 5080.  I was trying to get the 5090 but was priced out with the tarriffs and price hikes.  Thankfully I paid MSRP for my MSI 5080 Gaming Trio pre-tarrif ($1150).

Will upgrade to a 5090 eventually......

EDIT:

So tested out AutoFPS with generally these settings and worked wonders!  Definitely much happier.  Updated to this AutoFPS build as looks like a test version but worked great.  

First run I still maintained all "High" settings and ray tracing off.  Flew the Wilga from KPAE to KRNT in the Seattle area.  This flight usually gives me trouble in 2024 as a lot of scenery, buildings, details and planes (I ran multiplayer on).

Breezed through the flight north of 100 FPS and mostly 120ish.  Landed in the 80s, which was fine.

Temps (low 60s on the GPU) and VRAM (70s) all solid.

Only complaint is not the greatest fidelity on high settings.  Was a light drizzle in Seattle (live weather) and the rain drops on the windows produced artifacts instead of rain drops.  I feel like I can trouble shoot that. Ground fidelity was above average, but the bridges didn't look good.  I think this is fixable since my temps and FPS are solid.

2nd flight flew out of Santa Monica and headed north for a short 45 minute flight.  For this flight I enabled Ray Tracing and bumped some settings up to Ultra, e.g., trees, buildings.  Still mostly high but bumped a couple things up.

Still pretty solid.  VRAM went to around 82% (acceptable) and my FPS was more in the 80s when compared to prior flights.  That is acceptable to me I can totally live with 70 FPS.

So thanks again, This really helped and I feel pretty good about the 2024 experience with the 5080.

Edited April 2, 20251 yr by WolverineHusky