Well, for me and a lot of people that are mostly on lower systems than yours (but not all of them) we used to have a lot of huge stuttering at regular intervals for 2 to 10 seconds where the game was unresponsive as it would suddenly go down to unusable 9-10fps with CPU usage going to 100%. The more the crowded the scenery was, the more you’d have those and the closer they were between each. Oddly enough, game was smoother back then in between with higher FPS most of the time than after patch 2. One surprising thing too was that if you alt-tabbed your way out of MSFS and let it run in the background during one of those massive drops, despite still being under 100% CPU, the game would run nicely despite a few FPS loss. But as soon as you alt-tab your way back in if it was still under 100%, then it would massively drop again and become unresponsive.
After patch 2 though, none of this occurs anymore. I could be all wrong, this is just an assumption, but I feel like it was tied to how the scenery was loading in “big bursts” so to speak that plagued older systems resources too much at regular intervals as the faster the plane was the more often it used to occur. (I’m using an old i7 4790K OC@4.6 with a 1070 and 16GB RAM, a system that, otherwise, gives me very satisfactory performances in high or even close to Ultra in 1080p).
What I fear is that, for lack of a proper solution yet, in the meantime they chose to downgrade the game (so to speak) for everybody, effectively momentarily taking care of this problem at the expanse of graphics while they investigate the matter more deeply.
I hope it’s not that, especially for people with high-end rigs who shouldn’t have to deal with this, but that would make some sort of sense.