Hi Fred! What I explained was what I found when testing the simulation. Naturally you have to be on an intercept and at an altitude below the GS! I didn't mention those requirements because I assumed we all were doing that! But what I am relating is what the simulation is requiring. I agree with you that in the RW that is probably as it should be. With the other PMDG simulation (B744) that I have that in fact is the case and also with the Level D, and the Super 80, but the NGX will just not sustain the second CMD active until I select flaps 30 or flaps 40. From what you say this is obviously something that departs from reality.

I select both autopilots when only at flaps 5 or 15 all the time with no problems.It works just like the real aircraft. Are you using the latest hotfix ? Fred.

Hi Fred! Aha! That must be something they fixed then in the updates. I have only the original that came out on Aug 5th. I am unable to activate any of the updates and have not had any answers on my trouble ticket regarding this issue. So I had to restore my computer back to before I had attempted the update. That allowed me to use the original without having to attempt to re-activate. I am hoping they will have resolved the activation issues before they complete SP1. I never had a CTD issue and everything seems to work correctly with the exception of the 2nd CMD issue we are discussing and some strange anomally that occurs when I attempt a miss-approach. Maybe you can give me some info on that. When I initially activate TOGA the power increases and the plane begins to pitch up but then it immediately cuts the power back and begins to descend if I don't immediately intervene by pressing TOGA a second time and manually pitching it into a climb. I have been experiencing this with non-precision approaches and pressing TOGA before I disconnect AP (which immediately disconnects anyway). I cannot remember whether the same problem occurs during an autoland approach. This could also be something that has been addressed and fixed on upgrades.

Hi Fred! Aha! That must be something they fixed then in the updates. I have only the original that came out on Aug 5th. I am unable to activate any of the updates and have not had any answers on my trouble ticket regarding this issue. So I had to restore my computer back to before I had attempted the update. That allowed me to use the original without having to attempt to re-activate. I am hoping they will have resolved the activation issues before they complete SP1. I never had a CTD issue and everything seems to work correctly with the exception of the 2nd CMD issue we are discussing and some strange anomally that occurs when I attempt a miss-approach. Maybe you can give me some info on that. When I initially activate TOGA the power increases and the plane begins to pitch up but then it immediately cuts the power back and begins to descend if I don't immediately intervene by pressing TOGA a second time and manually pitching it into a climb. I have been experiencing this with non-precision approaches and pressing TOGA before I disconnect AP (which immediately disconnects anyway). I cannot remember whether the same problem occurs during an autoland approach. This could also be something that has been addressed and fixed on upgrades.

That's it so !! A lot of those little things were fixed in hotfix 3. Single channel now announces instead of CMD before 1500 ft etc......... I am loking forward to Sp1 too. Enjoy flying ! Fred.

Thanks, Fred

I think the logic is that if you have are not in APP mode or have not captured the G/S, then you can not engage autoland, so pressing the other CMD button simply means you want to use the other A/P. After you have captured the VOR/LOC you can engage APP. After you have captured the G/S, you can engage autoland (by pressing the inactive CMD button).

I think the logic is that if you have are not in APP mode or have not captured the G/S, then you can not engage autoland, so pressing the other CMD button simply means you want to use the other A/P. After you have captured the VOR/LOC you can engage APP. After you have captured the G/S, you can engage autoland (by pressing the inactive CMD button).

The glideslope does not have to be captured first to engage the second autopilot !If your configuration is correct you can slect both autopilts after Pressing APP. The APP mode is different to all other modes because it is the only mode that can control Thrust, Pitch and Roll at the same time.