Flying from Sausalito VOR (SAU) to KFSO VOR at 10,000' 225 kts in TBM 930 - empty community folder. Sim stable, scenery wonderful, clouds perfect. 

NO FrameGen  V-synch at 50% of 120Hz refresh rate on 4K monitor

~18 to 19 FPS / GPU & CPU time per frame @ ~54ms GPU@100% busy / GPU and VRAM at 98% usage / CPU 45% busy  / 26 GB out 64 GB used  
        TLOD@295 OLOD@195 DLSS@Quality All graphics @ High except Buildings and Clouds@Ultra

I then lowered each parameter significantly (shown below) one at a time and then all together.  In every one of the five change the Sim FPS jumped up to about 35 FPS and the GPU & CPU time per frame dropped to about 21 or 22 ms.  Then, EVERY time I changed a parm, the time per frame for GPU and CPU slowly increased over a period of 30-seconds and then steadied out at 54 or 55 ms and the FPS slowly decreased over the same time period to level out at 17 - 19 FPS.  That is exactly the same performance as before the change. 

TLOD reduced from 295 to 155
OLOD reduced from 195 to 100
DLSS reduced from Quality to Performance
Buildings and Clouds reduced to Medium

Made all the changes shown above in one change and reduced all other parms to Medium - same result FPS jumped to 35 and slowly lowered to 17 and GPU/CPU frame time increased from 20 to 55ms.

I then terminated the session and restarted it.  I flew the exact same profile with the same Graphics settings, Quality DLSS and no Frame Gen.  In the SAU to SFO leg the FPS was a steady 55 with GPU and CPU times at 16 to 17 ms.  The sim was very stable and performed wonderfully. 

How can two identical flights have such different performance profiles?

 

Edited April 16, 20251 yr by TacomaSailor

The beta has become a hot mess for me, performance has tanked and yes I've also seen two identical scenarios with massive differences in fps, the VRAM issues have certainly not been fixed either. 

They changed something a couple of updates ago to cause all this as it was running fairly well awhile back (still not good enough then but better than it is currently).

It's got to the point I simply cannot fly from medium sized airports because the FPS is so low,  if the public release is like this then I simply won't bother with it until SU3, not worth the effort.

I see a similar framerate reduction, particularly just after touchdown, dropping into the low twenties or even teens.

I have found that alt-enter to go windowed, then alt-enter again to back full screen restored my frame rate.

I use FG with a 60Hz monitor, so I have no problem with my system 'normally' holding 60FPS.

This is a new issue that I noticed in the last iteration beta to this one.

Stu

16 minutes ago, Bunchy said:

I see a similar framerate reduction, particularly just after touchdown, dropping into the low twenties or even teens.

I have found that alt-enter to go windowed, then alt-enter again to back full screen restored my frame rate.

I use FG with a 60Hz monitor, so I have no problem with my system 'normally' holding 60FPS.

This is a new issue that I noticed in the last iteration beta to this one.

Stu

When it happens I usually go to settings, switch global setting to low and switch back to custom (and work on each slider to a desired setting). This seems to "flush" vrams and restore the fps back. 

Edited April 17, 20251 yr by History

I'm doing a flight from KSDF to KOAK in the A300, had 70FPS in external view, 30 in the cockpit at KSDF but since I've departed I've had 30FPS no matter the view.

This is with frame gen, so actual FPS is around half that.

Yesterday I did a flight from MROC to CYYZ in the A330, couldn't get above 40, but later that day I did a flight from Christmas Island to Jakarta in the A320 and had 70 for most of the flight until I started approaching the airport when again dropped to 30-40.

Did a flight on Tuesday from San Juan to Miami in the A321Neo, around 60 FPS until I got close to Florida and when it dropped to the 40s.

the DevMode FPS counter says I'm hitting my main thread limit, but task manager says I'm only using 50% CPU power

I am using AutoFPS set to Frame Gen 60FPS

Found someone on reddit reporting similar issues

https://www.reddit.com/r/MicrosoftFlightSim/s/xFbU9TJbcH

Edited April 17, 20251 yr by Tuskin38

10 hours ago, Bunchy said:

I see a similar framerate reduction, particularly just after touchdown, dropping into the low twenties or even teens.

I have found that alt-enter to go windowed, then alt-enter again to back full screen restored my frame rate.

I use FG with a 60Hz monitor, so I have no problem with my system 'normally' holding 60FPS.

This is a new issue that I noticed in the last iteration beta to this one.

Stu

I've had that experience many times.  That is why I tried to change the parameters one at a time to see which might result in a permanent increase in performance.  Every change I make to a setting results in much lower GPU and CPU service time that slowly increases.  I carefully monitor VRAM and system RAM usage, working sets, page faults, hard page faults, disk and net I/O but none of those things change as the GPU/CPU time slowly increases while the FPS decreases.  

As others have said - this is very disappointing.  FS 2024 is wonderful when working properly and it does work that way much of the time.  But, at times a 64GB 9800X3D and 12GB RTX 4070S are not enough to get 20 FPS even with all settings at low and flying at altitude in remote areas.  

The sim will have trouble retaining, let along gaining members if they cannot resolve the issue. 

The PIX DX12 debugging tool provides a lot of very detailed information.  If ASOBO and/or Microsoft would issue a Beta (really Alpha) version with all debugging options allowed so we can see PIX events, markers, sim PDBs (timing per call or event) users like me (40+ years working on system/application performance measurements and tuning) could spend a lot of happy time delving deep into the problem.  Allowing we users access to the PIX data provides insight to many unique combinations of hardware and software that the developers might not otherwise have. 

I got rid of stutters and FPS issues by turning all "shadow" settings down to the lowest value and disabling ray tracing.

I have don't really see a difference in having ray tracing on or off FPS wise, just increased VRAM usage. 

I'm lucky enough to have a 4090 and have never come close to 24GB limit but regularly see the VRAM in the 16 to 18GB range in 4K, with the Fenix and FSLTL Traffic.

I have a 60Hz monitor and use FG, so 60FPS is my usual FPS state.

All my seetings are ULTRA apart from

Airport Traffic quality OFF

Air traffic OFF

Cars, boats, fauna HIGH

Depth of Field OFF

Motion Blur OFF.

Edited April 18, 20251 yr by Bunchy