do you ever feel like your wasting your time :)

Ok I am having the same problem out of the blue - aircraft trimmed correctly, TO/GA engages, FDs are on, flaps correct no warnings but autopilot does not engage after takeoff. As for the OP I have flown this aircraft many times previously and have not had any problems with the autopilot so something is missing here Furthermore if I load a saved flight with the autopilot already engaged in flight then disengage it wont re-engage. These are flights I have flown before without any autopilot problems. Turning off realistic autopilot engagement makes no difference. Suggestions appreciated. Bruceb

I also have an issue with this. The only issue I have ever had with the NGX is the disappearing aircraft problem which was sorted by the Hghmem=1 fix.Last night I installed UT2x. Seemed straight forwrad enough but now, no matter which NGX I fly, (800 or 900) the autopilot will not engage. The button will not illuminate, the horn will not sound when disengage tab is flipped, just nothing. The plane itself flys superbly and I am not suggesting for a second that there is a flaw.... simply that I have done something when installing UT2x. I just dont know where to look!Any help appreciated. The plane is in trim, hand flown to align onto the 1st waypoint, fmc seems happy but no A/P. I have also just installed the latest FSUIP.I have attached a screenshot showing both the annunciator panel and the centre consul trim wheel etc.Kind regards,Clive.

I also have an issue with this. The only issue I have ever had with the NGX is the disappearing aircraft problem which was sorted by the Hghmem=1 fix.Last night I installed UT2x. Seemed straight forwrad enough but now, no matter which NGX I fly, (800 or 900) the autopilot will not engage. The button will not illuminate, the horn will not sound when disengage tab is flipped, just nothing. The plane itself flys superbly and I am not suggesting for a second that there is a flaw.... simply that I have done something when installing UT2x. I just dont know where to look!Any help appreciated. The plane is in trim, hand flown to align onto the 1st waypoint, fmc seems happy but no A/P. I have also just installed the latest FSUIP.I have attached a screenshot showing both the annunciator panel and the centre consul trim wheel etc.Kind regards,Clive.

It looks like one of your IRS's isn't aligned. Maybe that has something to do with it?

What's going on with your 1st officer displays. Are both IRS aligned.Steve

Ahh thanks guys. You know how sometimes you just get too close to the whole thing and no matter how much it stares you in the face, you're never gonna get it.Very much appreciated.Clive.

I am following this topic because, since last Aug, in two or three takeoffs this AP nag has happened. I could engage it after sometime (1 to 2 mins) but it has left a doubt in my mind: what could be wrong in such situation as the checklist was followed to the letter and the NGX was trimmed and FDs on and aligned? These events were before SP1, with the 800.Yesterday, taking off at the default KGEG-Spokane-WA with the 600, the A/P again refused to engage. And this time I had to hand-fly her more than 5 mins before succeding in engaging the A/P.All I can remember is: (1) It was a radar vectored departure (SPOKANE ONE) and the plan in FMC did not point directly to the first waypoint MLP VOR, as it was a runway heading T/O clearance, so only VNAV could be armed. (2) Although I think this is not important, I forgot to turn off the APU before T/O.Regards,

Ok, Im looking at this thread because all of a sudden Im having this problem too, and I too cant figure out whats going on. Ive had the ngx since release day and not once EVER, never, never ever had this problem. I finally go from cold/dark setup to climb with FS2CREW working perfectly the whole way through, then this! My displays looked exactly like Clives's, I mean exactly. Departed Seattle enroute to Spokane and somewhere during climb I noticed I was above altitude, thats when I noticed CMD A off and the flight director cues missing, etc. All was fine during the initial takeoff and climb then something went haywire during the climb. I wasnt even touching my desk that the computer is on.

If your displays look like his then you didn't align both INS'

Uhm, yes, they were. They were aligned perfectly during the whole setup, with flight plan showing perfectly on both Pilot and F/O side. Taxi to runway...aligned...Enter runway....aligned....Takeoff...aligned.....Initial climb and gear up.....aligned with flight director cues on my side and theF/O's. Engaged autopilot after my intial turn and all was well with displays on both sides. Within about 10 minutes I noticed the problem after going and getting something to drink.