EGLL/YSSY Trip Report 19.5 Hours
Plugged the trip in VFR direct from the main page with the plan to use 3D, set the autopilot after TO and have some performance monitors running.
Departing London, in 3D with FPS @ 42, it dropped immediately to 13. Photogrammetry can be difficult in certain areas and London is one of them. This is what the Windows Event Viewer was flagging during the brief drop and may speak to the audio popping some have reported
.
Getting away from London the FPS rose to 48. Leveling at FL 350, I switched to 2D mode (FPS 150), turned off WMR portal and resized the MSFS window to add performance / hardware monitors on the screen.
The flight was uneventful until checking status at 12 hours. FPS had dropped from 140-150ish to this
And from the Event Viewer
After seeing hardware and resource utilization looking normal, the COM warning made me suspect of the Photogrammetry issues with FPS and decided to turn it off. The jet was over water at the time.
Two hours later and coming up on land, things had improved a bit
FPS continued to improve driving across AU with the approach to Sidney looking like this
My impressions are;
The physical memory and paging are solid
Photogrammetry data handling has an impact on FPS / sim cache / manipulators
I’m tempted to bump the Manual cache up
The sim has a big wad to chew
I won’t do this again. I’ll teleport.