AFAIK the ILS localizer simulated in FSX is set by true bearing and magnetic variation has no impact on it whatsoever. The FSX GPS (and AI tracks) do use magnetic courses. For the GPS it is the "line draw" and if you have an ILS approach selected and the gps/nav switch in gps, the default flight director/AP and deviation indicator will be based off that line draw (not the sim raw localizer). Even with the possible line draw issue, the waypoints which anchor the lines are set by lat/long so the line can only vary just so much (for example, the final approach fix will be a target and will be in correct position relative to runway). If you move the switch back to nav position, you will get sim raw localizer and that will be correct.

 

Don't know if the the sim automated flight features in the advanced aircraft use the default FSX capabilities or do their own sim. If the later then you need to look at the addon sim feature that isn't working correctly. I think Master Chief Dave is absolutely correct that the CRS knob does nothing in FSX except rotate the compass card (on an HSI) for localizer sim. If the CRS is doing something on your addon, you need to look at the addon sim function.

 

scott s.

.

OK so the problem must be with FSX. I uninstalled UK2000 tried the EGLL circuit and CYYZ circuit. Both times I could not activate the localizer. Something must have corrupted somewhere. I tried the exact same circuits on my iMac and everything worked as it should.

 

Does anyone have any idea what file/files contain the ILS information?

 

I could return to an earlier backup I made with a fresh install of FSX if I don't get anywhere

 

Thanks for your help anyway guys

 

Richard

I dont have the airbus, but the ngx and md-11 had similar problems at different airports. All has to do with the scenery not aligning, or the AFCAD from what I understand. Even then it may not fix it to update it as the AFCAD may only up date the ils freq and course but not the whole airport alignment.

 

You can try this page for some AFCAD files updating. Most are 2012. Or search the airport name for an AFCAD. May or may not help and if not careful you can cause conflicts with weird black boxes on the ils approaches. Just an idea. im no expert. It solved a few airports for me though.

If only we could update FSX with an AIRAC it might help some.

 

http://www.blueprintsimulations.com/BluePrint_AFCADS.html

OK so I have done some experimenting and basically what happens is that when this problem occurs on a particular runway, lets use 24L at CYYZ. The correct ILS frequency is entered but on the PFD it shows the ident code for the localizer at the other end of the same runway.

 

Eg 24L has a freq of 111.95/IDP but on the PFD 111.95/ICV shows which is the ident for 06R

 

I still have no idea whats caused this but I guess the only thing I can do is cross reference what is shown on the approach chart and in the event of an error choose a different runway.

CYYZ shares the same freq. for 24L, just as 15R shares the same freq for both ends. I'm not a "tuber", but doesn't the FMC offer the choice for the correct ident? Not being snarky or anything, but isn't it the pilot's responsibility to make sure the FMC or whatever it's called is programmed correctly? That would include making sure the correct ILS approach is entered, so that it doesn't surprise you by wanting to do a 180 deg turn-around.

 

I'll now go back to flying my itty-bitties... :ph34r:

OK so I have done some experimenting and basically what happens is that when this problem occurs on a particular runway, lets use 24L at CYYZ. The correct ILS frequency is entered but on the PFD it shows the ident code for the localizer at the other end of the same runway.

 

Eg 24L has a freq of 111.95/IDP but on the PFD 111.95/ICV shows which is the ident for 06R

 

I still have no idea whats caused this but I guess the only thing I can do is cross reference what is shown on the approach chart and in the event of an error choose a different runway.

 

Where is your aircraft physically located when this happens? In FSX, when a given runway has an ILS off of both ends, the position where your aircraft is located (in relation to the runway) is extremely significant when both ILS localizers use the same frequency, which is exactly the case with Toronto's 06R / 24L The runway 24L ILS uses the frequency 111.95 with ident "IDP". The runway 6R ILS also uses the frequency 111.95, with the ident "ICV".

 

At a real-world airport where a particular runway uses the same frequency for an ILS approach off of both ends, the local tower would never have both localizers running at the same time. Depending on the direction of landing traffic, they would activate the transmitter at either one end or the other, but never both. Obviously, in the simulation, there is no human tower controller to switch on one ILS or the other, so the one that is received on your ILS receiver is based entirely on the position of your aircraft.

 

Let us take the example of an imaginary runway 09 / 27 which runs due east west. It has an ILS off of either end, both on 109.1 mHz, with the runway 09 ILS having the ident "ABC" and the runway 27 ILS with the ident "XYZ". Now, picture a line, running due north and south, bisecting the runway at its exact midpoint.

 

If you are at this example airport in FSX, with your NAV radio tuned to 109.1, if you are physically positioned anywhere to the west (left) of the north / south dividing line, your will receive the runway 09 ILS, with the runway 09 "ABC" ident. If you are anywhere east (right) of the dividing line, you will receive the runway 27 ILS, with the "XYZ" ident.

 

It works this way both in the air, and on the ground. If you are parked on the ramp, you will receive the ILS localizer and ident of whichever runway threshold happens to be closest to where you are parked at the time.

 

In flight, if you are approaching the airport on a long downwind leg with the ILS pre-tuned, you will receive the "wrong" ILS signal and ident, until your downwind leg carries you past the midpoint of the airport, after which the "right" ILS will be received.

 

It definitely works this way in virtually all of the default FSX aircraft, and with all of the add-on enhanced aircraft I have used (PMDG, LevelD etc.). Perhaps the Airbus Extended does not work properly in this regard, but before determining that the aircraft is at fault, you need to verify where you are in relation to the ILS you are trying to receive.

Where is your aircraft physically located when this happens? In FSX, when a given runway has an ILS off of both ends, the position where your aircraft is located (in relation to the runway) is extremely significant when both ILS localizers use the same frequency, which is exactly the case with Toronto's 06R / 24L The runway 24L ILS uses the frequency 111.95 with ident "IDP". The runway 6R ILS also uses the frequency 111.95, with the ident "ICV".

 

At a real-world airport where a particular runway uses the same frequency for an ILS approach off of both ends, the local tower would never have both localizers running at the same time. Depending on the direction of landing traffic, they would activate the transmitter at either one end or the other, but never both. Obviously, in the simulation, there is no human tower controller to switch on one ILS or the other, so the one that is received on your ILS receiver is based entirely on the position of your aircraft.

 

Let us take the example of an imaginary runway 09 / 27 which runs due east west. It has an ILS off of either end, both on 109.1 mHz, with the runway 09 ILS having the ident "ABC" and the runway 27 ILS with the ident "XYZ". Now, picture a line, running due north and south, bisecting the runway at its exact midpoint.

 

If you are at this example airport in FSX, with your NAV radio tuned to 109.1, if you are physically positioned anywhere to the west (left) of the north / south dividing line, your will receive the runway 09 ILS, with the runway 09 "ABC" ident. If you are anywhere east (right) of the dividing line, you will receive the runway 27 ILS, with the "XYZ" ident.

 

It works this way both in the air, and on the ground. If you are parked on the ramp, you will receive the ILS localizer and ident of whichever runway threshold happens to be closest to where you are parked at the time.

 

In flight, if you are approaching the airport on a long downwind leg with the ILS pre-tuned, you will receive the "wrong" ILS signal and ident, until your downwind leg carries you past the midpoint of the airport, after which the "right" ILS will be received.

 

It definitely works this way in virtually all of the default FSX aircraft, and with all of the add-on enhanced aircraft I have used (PMDG, LevelD etc.). Perhaps the Airbus Extended does not work properly in this regard, but before determining that the aircraft is at fault, you need to verify where you are in relation to the ILS you are trying to receive.

 

Hi Jim,

 

Thank you for your reply, that was a great explanation. Each time I have experienced this issue I have made sure I am approaching the relevant runway from the correct direction before initiating the ILS frequency. The previous poster seems to think this is "Pilot Error" I agree I am new to this hobby but in the 3 months I have been doing it I have taken the time to study and learn how to read airport charts and approach plates and I know how to plan a route using the correct Sids/Stars/Transitions. This problem has manifested itself recently. I know it is an FSX issue because I have recreated the circuits I flew last night on another computer running FSX with the same aircraft and not had these issues at all. When I 1st started flying I saw exactly what you described in the wrong ILS ident being shown due to my position in relation to the airport. Since then I exclusively fly using routes I create with FSC so I always check my approach is correct. I have gone through the FMC setup of the PMDG737 NGX to see if there is a way I can select a different ILS Ident in the case where a single runway uses the same ILS frequency but I haven't found a way to change it.

 

I am sure it is something I have added to FSX that has corrupted a config file somewhere. When I added the SSD to my system I did a complete re install and took the time to backup a fresh version of windows then another backup with a virgin FSX + Acceleration just incase I ever run into any issues.

 

I am quite happy to revert to a backup but I am more curious to find out what the true cause of this was so that I can correct if it happens again or help others who have the same problem and do not have a good backup to revert to. I know how long it takes to do a fresh windows install and setup & tweak FSX

 

Richard

This is all fine and well. However, the only aircraft I am having a problem with is the Airbus X Extended. I must have well over 1000 hrs with the NGX alone and countless ILS approaches without a glitch.

I solved the problem !! After much searching I found the same issue posted by a TrafficX user. I had to disable an addition by TrafficX in the scenery library. I'll post exactly what it was when I get home.

 

Did 2 quick circuits at CYYZ & EGGL before leaving this morning and all is well

 

Richard

I solved the problem !! After much searching I found the same issue posted by a TrafficX user. I had to disable an addition by TrafficX in the scenery library. I'll post exactly what it was when I get home.

 

Did 2 quick circuits at CYYZ & EGGL before leaving this morning and all is well

 

Richard

 

For anyone that has TrafficX installed and comes across this ILS issue, I did the following.

 

In FSX Scenery uncheck Traffic X Airport Facilities

I am not sure what this does but it fixed the ILS ident issue. I am going to try emailing justflight support

 

Happy flying!

 

Richard

For anyone that has TrafficX installed and comes across this ILS issue, I did the following.

 

In FSX Scenery uncheck Traffic X Airport Facilities

I am not sure what this does but it fixed the ILS ident issue. I am going to try emailing justflight support

 

Happy flying!

 

Richard

 

Good for you! ^_^ Strange though, as I don't have Traffic X. <_<

 

Just now, I did an ILS approach into 26L at Atlanta, using only default scenery. The Airbus X Extended followed the STAR all the way into the final app course. I-AFA tuned and identified. Bang smack on the localizer, I went to select LOC.. and weeeee hard right 90 degrees. Piece of s....

I had a similar issue with an approach into Atlanta last week, I can't remember which runway but the localizer had been captured and the same thing instead of turning on to the final approach it went off in completely the wrong direction. This was in the PMDG737 NGX so the issue may not be with your bus. I will try a circuit later landing at 26L and let you know what happens

I had a similar issue with an approach into Atlanta last week, I can't remember which runway but the localizer had been captured and the same thing instead of turning on to the final approach it went off in completely the wrong direction. This was in the PMDG737 NGX so the issue may not be with your bus. I will try a circuit later landing at 26L and let you know what happen

 

It did say 26L, didn't?.. sorry, it was actually 27R if you want to check that.

 

I must say, this is weird. Never had any trouble with any of the ILS approaches at Atlanta and I have flown into ATL quite a few times...

LOL

 

I just did a circuit taking off from 26R landing 26L with no problems

 

I'll try again

Hi Daniel,

 

I took off from KATL 26R and landed on 27R. Everything worked well and I successfully captured the localizer and performed an auto land in the PMDG 737NGX. I remember when I first had the issue described at the beginning of this thread it happened on 2 different planes. In the NGX I wasn't able to select the LOC button for certain runways. In the Airbus X extended trying to do the same approach I was able to select the LOC button and it looked like it captured the localizer properly but then the plane turned way off course so I was sure the problem was with FSX and not the aircraft which appeared to be the case. For me I started looking at all the addons I have. Luckily I started with TrafficX which was my last addition.

 

Some food for thought, hope you figure it out

 

Richard