I wish the Asobo and Microsoft Flight Simulator teams would consider adding a better way to control memory resource management.
What I specifically mean is this:
Currently the sim aggressively tries to unload resources from memory to keep it clean for future demands which is a good thing but also can work against itself. For now the sim unloads stuf from memory as soon as you turn your eyes away from it or you are a little bit far away… meaning few miles away!!
This could be OK for heavy scenery like big photogrammetry cities but it becomes a stuttery annoyance when assets like houses or objects from a small scene are unloaded just because they are being passed by the aircraft only to be reloaded with a huge stutter when the aircraft turns around like is the case on a airfield pattern. And is not the loading of the high speed nvme that produces the stutter per se but the fact that the object needs reprocessing of LODS and shadows and materials and all and the sim can’t just fly along as they get loaded and processed it seems it needs to stop to sync everything.
We’ve been promised with DirectX12 this will be improved yet… especially on PCs with big amounts of RAM looks still like an unsolved yet easy in appearance problem.
Just stop unloading stuff that is close to the plane. Just give us a slider. The preload stuff in the settings appears to “control” just how uch is loaded but not the aspect of aggressive unloading it afterwards.
But isnt this because this sim wasnt built specifically for you and your setup? When I started using the sim I only had 16 gigs of memory so flushing memory was obviously a good thing. Any sim has to work around the limitations of the general hardware being used. It’s not always about just you
I think this point is a bit of a distraction.
MSFS 2024 has recommended system Memory specifications as 32GB of RAM and ideal 64GB.
as you can see it here:
My system has 32GB and while monitoring the RAM load it never goes dangerously to 32GB in most of my flying sessions.
If one flies in New York for example with a lot of mods and photogrammetry one can expect some shaffling but in a… Romanian country side I wouldn’t expect such problems.
Why my example matters?
Because Romania is in East Europe it doesn’t have any sim update over it so no special features there other that rather good terrain elevation data and aerial textures. So if I fly around a spot without any objects usually nothing happens, it’s a breeze for the sim, but if I create a scenery in DevMode and add some base MSFS objects and fly around the scene again I have pause of obvious reloading of the scene.
It’s a small airfield, some objects placed there nothing crazy all MSFS base. If I fly a bit away (but still in visual distance… say 2 miles maybe less the scene objects are unloaded… sometimes they are hidden by some forest or hill… when I pop out and they need to be draw again… the system hicks up because… “oops… we thought you went away chef”. This is an unwanted behavior. There is nothing around to require more space so no “anticipation” excuse either. Just aggressive and overzealous memory cleaning.
And before someone comes with the funny “turn off antialiasing if it doesn’t look nice enough for you” type of comment 
I have 10Gbs internet optical fibre and play from France. So no, it’s not the internet nor the wifi as I play with PC wired and wireless VR and the headset doesn’t have any issues.