Thank you I’ve commented on the FBW Github, hopefully they can figure out what is going on
If that’s true then Windows’ memory manager is broken. As was mentioned, standby memory is basically a cache which should be released should other applications require more physical memory. This is why task manager does not count standby memory as used physical memory.
2nd this - flew STL-MDW-DTW – started great, by time is got to DTW it was 1/3 of the FPS
And it sure did! This is a eureka! exactly as expected!! Just did a flight with all the bells and whistles without a Hick-up
What was the registry edit that you did to “fix it” ?
The solution (solved) is located on the very first post
how can I do the CPU check to see if one of my cores if getting eaten up?
Task Manager. I forget which tab but it should be self-evident when you find it.
Ah… that is probably the famous CPU LOD bottleneck. In short, your Terrain and Object Level of Detail settings as well as traffic settings (especially airplanes) might be just a bit too high.
LOD seems to be sent to the last CPU core, and if set too high, it tends to max out the CPU, especially at big airports. And if one core gets maxed out, the whole computer is throttled to keep all cores in sync with the slowest core.
When the GPU is the bottleneck, your FPS slows down. When the CPU becomes the bottleneck, you get immersion breaking stutters (and those are terrible).
You may want to check Dev Mode in sim, and follow the steps listed in this linked post and subsequent posts in the same thread.
This thread talks about maintaining a locked 30 FPS but if you have the system for it, you can maintain a locked 60 if you go for 15 ms instead of around 30 ms.
But if you don’t even acknowledge that there could be an an issue, then you do not have to address it … (or even deny there is an issue)
Going forward, this may well get know to be “The Aerosoft Effect”, as they seem to have perfected this form of customer support.
Performed the NDU registry change and still had FPS drop.
Next, I just removed the Toolbar Pushback after using it for the past several months. Performed a flight DTW-CMH. No FPS drop, using the FBW (latest exp) sitting at the gate after landing in CMH for 1hr. GPU still at 100%, same frames as when departing DTW.
Seems like the Toolbar Pushback jacks up the performance. THRILLED I can finally perform multiple leg flights
The basic design of Windows memory management has been the same for more than 20 years. It isn’t broken. Windows is designed to process many different types of programs from email to word processing to web browsing to games to watching video to video editing. Windows is designed to run these programs on many different hardware platforms. According to the MSFS FAQ, the minimum memory spec is 8 GB. I wouldn’t recommend this amount of memory to anyone. However, the design of Windows memory management allows MSFS to run with only 8 GB.
Windows is NOT designed to run only MSFS or even to run MSFS optimally. One “workaround” is to buy or build a PC specifically for MSFS…
As far as FPS decreasing or stuttering as memory utilization increases, this is because Windows moves parts of memory to the paging file virtual storage to accommodate programs needing memory to run. If any part of MSFS memory is moved to the paging file, FPS will drop or stuttering will happen because when MSFS needs that memory that is on the paging file, Windows has to retrieve it from the paging file and put it back into memory if there is room. If there is no memory available, Windows finds other memory to move out to the paging file to make room. All this takes time and even though it happens very fast, a few milliseconds delay is a stutter or a drop in FPS.
Windows memory management allows users to run MSFS, Navigraph, LittleNavMap, and a web browser to watch YouTube all at the same time.
When Windows starts moving memory around MSFS performance starts dropping. Personally, I watch my memory utilization and as soon as it gets to about 50%, I start looking for any unnecessary programs to stop.
If this were an option that it should be possible to define what that is, and if that can be done then it should be possible to look at any system, and find what is missing to make it so that it is.
my mainthread is going through the roof over time.
starting with 50-60fps going all the way down to mid 20’s and low 30’s.
I run the sim at ultra preset 3840x1600
Sim is installed on an SSD, same happens with an empty community folder.
i7 10700k (stock)
32GB 3200mhz stock xmp profile.
3080ti not overclocked
1TB nvme (where the sim is installed on)
So after around 45 mins of flying from BHX and now West of Paris, which is notoriously heavy around CDG, im still getting solid fps. At the weekend over the same area i was getting around 20-25. All ive done is remove the latest better pushback mod from the community folder.
Can confirm, landed back at BHX after 1.5hours of flight over france and back, the FPS is exactly the same as when i took of at EGBB in the same spot as when i landed with Better push back removed. I was using the FBW A32N mod. So for me it was the better push back mod thats caused all this issue. Hope this helps some of you.
I’m wondering if the memory leak has to do with the gate vehicles and animations in general. I removed Toolbar Pushback and that has helped - the sim was buttery all the way up to the gate. But when I called the tug and catering and baggage carts from the FBW flyPad, my FPS went down. Not nearly as badly as before, but still noticeable.
I am really thinking airport tasks like those you mentioned hit the CPU and lower FPS. Airports in general are really taxing on the CPU in MSFS whereas flight generally taxes the GPU.