Hi John,Ok, I have just done exactly what you have written down here. The only difference is what I see up by the speed tape is the following:ILTN/259DME 23.0ILSAgain at this point I had not left the ground. Its got to be something I have missed. Or more likely inadvertantly changed. According to the map display the first DME I would cross to ILS 26 would be 77DME.Andy.

andyNot sure how else we could communicate, I am happy to stay online and we can compare set ups, now you know the system works, it has to be either a setting or something you have missed. I have skypeJohn Calleja

I have Skype, However can we do this tomorrow, I have to get up at dirty oclock. I can send you an offline message with Skype details, when I'm back online tomorrow.This sim is to addictive and I wonder why I'm tired all the time!!! :-)thanks for your help.Andy.

ok no problem, I am working tomorrow evening from 4pm to 9 pm but available before and after.John Calleja

Andy,Try this when you get a chance. To eliminate the NGX load a default 737 at EGSS rw 22. set both the nav radios to 109.15 and the course to 256. I still get by the speedtape ILJ/256 12.3 nm, so it seems the NGX gets its ILS from fsx? i chose the 737-800 Orbit one. Secondly do you have third party scenery that may have changed fsx runway data. or maybe need to run a database with that software to ensure frequencies are correct. If you have disarm them in the scenery library so you are just using default, to eliminate third party. Finally do you have FS Commander, if so centre the map onto EGGW and look both ends of the "feather" to see what the ils frequency is and the labels for the ILS. That will tell you what fsx calls everything and what the radios will tune to.or have you ever used a scenery editor, anf the ILS names have been copied to both ends?Hook up soonJohn Calleja

Edited January 11, 201214 yr by jc_150

Will have a look at the default FSX 737, At the moment apart from the NGX and Traffic X, the installation is clean as in there are no scenary addons airfield addons etc etc. I do not at the moment have FS commander. .ThanksAndy

Edited January 12, 201214 yr by Andy764

Hi Andy! I have to chime in here again. First off, have you setup the FMC and selected ILS26 as arrival runway? Keep both Navs UNTUNED at this point. Next verify in the Index/Approach page that the correct frequency and course shows up. If you are taking off from RWY 26 and want to track the LocBC outbound then select 109.15 on Nav1 and course select 079. BUT if you are NOT going to use it, then DON"T input the frequencies until you are on the approach (East) side of the airport and ready to fly the intercept heading. NOW activate the frequency in NAV 1 (and Nav2 if you want to autoland), verify that the top of the PFD is correctly showing ILJ for the ILS (or as I had suggested earlier, turn on NAV1 audio and verify this with Morris code ). Once on the intercept select (or verify) that the correct course setting has been entered for Nav1 (and Nav2 if you are going to autoland). Now activate APP and select CMD2 and they should both stay on and you should see the correct annunciation on the top of the PFD. The reason for this is that when you put in the 109.15 frequency it will pick up the nearest side localizer. If you wait until you are East of the airport before you activate the frequencies in the Nav's, then they will correctly pickup ILS26. It sounds as if you were pre-selecting those frequencies before you were East of the runway. I duplicatedyour scenario and had no issues with the radios correctly picking up ILJ when I activated them East of the runway.

Craig,I see what you are saying and basically what you have said is what I have done. Even as said above starting at EGSS and doing a basic flight but setting the FMC for arrival at EGGW whilst on the ground at EGSS. As soon as I set the frequencies in Nav 1 to be active what I see by the speed tape is ILTN/259.In In all cases except for the stansted experiment I have not been setting the NAv frequencies until I am about to intercept the G/S / localiser for 26. Stansted being East of Luton I should see What John saw above. Even on the ground.ThanksAndy

Andy,Try this when you get a chance. To eliminate the NGX load a default 737 at EGSS rw 22. set both the nav radios to 109.15 and the course to 256. I still get by the speedtape ILJ/256 12.3 nm, so it seems the NGX gets its ILS from fsx? i chose the 737-800 Orbit oneJohn Calleja

OK I tried this with a default FSX 737 and doing exactly as above I still get the ILTN/256 showing next to the speed tape. Not ILJ/256. Does this mean that actually the problem may be something in my install of FSX? Sorry this is probably getting boring now... but thankyou for the continued support.Andy

Edited January 12, 201214 yr by Andy764

Hi Andy,My understanding is yes you have an issue with fsx as I think that NGX uses the ils data from fsx to work as does the default planes. so I am assuming you have an issue with fsx. I havce done some research as i did not start work till 4pm today and I think I know where the Luton ils information is, and have some suggestions for you if we can hook up on skype, as it involves checking some files which I would rather not do on the public forum as I do not think PMDG would like this done here.regards. PS I only find computing interesting when there is a problem. lolJohnC

Edited January 12, 201214 yr by jc_150

Just tried this myself - everything worked perfectly:Just after G/S intercept:Just before autoland:Something's gotta be wrong with the actual ILS in your FSX scenery I think.

the easiest way to check FS scenery - look at the in-built map. Make sure that you have ILS beam on both sides. If yes, check their frequencies. If not, there is the problem.

Hi John,Tomorrow I am going to be getting myself a new processor Mobo, etc etc I need more speed, so I will probably do clean install of Windows after formatting the HD so this will give me a chance to do a completely clean install of FSX and get rid of any garbage that might have got in there.. My hope is that if it is FSX at fault then this will cure it. As to skype, I will send you a message with details however of all things, despite being surrounded by technology I cannot find my skype headset and mic. It appears to have been "tidied".......! - My better half appears to have been cleaningand has gone out.... Its a Man Room for a reason... :-) I'll let you know the result..Many thanksAndy

Hi AndyNo Problem, make sure that you have enough information to be able to re install PMDG NGX before you fornat your hard drive, like original installers etc, as some people have not been able to install after a re-format without PMDG support. As you are starting from fresh, I would recommend the following procedure from what you have said already. Get the computer up and runnong with windows and service packs etc, then install fsx, and service packs or acceleration pack. Then do a couple of tests to make sure you can do what you want with just default planes. Then add NGX last when everything is working ok then you have a "trail" if anything goes wrong for fault finding purposes.regardsJohn Calleja

Andy,Follow our guide here for the FSX install...http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx