Hi all:

Let me begin by thanking the Leonardo team for their response on the brake issue. The latest version fixed the problem in my FSX. Works fine now.

On another subject, I am seeing some difficulty with the aircraft capturing the localizer and tracking when on AP. It seems that she starts the turn but blows right through the capture heading, then she loses her way and heads off into nowhereland. So I kick off the AP and hand fly the approach. I have been using no more than a 30 degree angle on the intercept heading. I notice the yoke is thrashing back and forth without a lot of response from the aircraft. I did read in the manual that the real aircraft is sluggish at low speed, so this seems to be consistent. Usually I try to intercept the localizer at 160-180 kts with appropriate flaps so it is not real slow and I try to never exceed around 30 degrees. The AP seems to be doing all the right things but the controls don't seem to be able to keep up.

Just me or anyone else?

Edited February 24, 20188 yr by Wink207

Hi,

I experienced too that the aircraft did not intercept the localizer in the right way.

It overshoots the localizer and then try to track back and overshoots again.

Just now after five ILS landings it did it right, so i guess 1 out of 5 it does o.k. (should be better though).

Kind regards,

Ben

That is usually a sign of scenery having different ILS information than the NavData in the aircraft.  Are you sure it captured the Localizer?

Best wishes.

 

32 minutes ago, DaveCT2003 said:

That is usually a sign of scenery having different ILS information than the NavData in the aircraft.  Are you sure it captured the Localizer?

Best wishes.

 

Well, this latest was BOS runway 33. The localizer freq was correct in the MADDOG FMS and was the same as in the sim. I checked, as I always do as sometimes the FSX freq is different from the latest published freqs. And no, it did not capture the localizer, although she tried. The display looked right and the aircraft started the turn to capture but was unable. So she blew through the intercept heading and then was lost.

13 minutes ago, Wink207 said:

Well, this latest was BOS runway 33. The localizer freq was correct in the MADDOG FMS and was the same as in the sim. I checked, as I always do as sometimes the FSX freq is different from the latest published freqs. And no, it did not capture the localizer, although she tried. The display looked right and the aircraft started the turn to capture but was unable. So she blew through the intercept heading and then was lost.

Okay, I've contacted Umberto at FSDT and he's going to send me the AFCAD or scenery. I'll work this out and let you know what i find.  I know the Boston airport pretty well.  In fact, you meant 33L, right?  That's what I'll check anyway, as I believe 33R is a little short for our aircrash (lol).

I'll let you know as soon as I get the data from FSDT.

 

The same thing happened to me at flightbeams kden runway 17L

17 minutes ago, DaveCT2003 said:

Okay, I've contacted Umberto at FSDT and he's going to send me the AFCAD or scenery. I'll work this out and let you know what i find.  I know the Boston airport pretty well.  In fact, you meant 33L, right?  That's what I'll check anyway, as I believe 33R is a little short for our aircrash (lol).

I'll let you know as soon as I get the data from FSDT.

 

Yuk! Yes, 33L. 33R is a wee bit short ....:)

Thanks

Okay, just fly (flying actually) the ILS 33L using real world data, which matches the Maddog (verified).  Perfect. 

One thing, a localizer isn't much good past 18 miles, and thought the Maddog will capture it out that far it's a little squarely as it would be because the signal can be all over the place.  But if you intercept at 18nm or less it's perfect.

I have a video if you'd like to see it.

If you're having problems inside of 18nm then it's the scenery. I'll write back when I have it.

Best wishes.

 

This thread is what I was searching for!

Ive had the greatest difficulties landing the MD80. A lot of over runs on the LOC, or even flying away from it. 

Ill try the <18NM trick. See is that helps. 

I am opening a ticket on this with a screen grab of the problem

I don't know if this is h replace to post it,  but I have no problem capturing the localizer.  However, I have been unable to successfully complete an autoland so far.   Everything appears normal, until the autopilot goes into the ALIGN mode.  It never properly aligns, and goes off the side of the runway.  I am within the wind limits of the autoland capability too.

 

11 minutes ago, Wink207 said:

I am opening a ticket on this with a screen grab of the problem

Below are links to three sequential/short videos my ILS approach yesterday. AIRAC 1802, ILS Info Runway 33L 110.7/330 degrees. I had another Beta Tester do the same and he experienced exactly the same thing.  We are running the same software you are, the only difference is that neither of us have the new FSDT KBOS scenery.

It's certainly your prerogative to put in a ticket, but none of us can replicate your problem in  P3DV4.2, and we'll note that in our response to your ticket. 

I'm still waiting to here from Umberto to check the scenery.

Note: In Video 1 I had an Offset RNAV Selected so that the path to 33L was no obsurded during initial LOC Capture. I changed it to the ILS approach later on. 

Video 1:  https://www.dropbox.com/s/8nd3fan9vbojv07/Video 1.mov?dl=0

Video 2:  https://www.dropbox.com/s/49py0vqwhueinmc/Video 2.mov?dl=0

Video 3:  https://www.dropbox.com/s/g7ezjtoo5s7dn6i/Video 3.mov?dl=0

 

Best wishes.

 

 

2 minutes ago, KORDATC said:

I don't know if this is h replace to post it,  but I have no problem capturing the localizer.  However, I have been unable to successfully complete an autoland so far.   Everything appears normal, until the autopilot goes into the ALIGN mode.  It never properly aligns, and goes off the side of the runway.  I am within the wind limits of the autoland capability too.

Are you setting both Nav Radios and Courses, selecting VOR, and then selecting Autoland (without selecting ILS first)?  Have you checked to ensure the scenery ILS frequency matches the AIRAC?

If so, which airport scenery and runway?

By ALIGN Mode, do you mean Capture?

Looking forward to hearing back from you.

 

44 minutes ago, DaveCT2003 said:

 

Below are links to three sequential/short videos my ILS approach yesterday. AIRAC 1802, ILS Info Runway 33L 110.7/330 degrees. I had another Beta Tester do the same and he experienced exactly the same thing.  We are running the same software you are, the only difference is that neither of us have the new FSDT KBOS scenery.

It's certainly your prerogative to put in a ticket, but none of us can replicate your problem in  P3DV4.2, and we'll note that in our response to your ticket. 

I'm still waiting to here from Umberto to check the scenery.

Note: In Video 1 I had an Offset RNAV Selected so that the path to 33L was no obsurded during initial LOC Capture. I changed it to the ILS approach later on. 

Video 1:  https://www.dropbox.com/s/8nd3fan9vbojv07/Video 1.mov?dl=0

Video 2:  https://www.dropbox.com/s/49py0vqwhueinmc/Video 2.mov?dl=0

Video 3:  https://www.dropbox.com/s/g7ezjtoo5s7dn6i/Video 3.mov?dl=0

 

Best wishes.

 

 

As you know, I am running FSX

43 minutes ago, DaveCT2003 said:

Are you setting both Nav Radios and Courses, selecting VOR, and then selecting Autoland (without selecting ILS first)?  Have you checked to ensure the scenery ILS frequency matches the AIRAC?

If so, which airport scenery and runway?

By ALIGN Mode, do you mean Capture?

Looking forward to hearing back from you.

 

 

47 minutes ago, DaveCT2003 said:

 

Below are links to three sequential/short videos my ILS approach yesterday. AIRAC 1802, ILS Info Runway 33L 110.7/330 degrees. I had another Beta Tester do the same and he experienced exactly the same thing.  We are running the same software you are, the only difference is that neither of us have the new FSDT KBOS scenery.

It's certainly your prerogative to put in a ticket, but none of us can replicate your problem in  P3DV4.2, and we'll note that in our response to your ticket. 

I'm still waiting to here from Umberto to check the scenery.

Note: In Video 1 I had an Offset RNAV Selected so that the path to 33L was no obsurded during initial LOC Capture. I changed it to the ILS approach later on. 

Video 1:  https://www.dropbox.com/s/8nd3fan9vbojv07/Video 1.mov?dl=0

Video 2:  https://www.dropbox.com/s/49py0vqwhueinmc/Video 2.mov?dl=0

Video 3:  https://www.dropbox.com/s/g7ezjtoo5s7dn6i/Video 3.mov?dl=0

 

Best wishes.

 

 

Please take a look at the ticket. There is a screen grab included. Perhaps you can find something wrong with my lineup but it is obvious that the aircraft did not capture the localizer.