I have lost count of the number of posts documenting the stuttering problem. Briefly the stuttering problem happens at random times and places while flying. The FPS significantly, usually in half, for a short period of time. The stuttering stops suddenly and “normal” flying resumes. There have been so many reports that indicate the stuttering is not specific to any hardware, aircraft, location, weather, time of day, monitor resolution, graphics parameters, Community folder add-ones, or anything else.
Here is a screenshot taken during stuttering while flying yesterday. The items marked explain what happens when stuttering starts. The information here is very “Windows technical”. You do not need to know any of this to use MSFS.
#1 - Red Not Responding - MSFS is busy doing something else and cannot respond to the user inputs. This doesn’t last too long but definitely breaks the video stream processing. FPS is decreasing.
#2 - MSFS is reading into memory a large number of files at the same time. Notice the file names like “bush trip”. I am not flying in a bush trip and haven’t for months. Flight tutorials are being loaded into memory. The screen is not big enough to show the entire file list. (Note small scroll bar on the right.) Also, different files and different amounts of files are read into memory from the same subdirectories during other stuttering occurrences.
I have no idea what is triggering MSFS to read these files at this point or any point during the flight.
#3 - The performance graphs show the impact of these files being read by MSFS.
CPU utilization decreases because the amount of graphics processing is decreased while the files are being read into memory. Also, MSFS isn’t doing any processing of these files once they are loaded into memory.
Disk utilization is very high because of the large amount of files. File sizes vary and larger files take longer to read into memory.
Network is not busy. Sometimes there is a lot of network activity during the stuttering if scenery files are being downloaded into the rolling cache.
Memory utilization is growing as more files are shoved into memory.
#4 - Because of the large number of files MSFS is putting into memory, Windows has to make room for them quickly. Also, Windows doesn’t know how many files will be read into memory or exactly how much space will be needed. To prevent a complete system freeze, Windows moves some memory pages from RAM to the paging file. If MSFS needs any of those memory pages to continue running, Windows has to move them back into RAM. Because there already is a lot of disk activity, the moving of memory pages adds additional load.
When the files have finished being read into memory, the stuttering stops, at least for awhile.
If the developers FPS counter is displayed during stuttering, it shows the the FPS is limited by the main thread. This file processing does limit the main thread as shown by the CPU utilization decrease.
Several users have posted decreased stuttering after reducing the object level of detail. The stuttering decreases because when the CPU is available during all this file activity, it is processing scenery files. Decreasing the graphics completely allows more frames to be processed during the file crunch.
Also, this is NOT the memory leak problem. When stuttering stops as described above, Windows cleans up any unused memory. The memory leak problem never restores the FPS.
