It’s pretty common place with PC games to set your expectations lower than trailers show, depending on your system. FS2020 is a bit of an outlier in that it sort of self destructs when it falls behind.
As you see from the screenshots I posted earlier, my system can produce beautiful scenes, if I give it enough time to keep up (about 30 knots moving speed). Scroll up a bit and you see what happens when I fly at 180 knots.
It’s a balance between bandwidth, memory, cpu speed vs draw distance, altitude and movement speed. The GPU is the last piece of the puzzle and really only matters for resolution and fps.
Now what I don’t envy Asobo for is the task to get this running on a Series X. Of course people are going to try to fly low and fast over the Thames, expecting 60 fps and visuals as seen in all the trailers. I hope it doesn’t turn into a CP2077 train wreck. Yet the tendency to self destruct when resources run low needs to be solved somehow. Series X has 13.5 GB available for games, Series S only 9 GB at most. At least the CPU speed is good at 3.6 and 3.8 Ghz. My system’s 16GB is definitely not enough to fly over London at regular speed.
Testing what terrain level might work
Terrain detail at 100
Starting with 19.8 GB allocated (down from 23.7 at terrain 200)
My CPU and RAM cannot keep up at 187 knots
But after leaving the PG area it manages to recover
Memory allocation is already up to 27.2 GB though
But the sim survived (still crashed, forgot the landing gear )
28.7 GB allocated, 150 hard faults/sec, it’s barely alive, need more ram.
Heathrow is also a resource hog of course (I have ground aircraft density at 10% to help with that)
Restarting the sim from desktop, trying terrain detail level at 50
17.8 GB allocated (down from 19.8 GB with terrain at 100)
It’s keeping up longer but still falls behind and I see it updating right in front of me
Memory allocation went up to 20.9 GB
Fine outside the PG area, memory allocation dropped a bit to 20.1GB
And another belly landing (I get it now, I’m sending the ‘g’ to the resource monitor, not the sim haha)
Heathrow drove memory use up to 21.2 GB
Can London even fit in 16GB, terrain and object detail at 50, high settings for the rest:
17.7 GB allocated, still doesn’t fit. Such a resource hog!
It runs buttery smooth, mostly, still hitches when the pagefile gets hit
Memory use up to 19.6 GB
Successful landing, heathrow drove memory use up to 20.7 GB
Btw back to my regular settings (terrain 200, object 150) without PG data starts at 22.6 GB, goes up to 25 GB allocated over London and spikes to 29 GB allocated while landing at Heathrow. Runs pretty smooth though (minor pagefile stutters) and has no problem keeping up with the AI generated scenery.
In conclusion, PG really needs 32 GB Ram minimum, or go very slow.
System requirements should be, minimum 16 GB, recommended 32 GB, ideal 64 GB