I re-flew ORD-OMA tonight to stress-test the sim and recreate the problem, which was successful. Here are the steps I performed to do this:
- Loaded the Fenix A320 at Gate E6 at FSDT ORD with live weather.
- Started AIGTC and ran it at 90% traffic.
- Went in to GSX setup and chose Dense for passenger timing.
- Commenced boarding and fueling.
- Pushback and taxi to 9C for departure.
- Flew to OMA.
First image shows an empty ORD, even though AIGTC is showing a somewhat full house.
Second image shows an empty ORD after takeoff.
Third image shows the single-digit FPS on short final. The calculated approach speed was much lower than what is shown, and perhaps the Fenix was out-of-sorts as a result of the sim, but not sure on that part.
Fourth image shows that the scenery is just gone, photogrammetry and vegetation remain, and FPS is even lower than on short final.
Fifth image is of the Console view, and slightly better FPS. I forgot to sort by occurrence, so this is what was going on at the time of landing. It seems that the airport scenery was trying to load. I explored the console list in cruise and several errors happened to be related to the Fenix. Keep in mind, this sim issue has also happened to me with the PMDG 738.
Sixth image shows what happened when I exited to main menu. The sim froze while loading and had to CTRL+ALT+DEL to get out. Again, forgot to sort by occurrence, so this is by time. But hey, at least the FPS came back.