Hello,For the past year I have been mostly flying PMDG 744. I decided to join a virtual airline, in which I started usingdefault panels with the downloaded aircraft.Since joining, I've downloaded all kinds of other panels. My problem is when doing an ILS approach the localizer does not show up on the PFD but I do get the glideslope. I have a feeling when I was messing around with freeware panels I might have overwritten a file. I can't for the life of me figure out which down load it was. I've noticed it doesn't matter which default panel it is.I'm using FS9.Thanks for any advice

I thought I would bump this once, to see if anyone had any ideas. I appreciate any thoughts you might have about this.Thanks!

Just a couple of quickies:First check your FS9 registry setting with this tool:http://www.flight1.com/view.asp?page=library getting FSX/FS9 Registry Repair Tool (36KB). If on VISTA or WIN 7 be sure you are logged in as an admin and run it as an admin. Be sure your FS9 entry is correct. This is necessary also for the following step.Go to http://www.schiratti.com/dowson.html and download and install FSUIPC 3.98 (FOR fs9) in case that was overwritten by another add-on.Both of these are needed to be checked and current to prevent localizer errors.You are getting the GS so you do appear to be correctly tuned. The 744 auto tunes the NAV. Check the ident in the PFD and insure it has the correct localizer tuned in. If you are going into airports where the same localizer frequency is used at both ends of a runway unless you are near center line you will pick up the wrong one in FS default scenery. This is because in FS default scenery all localizers have their back course turned on. For safety rather than AFCAD 221 use ade9x to go into any questionable scenery and turn off the back course in these cases.You can use AFCAD to just read the ILS/LOC frequencies in the scenery if you wish. I don't have the 744 and I do not know where its frequency database comes from. I do use the 737 and have to manually tune the nav receivers.I think you can also set your ND display to show GS and LOC. Does the annunciator section of the PFD show any GS mode and the LOC IDENT on the PFD display?Finally, be sure you are not confusing the vertical path indicator used during descent appearing in the ND with a GS indication. The ND display mode is controlled on the EFIS control panel. I generally just use the LOC/GS indicators on the PFD.That's all I can think of at the moment. I assume you did not modify the PMDG 747 panel with any other. If so, a removal of the 744 and reinstall is necessary. Make sure you have any registration keys from your e-mail.Last describe your version of Windows in case there is a user access issue.See if any of this helps. You can also browse the PMDG 744 support forum here on AVSIM.

Ronzie,Thanks for the reply. I should have been a little more clear. I don't have any issues with PMDG's 744, everything is working great. Its when using the default panels I have problems.I'm not familiar with the registry tool and will give that a try. What does it actually do? I'm using XP. I already have FSUIPC but will double check that as well.Thanks for the help

The default panels do not use FSUIPC. I think the only localizer ident you will get on them is Morse Code but I could be incorrect in how some default gauges function. If you have IFR plates for the airport the Morse Code should be on there.The other comments regarding back course still apply. I'm not sure if the default aircraft is realistic in that the OBI heading control does not have to be set for a localizer so turn the OBI course selector to the inbound course if flying a front course. You can bring up the default GPS to see when you are lined up with the localizer. The default GPS though is only good for default scenery if you are using an add-on that differs. Both the FS GPS and the FS map info have fixed databases that will not reflect add-on scenery. The aircraft LOC/ILS OBI will reflect scenery changed/added navaids using those frequencies.Several default models share gauges. Perhaps only one type of OBI gauge has been replaced and is causing that problem.I'd also look in your modules folder for strange properties on ones that seem related to gps, gps_export, panels, facilities, symmap, util. These should be MS produced with either 9.0 or 9.1 versions. Check especially the gps_export version as a few models replaced this with an FS8 version but this usually caused a crash.If you ever had FSX installed and then removed it your FS9 registry entry might be incorrect. Some models use that to point to navaid data and magnetic deviation tables. If your PMDG is OK that is probably OK. There have been claims that one add-on scenery overwrote the magnetic deviation tables creating a problem.Otherwise, post in this forum where the gauge and panel experts reside:http://forums1.avsim.net/index.php?showforum=122

Ronzie,Thanks so much for the thorough reply. It gives me plenty of options to explore and points me in the right directions.