It is really a disappointment that a plane with so many good attributes fails to achieve real usefulness with its FMC/CDU.  My inexperience coupled with what I assume are real failures in the FMC/CDU leave little incentive to continue to use these features. I've spent too many hours learning and trying to use a faulty system. Hopefully CS will find a solution that will allow the FMC/CDU to create plans that work on all PC configurations and MS operating systems.

I have had one successful flight plan and several unsuccessful ones. The successful plan was at a cruising altitude below 10,000 ft and included a STAR. Legs included ascent, cruise levels and descent. VNAV and LNAV lights stayed on and descent altitudes and speeds were achieved.

Many plans produced legs without descending altitudes. Any plan at a cruising altitude over 10,000 ft, such as 15,000 would not fly higher than 10,000 ft, even though the original fsx plan and the legs in the FMC showed 15,000 ft levels. Perhaps the 10,000 ft level that intially appears in the altitude window limits what the altitude the FMC can control, but to this inexperienced person that seems wrong. If that window is manually set to 15,000 ft prior to flying the plan the plane will fly to the 15,000 ft level in the plan, but other lower altitudes in the plan are not followed. VNAV gets turned off and SPD turns on. But then not all the leg speeds are initiated and any lower plan altitudes are not followed even though a T/D point exists.

CS757 v4.2 with fsuipc v4.3 gave problems and now CS757 v4.3 with fsuipc v4.4 gives the problems described above. My system uses Vista 32 bit and has both sp1 and sp2 installed.