I took the X-Plane 12 platform’s Flight Factor (FF) 777-2 v. 2 for an extended spin from San Francisco International to Frankfurt Airport. I’ve been using the FF 777-2 since they first released it in early 2024 while in alpha and beta development phases. I’ve become familiar with the software (minus crew interaction functions) and so will now write some of my thoughts on this particular KSFO to EDDF flight. I had hoped for a solid, error free flight, but that didn’t happen. 

On preparation for the flight, the EFB was a chore to use for simply closing the hatches and arming the doors. There’s unneeded user interface flourishes and, I think, hard coded lag time between user clicks and removing ground services and closing doors. Sometimes it’s not clear why doors or cargo hatches won’t close. I assume because I have crew interactions turned off, things a bit off kilter. Weight and balance was a chore with a lot of clicks between the fuel, passenger, and cargo screens. There can definitely be improvements to that loading workflow.

The FF 777-2 FMS navigation database is, after all this time, completely at odds with X-Plane 12’s AIRAC navigation database. FF’s 777-2 does not use X-Plane 12’s nav database. It uses AIRAC 2105 while X-Plane 12 has AIRAC 2510. FF’s built-in database is four years old! SIDs, STARs, airways, and waypoints have changed quite a bit since 2021. The only way to make them the same is to buy the navigation database from Navigraph and load their latest data into X-Plane 12 and the 777-2. This means, without forking over a 30-Euro subscription fee, if you want the load a flight plan .FMS file that might work the first time, the open source Little NavMap flight planning software needs to export STARs and even airways as waypoints. But since 2021, even waypoints have changed a decent amount in European airspace. So I had to scrap a bunch of waypoints and load in Flight Factor’s 2021 STARs and ILS procedures. I could have used custom waypoints using coordinates.

The FF 777-2 performed well enough for takeoff, climb, and cruise. It did perform step-climbs automatically while I was asleep (not an aircraft feature, but meant for unattended long-haul flights). The approach is where things fell apart. FF’s FMS had a bizarrely constructed VNAV PATH that would have caused a lot of passenger discomfort with high descent rates… especially when turning to final. There’s no way the aircraft would have a stable approach. So I used the MCP to fly the aircraft for a bit. I captured the ILS localizer and glide slope, and when I disconnected the autopilot, the aural alarm & light would not extinguish. The aircraft flew steady and true on approach, and I had a nice landing. But upon leaving the runway, the speed brakes were stuck up and could not be disarmed. The AP aural alarm was still going. Replay did not work and eventually X-Plane 12 crashed. I assume I was supposed to set up Flight Factor’s own replay since they simulate nearly everything using plugins instead of using XP12’s very capable programming. So that means they’d have to build their own replay software.

I think that, as Toliss can use most of X-Plane 12’s built-in functionality (and its Nav database!) to simulate complicated Airbus Aircraft, so too can Flight Factor for Boeing aircraft. But I have a feeling they’ve sunk too many resources into simulating outside X-Plane 12. That's a shame.

For airliners, I think I’ll stick with the Zibo 737-8 and Toliss Airbus for a while, since flying the FF 777 does not bring me much joy. The Toliss and Zibo aircraft are solid and extremely predictable, plus they mostly use X-Plane 12’s functionality for simulation and navigation. Replay then works great. Bottom line, with aircraft that use X-Plane 12’s core simulation software, there are no surprises.

#Aviation #XPlane12 #FlightSim