Consider Simflyers KLAX, RC3.1 Build 2272, FsNavigator and a custom AFCAD for KLAX.I am having a difficult time aligning to runways for ILS approaches. FsNavigator is reporting runway/ILS data drawn from SF-KLAXrwo1.bglThe custom AFCAD is located in the addon scenery default directory and has different assignments than FsNavigator.RC assigns a runway heading and frequency which is consistent with FsNavigator.However, I can never line up, get a LOC etc. For purposes of the ILS landing, which is taking precedent, the AFCAD or the KLAX rwy01.bgl?What can I do to bring everything into alignment.? Do I edit the runways.cvs file to reflect what is in the AFCAD?ThanksDom

what are the headings that rc has and the updates have? maybe the two are off by the magnetic variation amountjd

Possible.This is the data from runways.csvKLAX,0061,33.949162,-118.430611,126,69,8925,108.50KLAX,0062,33.946793,-118.434776,126,69,10285,111.70KLAX,0071,33.935879,-118.418793,126,69,12091,111.10KLAX,0072,33.933846,-118.418495,126,69,11096,109.90KLAX,0241,33.950130,-118.402206,126,249,10285,111.70KLAX,0242,33.952038,-118.402489,126,249,8925,108.50KLAX,0251,33.937443,-118.383270,126,249,11096,109.90KLAX,0252,33.939812,-118.380318,126,249,12091,111.10The attachment contains the afcadThanks

sorry, can't read the attachment. lax runways are 249 degrees and 69 degrees. what does your afcad file say they are?

Sorry..........24R IOSS 108.50 263.0 CATIII ILS/DME6R IGPE 111.70 083.0 ILS/DME6L IUWU 108.50 083.0 ILS/DME24L IHQB 111.70 263.0 ILS/DME25L ILAX 109.90 263.0 CATIII ILS/DME25R ICFN 111.10 263.0 ILS/DME 7L IIAS 111.10 083.0 ILS/DME7R IMKZ 109.90 083.0 ILS/DME25 IHHR 109.10 266.8 LOC

The airport diagram I have (Simplates 2004) shows a mag deviation of 13.9 degrees E. The AFCAD I looked at for UT2's version shows the same as above. If you subtract the mag deviation from the above, you get the mag headings in runways.csv and are therefore correct. The mag headings on the runways in the plate match those in runways.csv.From AFCAD docs:>>>>>>Magnetic Variation AFCAD will insert the magnetic variation for the airport in here. It is unknown if FS does anything with this, although it is conceivable that it is used by ATC when giving vectors for non-visual approaches. West magnetic variation is negative, so 12W is entered as -12. Localizer Heading The LOC heading for an ILS is always the same as the runway True Heading, or the reciprocal of the runway True Heading, depending on which end the LOC is for. If the LOC heading is not the same as the runway then it is considered to be an LDA (Localizer Directional Aid) or an offset localizer. LDAs are used to avoid obstructions or for noise abatement. Some airports in the U.S. with close parallel approaches use an LDA on one runway angled 2.5 to 3.0 degrees away from the adjacent ILS approach to increase lateral separation. <<<<<<

>Consider Simflyers KLAX, >I am having a difficult time aligning to runways for ILS>approaches.>What can I do to bring everything into alignment.? Do I edit>the runways.cvs file to reflect what is in the AFCAD?I had the same problem with the alignment of the KLAX ILS 25L. I uninstalled and then reinstalled the KLAX SimFlyers scenery set. The problem went away.-michael

It is possible if other add-ons are installed there might have been too many AFCAD bgls for KLAX spread around. Open KLAX in AFCAD2 with the airport open command. If more than one layer beyond the default is present open each one to get the full path/file name in the AFCAD window bar. Then rename the other than base layer files you do not want to keep. According to PAI only the base default and only one other AFCAD file can br present in the FS9 system or erratic results can be obtained. Deleting and reinstalling the scenery if it included the AFCAD file probably reordered things by causing a reindexing of scenery and AFCAD files.Just a guess. Also if the FS9.1 patch was run maybe that might have messed something up.Glad you found your solution.

>It is possible if other add-ons are installed there might>have been too many AFCAD bgls for KLAX spread around. Yes, this is possible, but not in my case. There was only the default AFCAD and the SimFlyers AFCAD - I manage my add-on and modified AFCAD files manually.>According>to PAI only the base default and only one other AFCAD file can>br present in the FS9 system or erratic results can be>obtained. Deleting and reinstalling the scenery if it included>the AFCAD file probably reordered things by causing a>reindexing of scenery and AFCAD files.Yes, this is true. It is also true that if you make a single change to an AFCAD file, FS will reindex the entire DB.-michael

Let's start again:RC is giving you the correct vector to intercept the LOC which should be 30 degrees away from the LOC heading.You can't begin to see the VOR or other indicator start to center as you fly along that heading?Here are some things to check:With opposite ends of the runway sharing the same LOC frequency, FS9 sometimes gets confused and feeds the wrong localizer into your nav system. If your nav system displays the LOC ident, or you crank up the audio for monitoring the LOC Morse Code ident as displayed, be sure you are receiving the correct LOC. In my case in a similar situation I sometimes only get the correct localizer only within a very small area away from the the extended center line. I use AP heading control to initially establish on the LOC always checking the ident and turn the aircraft to the inbound heading insuring I'm near the center before locking on APP mode (and always engage below the GS if present). If you are in fact getting the wrong LOC due to FS9's shared frequency bug (in real life on one would be turned on) you will get reverse course correction.Also be sure your VOR bearing is set for the correct inbound course.Now you state that RC and AFCAD agree on the info but FSNAV does not. It appears that FSNAV has a problem, perhaps similar to the FS9 bug.Try this: Bring up one of the Garmin GPSs which show the LOC pattern and use this as a backup guidance to insure you are on a vector to the merge. Also at this point, don't be locked to FSNAV on your AP. Use your VOR CDI or EHSI (I use Reality-XPs JL gauge sets).Use the ALT and HEADING AP control to merge, turn, and establish yourself on the LOC and after crosschecking with the GPS and the LOC ident on your EHSI or audio panel only then engage APP on your AP.Also note that if you have the wrong ILS for any reason your GS is invalid.In summary, I don't think you are having an RC problem.Now I don't use FSNAV so I'm not familiar with its features which I believe ncludes AP coupling. If it is causing a problem then disengage it after the initial vector is accepted. Close it out so there is no conflict on your final run coupling to the LOC.