I did notice I could not get mine to work at Nice Côte d'Azur Rwy 04L tonight. Second auto-pilot would not come on. Both FD's on, Both Courses Set, Both ILS Frequencies Set, ILS 04L set in FMC, and had the HGS Set. I wonder if that last hotfix messed up the Autoland for some people. Anyway dong a 6.5 hour flight from Nice down to Dubai will let ya know if I can get it to work down there.

The problem I have is that every time I get the "SINGLE CH" message and I want to turn on CMD B it will turn on for a second then CMD A will disengage.

Just got into Dubai United Emirates from Nice France. 5 hr 45 min flight. Was able to make a full AutoLand on ILS 12R. So the Autoland is definately working with Hot Fix 3. However I am using a clean NGX install with the new installer that has all 3 Hotfixes included already.

The problem I have is that every time I get the "SINGLE CH" message and I want to turn on CMD B it will turn on for a second then CMD A will disengage.

That is actually a feature if you have the realistic A/P behaviour activated (Default). It took me some training to first enable Approach and then activate the second A/P system at the right time which is when the glideslope becomes alive and its diamond shape turns pink.

The problem I have is that every time I get the "SINGLE CH" message and I want to turn on CMD B it will turn on for a second then CMD A will disengage.

You cannot engage both autopilots until after you have pressed the APP button ! Fred.

A

You cannot engage both autopilots until after you have pressed the APP button ! Fred.

Oh,of course! Who doesn't know that? I have absolutely everything configured (NAV1,NAV2,CRS,MINs,FLAPS,GEAR) and I am fully established on an ILS and I still cannot engage CMD B.

That is actually a feature if you have the realistic A/P behaviour activated (Default). It took me some training to first enable Approach and then activate the second A/P system at the right time which is when the glideslope becomes alive and its diamond shape turns pink.

I'll try to turn it on right as the diamond appears tomorrow...I tried to turn it on when I was fully established and it did not work.

I would think it's the hotfix so ! I have used no hotfixes yet and am having no problems at all. Fred.

I'm with you Fred, if it ain't broke don't fix it! I'm sure PMDG is thinking about the best way to resolve problems is to get more users on board w/ hotfixes so they can continue to troubleshoot the issues. I'm lucky I guess as it seems to be working fine so far. Noel

I think you may find that if you try to fly an autoland from a saved flight that was saved before the hotfix it will give the NO AUTOLAND response. If you refly the flight from scratch and do the same approach with the hotfixes applied it will work okay. One thing worth trying to get around this maybe (if you want to use your old saved flights) is to retune the NAV radios before approach but I havent tried it yet.

I originated this post and now thanks to all the comments above I have found the solution to what I was doing wrong.On my last test flight I did not use an old saved panel state (i.e. from before the hotfix installation) I started from the default cold and dark.Secondly ( and probably the real reason) I waited until the G/S was fully captured before selected CMD B. Previously I selected this after capturing the localiser.Now I still see 'single channel' indicated until 1500', but now after this it correctly engages 'LAND3' and arms 'flare' and 'rollout' and lands successfully. As mentioned earlier the hotfix has changed the way autoland behaves i.e. the single channel is now indicated even when both CMDs are on until 1500'.Thanks to all!

Secondly ( and probably the real reason) I waited until the G/S was fully captured before selected CMD B. Previously I selected this after capturing the localiser.

Whats the indication that the G/S is fully captured? I tend to press CMD B right after the approach button turns off.