Indeed, there is quite a bit you can't see from the videos and screenshots...and also, its not just one or two folks, but 1000s that will trying all differing things, making for 100,000s of possible combinations that might be entered into the FMC. So while we are definitely not striving for perfection, as evidenced by our "whats not in V1.0" list, we do have to ensure that the basics desired are in. To elaborate further, the "desired basics" are those FMS functions that We ourselves as simmers have always said with other products, "I wish the FMS did X....or Y, etc. It turns out the X and Y is a pretty long list of stuff and you take for granted just how many things, as a coder, you have to account for.
For example, I'm going to throw Jan under the bus here a bit to illustrate. Jan tells me once, "cruise phase is always in mach". Ok...cool...I made that happen. THEN...a good while later, Jan flies a flight with a cruise altitude under 10,000...where the speed restriction altitude is 250 kias. Jan comes back...."hey Tom...these cruise value should be in KIAS"........"OH...so you mean cruise phase is always in mach, except for condition A.........um....is there a condition B I should know about too? A C perhaps?" Sorry Jan! So things from a coding perspective are not as simple as they may seem on the surface. While maybe 95 out of 100 flights will probably never use cruise altitude below 10,000', some will..and we have to anticipate that before hand and handle it. It turns out there is a whole lot of these situations. The good news is that we believe our V1.0 FMS feature set is complete and we are "testing/calibrating" the performance while we simultaneously clean up textures, loose ends and docs.
-tkyler