Hi All,

 

Over the last few months I have been getting some great hours on FSX mainly in PMDG737 NGX and now Airbus X Extended. I have completed many successful landings at Heathrow but something has changed. Tonight for instance I flew from EDDF to EGGL with a planned arrival at runway 09R. When I reach my TOD I set my landing flap config then setup my ILS frequencies and course. The problem is that I cannot select the LOC button to allow me to capture the localizer. The weird thing is if I change the course to 271 for runways 27L & 27R I can select the LOC button even though I am approaching from the opposite direction. I have no idea what has happened here but it us driving me a bit crazy. I noticed the exact same thing happen last night on an approach into runway 24L at CYYZ. Again I couldn't select the LOC button.

 

I also tried a flight in the A320 into runway 24L at CYYZ. I was able to select the LOC button but instead of capturing the localizer the plane just took off in completely the wrong direction. Other runways seem to be OK.

 

I have landed many times before at EGLL & CYYZ without problems but this is really stumping me.

 

If anyone has the remote idea what is happening i'd love to hear from you

 

Richard

I have experienced the exact same thing. Making 360s instead of following the localizer. I have no idea what's going on, but the bus has been grounded with me until they figure it out. Luckily, the NGX still works like a charm. ^_^

Did you get the ILS frequency and course from the FMS? I have found in the past that the actual real-life frequencies are different to the ones microsoft programmed FSX with, many years ago. The easiest way to get around this is to use the FSX map and see if the freq/course is different to the one displayed on the approach ref page of the FMC.

 

If they are the same I don't know what else to suggest.

I have had it happen at OMDB (Fly Tampa scenery) rwy 30R, ILS identified, diamonds showing, final turn on the STAR then.... turning the wrong way instead of capturing the LOC.

 

I guess we'll just have to wait for the devs to come up with a fix.

I guess we'll just have to wait for the devs to come up with a fix.

 

 

I think they already did come up with a fix and it was already there in version 1. ^_^ The Introduction pdf, page 55, tells about the option called SET FSX LOC CRS.

 

• SET FSX LOC CRS: When it comes to navigation data, FSX has an inherent weakness in that data related to ILS/LOC stations is hard coded into the simulator and is not updated to keep it current with the normal magnetic shift. The end result is that the localize final approach course in the FSX world will sometimes vary from the real world. Since many users are also using real-world navigation charts, this can create some confusion and can also create problems if the LOC course is not correctly set to match the FSX hard-coded information. (The airplane cannot fly the localizer properly if the CRS knob is set incorrectly.) To compensate for this, we recommend setting this option to ON, and we will read the appropriate FSX localizer course and adjust the setting for you, thus saving you time and frustration.

 

So check that setting! It's part of the Equipment options. Don't really know though if this solves the problem the OP is having...

The NAV/GPS switch might be in GPS. The CRS knob sets VOR radials and does not work in ILS mode.

 

Dave

option called SET FSX LOC CRS.

 

Ah, well ok. I guess I didn't read the manual Thank you very much, sir. Will check. *EDIT* You're talking Airbus now right?? Because I have this set in the NGX. And I have a feeling you're talking NGX now, come to think about it.

 

The NAV/GPS switch might be in GPS. The LOC button won't light unless a ILS freq. is selected. The CRS knob sets VOR radials and does not work in ILS mode.

 

Dave

 

Thanks Dave, but this is not the problem. For me at least.

The HSI or Course Indicator on all aircraft should work the same. I have never tried the Airbus. Since it's French, it might be different. :rolleyes:

 

Dave

he HSI or Course Indicator on all aircraft should work the same. I have never tried the Airbus. Since it's French, it might be different.

 

Dave

 

In the bus, the ILS is automatically tuned and set when you select an approach in the FMGS.

Then it sounds like what J van E said about old/new approoach data. I am too old school. I do all my nav in a Spartan, without GPS.

 

Dave

Have you got any EGLL scenery installed? I had this with the UK2000 EGGP, once i installed i couldn't capture the Rwy27 ILS. Turned out to be two data sets, the base FSX and UK2000 conflicting. I'd try looking at that before you 'blame the plane'.

I`ve had this issue a few times in the Airbus aswell, I`ve posted the problem in aerosofts forum. I`m using the correct ILS frequency read from FSX by EFB.

It seems to be a bug in Aerosofts Airbus Extended where it gets fixated on the last waypoint of the STAR.

This has happened to me on stright in ILS approaches and when making a fairly tight turn to capture the localiser.

Dont have the issue with other aircraft.

 

Regards Doogie

Ah, well ok. I guess I didn't read the manual Thank you very much, sir. Will check. *EDIT* You're talking Airbus now right?? Because I have this set in the NGX. And I have a feeling you're talking NGX now, come to think about it.

 

OOPS! MY BAD! SORRY! I read NGX and FMC and I thought it was all about the 737 NGX... Only in the OP there was a brief mention of the Airbus... (which doesn't have an FMC but a MCDU). Sorry for the confusion... ^_^

Have you got any EGLL scenery installed? I had this with the UK2000 EGGP, once i installed i couldn't capture the Rwy27 ILS. Turned out to be two data sets, the base FSX and UK2000 conflicting. I'd try looking at that before you 'blame the plane'.

 

Funny you should say that, I have UK2000 Heathrow Extreme and I did wonder that. Last thing I did before going to bed was to uninstall the UK2000 software so I will try later. I am sure it isn't the aircraft though as I am getting problems with 2 different planes. Also it doesn't explain the issue I had with CYYZ.

 

I have been using the frequencies loaded from the FMS which has worked without any issues in the past.

 

Got some food for thought so I will try a couple of things and report back

 

Richard

OK so I just did a very quick test on the windows bootcamp partition on my iMac that still has FSX on it. Took off from EGLL 09L in the PMDG737 NGX and did a circuit landing on 09R. Everything worked as it should I switched the LOC button on and the localizer was captured and an auto landing was performed.

 

I will try my main rig later to see if uninstalling UK2000 has made any difference. At least I know for sure it isn't anything to do with the 737 or the Airbus