Okay, I've Googled and searched and beat the bushes for some hint on how to make this work. Some runways have a single ILS LOC frequency (published and in FSX). Take 13R/31L at KDAL, for example. Same frequency! 111.10.In the "real world" (whatever that is), the Tower switches off the INACTIVE end so the airplane only "sees" one end of the approach. No problem. But FSX doesn't do that, as near as I can tell. So how do you successfully shoot a CATIII when the instrument refuses to give you the proper line up for the ACTIVE? Am I really going to have to go in and AFCAD this with "false" discrete frequencies?Long time simmer and low time Private Pilot,edhlmft

If the problem is you getting ILS for the opposite runway instead the one you want. I found this problem occurs when you add stuff to FSX that updates the airportsTrafficX , MyTrafficX etc.I fixed this by moving the scenery files for MyTrafficX far down the list of scenery in FSX Scenery Priority Setup Window. I think the priority of the new addon just needs to be higher number than Addon Scenery entry.

Thanks iko. Maybe I wasn't altogether clear about the problem. Many airports (real and sim) have one ILS frequency for both ends of the runway. At real airports, the Tower turns off the INACTIVE end. In fact, I think there is a 'lockout' that keeps both transmitters from transmitting at the same time. However, in FSX both ends "transmit" making it difficult to shoot the ILS. I've tried several approaches at KDAL and keep getting the wrong end (NAV1/NAV2) even though I'm set up by APP Control for the proper runway. I'm hoping there's a patch to FSX or that someone has discovered a trick.Cheers!

I've never had a problem with this. Are you setting up the HSI (assuming it's an airplane so equipped) correctly with the inbound course?

Thanks iko. Maybe I wasn't altogether clear about the problem. Many airports (real and sim) have one ILS frequency for both ends of the runway. At real airports, the Tower turns off the INACTIVE end. In fact, I think there is a 'lockout' that keeps both transmitters from transmitting at the same time. However, in FSX both ends "transmit" making it difficult to shoot the ILS. I've tried several approaches at KDAL and keep getting the wrong end (NAV1/NAV2) even though I'm set up by APP Control for the proper runway. I'm hoping there's a patch to FSX or that someone has discovered a trick.Cheers!

Maybe you need to google these terms togetherAddon scenery , Trafficx , FSX, ILSI had this issue after installing Trafficx, and fixed it by moving trafficx scenery above addon scernery, years later i decided to dump Trafficx and use the new MyTrafficx 5.4 and same issue again, fixed it this time by moving MyTrafficx scenery near the very bottom of FSX scenery so its priority is one of the highhest.Google the correct words on this, youll find many have had this issue, Now if you have not installed any addon that adds to your scenery dont know whats the cause.For sure google , Runway ILS opposite problem scenery, and you find what i am saying.Dont messup yuor AFCAD ,In FSX tower will not turn off ILS for opposite runway, it just works, when you dont have this issue.1. Try this , look in your scenery list for any none default scenery you might have installed lately2. Move the scenery above Addon Scenery, start flight at airport like EGLC which has same ils for opposite runway , see if you get both ILS signals correct3. If any ILS failed, move the new scenery file below addon scenery, and test again at EGLC or similar airport. At EGLC i could only pickup [iLSR] till i fixed the problem, by moving new stuff about in scenery priority list

Thanks for the good information iko. I have discovered a temp fix. If I 'uncheck' TrafficX scenery, the problem resolves perfectly. Now on to the TrafficX forum to find out if there's a fix for that! I didn't notice the KDAL airport in TrafficX's bgl list but maybe I wasn't looking in the right place? I have had to make modifications to TrafficX scenery (using ADE 01.50.01) before and maybe that's what I'll need to do this time as well.Thanks all!edhlmft

I have found a couple of problems with ILS at Traffic X airports. You'll need an airport editor (I use AFX) to fix them.1) Where the ILS frequencies are listed in the Map application, but not in the airport page on the GPS ... here it seems like JF used an old version of AFX that had a bug ... the fix is you just load up the airport in AFX, change something minor (e.g. I just tweaked airport elevation up and back down by 1ft), and save ... ILS service is restored.2) Some places I still had trouble, I tracked this down to airports in certain areas having spurious ILS defintions (though not assigned to runways) that belong to neighboring airports. For example KORD and KMDW were sharing one another's, and in the NY area I found huge confusion between JFK, Newark, LaGuardia, Teterboro and a couple of others. You need to go into Lists->Navaids... and delete the spurious ones. Checking against the stock version of the airport will confirm which ones you're meant to have. And where you find a spurious one, track down the airport that belongs to, as quite likely you'll find that in turn has spurious entries for other airports.Hope that helps.

Peedge, I really appreciate your taking time to pass along your experience. I haven't found anything on the TrafficX that gets at the problem. I will try your solutions. I know that "unchecking" TrafficX Sceneries makes the problem go away completely. I use ADE to adjust airports and your suggestions make sense. As soon as I can, I will give them a try.Thanks!

Peedge, I really appreciate your taking time to pass along your experience. I haven't found anything on the TrafficX that gets at the problem. I will try your solutions. I know that "unchecking" TrafficX Sceneries makes the problem go away completely. I use ADE to adjust airports and your suggestions make sense. As soon as I can, I will give them a try.Thanks!

The problem with disbaling TrafficX Scenery as a solution is that, you will get less AI traffic at the airports affected.Trafficx airports add extra parking spaces, you take them out, some airports will look a bit empty.One good thing about this problem is that its pattern is consistent- if both ends of runway share same ILS, the runway with higher number is the one youll pickup ils signal for , so for runway 28 and 10, on approach youll only get signal for 28.Better still dump Trafficx and move to MyTrafficx5.4, its much much much better.The AI in MyTraffix is about same standard as TrafficX, but aitports are filled better, even remote very small airports have traffic.And the airlines youll see at airports match what yioud expect, and that is gloabllyMilitary Air Bases nicely desne with Traffic , unlike Trafficx empty Militray Air fieldsAll together much better AI visuals all round, and none of this ILS issue.Cause if you go down route of fixing each airport, you may find that a very long road.