After much testing, weighing the pros and cons, thoughts of interfacing operability and much wringing of hands I think I have come to a conclusion on the software combination I will use for the 737 Glass cockpit and FMS. There were 3 or 4 contenders, each with their own strong points, but in the end I decided that the best ‘fit’ for my purposes was to go for Eric Marciano’s Easy FMS, and Paul Scarratt’s 737 Classic panel for the XML gauges and EFIS control logic. The AFDS I have ended up with a modified version of the default 737-400, and some of my own logic through LUA scripts.
The main driver which lead me to this solution was when I actually defined what I wanted to be able to do in the sim. My main purpose of the 737 is to allow me to fly air transport flights, focusing on the ‘flying’ part, rather than systems. This approach also allows me to fly in my retro FS world, without the worry of AIRAC data or navaids being up to date.
There are compromises of course; my chosen solution doesn’t allow me to select SID’s and STAR’s through the FMS, nor does it allow for VNAV.
One important part of the simulation is the use of X-Pause. When I first heard of it I couldn’t see the point of it…. One of our favorite customers requested it in his sim, and explained his reasons but i just didn’t understand… now I do. I have enjoyed flying the sim (albeit in it’s current basic state) through takeoff and departure, then leaving it to complete the climb and cruise on it’s own. Then once it arrives at a pre-defined point it pauses and waits for me to do the arrival and landing. Basically it lets me do even long-haul flights, but miss all the boring bits in the cruise. It also lets me do my flights in bite-sized pieces that fit in with my hectic lifestyle!
So… decision is made, plans are afoot, now I need a drink 😉