But that is not how this sim utilizes resources. The VRAM usage is tied primarily to the complexity of the scenery being generated not to the way it is processed.
I did exactly as suggested on Wed night. I decided it was time to work on finding that sweet spot on my system. I fired up the sim and parked on the ramp at a complex airport near a photogrammatic city and started tweaking sliders and options. My VRAM sat pretty steady at about 4.5GB the whole time, regardless of settings. My committed CPU ram went up as I changed my LOD settings but otherwise was also pretty steady around 20GB. What changed significantly as I tweaked was CPU and GPU load. When I started I was Limited by Main Thread and my GPU was never above 55%. By the time I was done I had managed to shift the load from the CPU to the GPU to the point where now I run about 75% CPU and 95% GPU at around 45fps. That’s a 15 fps bump from where I was.
Point is. MSFS does not use resources the way we are used to seeing This is mostly about processing the images and not about how much data is being committed. VRAM usage will likely never approach the levels you saw with GTA. You WILL see a massive CPU RAM commit in some areas. This is why it has been shown that although the sim will run on 16GB, CTD are prevalent if the available Virtual Mem + DRAM does not EXCEED 32GB. This title is far more PROCESSOR centric and managing your GPU/CPU load ratio is key to getting stable FPS.