I'm having problems with kdfwv3.zip By William Morgan dealing with RWY 18R/36L for a ILS approach and it happens everytime with any aircraft I use.When I try to capture the ILS beam and click the approach mode and the autopilot on a RWY 18R approach the aircraft makes a attempt to capture then veers off to heading due N away from the airport, this happens everytime I try to use that approach, Is there a update for that airport or can someone help resolve the issue?Also is there a way to make all the runways active?If you need a copy of the afcad to see if ya'll can fix the issue let me know I'll send it to youThanks I appreciate it

A couple questions:Does this happen with any other approaches at DFW, such as 17C, 36L?When do you shut off the autopilot during approach?Did you try emailing the author? [email protected]

Hi Ernie,The AF2 file that comes with the scenery has all runways active, 13-31s usable with the 18-36s and 17-35s, if that's what you mean. However, if you want to assign certain runways for landing or take-off make sure you do it for both ends otherwise FS runway assignment might be erratic.Concerning your ILS problem, is the localizer beam aligned with the runway? In other words, does the aircraft align correctly with the runway 18R in LOC mode?

Hi Ernie,The AF2 file that comes with the scenery has all runways active, 13-31s usable with the 18-36s and 17-35s, if that's what you mean. However, if you want to assign certain runways for landing or take-off make sure you do it for both ends otherwise FS runway assignment might be erratic.Concerning your ILS problem, is the localizer beam aligned with the runway? In other words, does the aircraft align correctly with the runway 18R in LOC mode?

No it doesn't align correctly, when you switch the autopilot into LOC mode in does the samething, the plane looks like its going to turn to capture the beam but turns off to the opposite direction, almost like its run a backcourse, I tried the other approaches 18L and 17/35 and they are working just fine, its just 18R

Hmmm :( In that case it looks like the LOC/GS beam is misaligned, let me check mine. I'll let you now how it goes.

Hmmm :( In that case it looks like the LOC/GS beam is misaligned, let me check mine. I'll let you now how it goes.

On my AFCAD 18R and 36L both use the 111.9 wavelength, and both have a backcourse activated. That can't be right!I have found AFCADs for other airports where this has given problems, presumably FS gets confused as to whether you are using the ILS or the BC. First thing I would do would be to de-activate the BCs, using ADCAD2 or AFX and if that doesn't work I would allocate a different wavelength to one of them. I'm only guessing this may be the solution, I haven't tried it at this airport myself.John

On my AFCAD 18R and 36L both use the 111.9 wavelength, and both have a backcourse activated. That can't be right!I have found AFCADs for other airports where this has given problems, presumably FS gets confused as to whether you are using the ILS or the BC. First thing I would do would be to de-activate the BCs, using ADCAD2 or AFX and if that doesn't work I would allocate a different wavelength to one of them. I'm only guessing this may be the solution, I haven't tried it at this airport myself.John

I have AFCAD2 also and I checked that also, but I didn't attempt yet to change it because I wanted someone elses opinion or if there was a update I just didnt see for it.

Ernie,I suspect your problem is with the localizer beam rather than the glideslope. Your localizer ident is I-VYN / 111.9, and you set your course to 174 right? I tested mine with no problems.John's idea is good too, you can try to disable the backcourse for 18R-36L. If not, drop me a PM and I'll send you my AF2 file.

Ernie,I suspect your problem is with the localizer beam rather than the glideslope. Your localizer ident is I-VYN / 111.9, and you set your course to 174 right? I tested mine with no problems.John's idea is good too, you can try to disable the backcourse for 18R-36L. If not, drop me a PM and I'll send you my AF2 file.

Yup, I set it to 174, and 111.90, I did think about shutting off the backcourse on both but I wanted to get some opinions on it before I did.

Yup, I set it to 174, and 111.90, I did think about shutting off the backcourse on both but I wanted to get some opinions on it before I did.

I turned off the backcourse option on RWY 18R/36L and I checked it out and got to report it is working right now, thanks for the advice.

I turned off the backcourse option on RWY 18R/36L and I checked it out and got to report it is working right now, thanks for the advice.

Excellent news!Check the other runways, too - I found they were all set up similarly on the AFD file I have.And . . . racking my brains . . . I think the initial location I discovered this problem at was at KJFK so you may want to check the runways there too - although I think I have an add-on now that superseded the one that gave problems.John