I had this issue happening to me today, flying from Paris CDG to Niamey, Niger. 5h of flight.
I was down to 10 FPS on landing. Restarted the sim, same flight-plan, same arrival airport, 25 FPS
My GPU was fine but my CPU was taking a hit, I also had some CoherrentGTdraw activity.
I was using :
-Hangar9 787 XE 0.0.5
-FlightSim.to Niamey Scenery
-Multiplayer Live Mode
-Real Time AI traffic functionality enabled BUT AI Traffic disabled
-Moving map NOT disabled
Disabling the VFR Map did nothing for me in mid air.
VRAM and RAM werenât maxed out.
Will try tomorrow offline and with the VFR Map disabled before hand
EDIT : issue still here, FPS seem to decrease linearly as time passes, currently investigating memory
My system:
CPU : i7-4790K @4.00GHz
GPU : RTX2060
VRAM : 6Gb
RAM : 16Gb DDR3 1600MHz
Drive : SSD 860 EVO 1Tb (Good Health)
VR Headset : Oculus Rift S
Since the UK update, a good 6/10 flights once they reach the 1 hour mark go from steady frame rates in 50s to 60s or higher down to 5fps and lock ups. Did a few flights yesterday and did not happen, so its hard to replicate.
i5-10500
2070 super TI
32GB Ram
1TB SSD M2
So frustrating ill get an hour through a beautiful VFR flight and bam, its unplayableâŠ
So annoying because i actually love this game and its the first time its given me any grief.
Strange thing happened to me, on a flight just now, from sundown to night. Started off FPS 40. Soon as I took off FPS went down to 20s, howevrr it was not jerky (to my eye) still flysble a32NX. Also had situation where FPS had dropped to 10. All sliders 100%
All my settings are high apart from clouds on ulra. and cockpit refresh medium.
GPU was 60% utilized
CPU from 50% to 70% utilized
(Monitored with MSI)
Temperatures were normal 60 degrees with cpu
75 degrees with GPU
System is 9 3950x
Widescreen monitor
Nvidia 2080 TI
64mb Ram
2 TB SSD only MSFS installed on other games installed on my other 2 TB drive
None of it makes sense to me, despite reading all the explanations and I am no computer expert. I have read most of the forums.
I had like zero issues for 3 months with MSFS before WU3. I can replicate the FPS drop from 45 to 10 by starting flight from ICAO: 21W and flying towards Seattle for 5 minutesâŠ
Found a fix for me by using ISLC v1.0.2.2 ! It was the standby memory growing until all the memory was used that caused the terrrible FPS. I hope this can help some people.
EDIT : Standby Memory which is named âCachedâ is not shown in the âin Useâ, thus it seems I have plenty of memory left but in reality no. (i.e, in the second pic, I have 16Gb, so 15.9 usable, and 15.9-10.2-5.7=0 Gb left of actual memory)
This is before the memory maxing out problem, there is plenty of free memory left, CPU color is all yellow :
This memory analysis is very sketchy. What is âfree memoryâ exactly? The Task Manager screen captures donât agree with the app info.
1st example: App shows 1872 MB âfreeâ - Task Manager shows 8 GB available - No explanation for the difference.
2nd example: App shows 6 MB âfreeâ - Task Manager shows 5.7 GB available - No explanation for the huge difference.
3rd example: App shows 7056 MB âfreeâ - Task Manager shows 7.7 GB available - No explanation for the difference although the numbers are closer.
The total memory in use and available doesnât show memory exhaustion at all.
1st example: 18.4 GB in use - 39.9 GB available
2nd example: 20.9 GB in use - 39.9 GB available
3rd example: 19 GB in use - 39.9 GB available
The app doesnât show any information about Working Set Size, Committed Memory, and GPU Memory used, all very important for any memory analysis.
The 2nd example tries to make the correlation between available âfree memoryâ and FPS performance. However, there is still plenty of memory available according to the Task Manager. The application seems to ignore how Windows performs memory management. The claim in the 2nd example of only 6 MB free is questionable especially when there is about 19GB of memory not in use. There may be multiple reasons for poor FPS but lack of âfree memoryâ isnât one of them.
Based on the examples shown, I doubt users would obtain any benefit from using the application and might have worse performance overall. I recommend that users donât waste their time installing it to âtry it outâ.
Thatâs because Standby Memory isnât shown in this view of the Task Manager. In the âResource Monitorâ you can clearly view that your memory is full due to Standby Memory, so purging it will help.
I should have shown this window instead.
What is sketchy is that windows doesnât show Standby Memory in the main view of the Task Manager.
Itâs literally an app that offloads Standby Memory when itâs taking all of your RAM, because on some machines windows doesnât offload it fast enough, so it wonât do any harm.
I recommend users to check their âResource Monitorâ to see if they have 0 memory left due to Standby Memory, in which case this tool is the life saver.
In the main view, you have to calculate it like that :
Available Ram = Total Ram - In Use - Cached
In the second photo,
I have 16Gb of RAM so 15.9 usable
15.9 - 10.2 - 5.7 = 0 Gb left available
And I believe that the 39.9 is my pagefile on my SSD drive, but Iâm not sure at all about that.
For my case, without purging the memory, after 2h of flight my memory looks like this :
It seems to be that the airport I take off from never gets offloaded from the memory, because I don"t have such issue when beginning the flight in mid air
(Photo from a microsoft forum)
There is no way to determine what is in memory without analyzing a core dump of the OS. It is possible to list all the files a process is using but that doesnât mean those files are in memory.
Anyone using any tools that mess around with Windows memory needs to clearly understand How Windows manages memory. The screenshot of Resource Monitor shows 35% Physical Memory Used or 2882 MB used. This leaves 5130 MB Available (or Standby). This memory had been used by processes or threads no longer running. Windows marks these memory pages as Available. The Free Memory of 0 MB is not meaningful. If a process or thread needs additional memory, Windows allocates memory from the Available pool.
If a process or thread requests more memory that is available, Windows looks at the In Used memory for memory not used recently. Windows then moves enough memory pages from real physical memory to virtual memory on a disk. When that memory is needed, Windows moves it back to real memory. It is important to understand that Total Memory = Real Memory + Virtual Memory.
tldr; Sorry for the long explanation but Windows Memory Management canât be described in 25 words or less except by saying, âIt works as designed.â
Pausing the sim and waiting for a minute lets the sim clean up itâs memory on its own. Iâve seen that a lot over London, commit keeps going up, pause the sim, commit goes down again. When commit reaches 40 GB (on my 16 GB physical ram system) it crashes.
It doesnât always work or can take a long time. Sometimes the game falls behind or leaks memory, no clue. I fail to see how an external program can re-arange memory use of another program. It seems more likely youâre just giving the game time to clean up without new data coming in while paused.
This didnât help. I can now replicate the FPS drop by departing ICAO: 21W and just climbing with CJ4 towards west, FPS drop always starts at around FL200.
Sorry, I think we have a different problem, because my FPS usually degraded linearly over time because of memory being used more and more as time passed, incredible amount of similar issues yet different.
Thereâs something going on with water as well. I had a big fps drop just from flying a couple hours of the ocean. Commit memory 17 GB, active memory just over 5GB, perfectly fine. Yet it was all very sluggish, no clue why. It did clear up after landing and departing again at the next island. Static build up, plane needed to be groundedâŠ
Sorry about my last post, indeed you were right it appears purging standby memory wasnât the fix for those who have little memory like me, it was a mean coincidence, I donât know why my performance went back up at the same time I purged though.
I am flying again and purging memory has no effect.
But what seemed to have solved my issue on the 787, is to go in exterior view, wait a couple of seconds, the sim froze for 10 seconds, and came back with the fps back too. Maybe linked to the cockpit screens idk.
Okay so I just retried to go in exterior view and now the fps donât come back, another coincidence. What is sure is the sim froze for a couple of seconds and then the fps came back
I notice it as well that the frame rate goes down when I leave it on its on for a couple hours on auto pilot. Somehow not interacting with it slows it down. After a landing fps goes back up again, but not always. Sometimes only after restarting the game.
Maybe with no use input windows goes into some sort of sleep state making life difficult for the game, causing fragmentation in memory perhaps. Thatâs all I can come up with when it doesnât have the issue when flying over complex terrain for hours (while interacting) while the fps tanks over a long empty stretch of ocean.
