ILS 4L -- can't get it to work in KJFK v.2

[Michael2]

I can't get the ils to work for runway 4L.  There is a localizer signal when I tune to 110.9, but doesn't appear to have any geographical connection with the actual runway.  There doesn't appear to be any glide slope.

[Michael2]

Any answer for this? 

[theshack440]

Have you put the course in?

[virtuali]

The ILS works correctly and nobody else has reported a problem with it. As the below screenshot confirms, the 4L ILS is in the correct position and the glideslope is perfectly in sync with the PAPI lights too.

[Michael2]

Thanks for looking into it.  I guess it must be something at my end. 

[Jürgen Krebs]

I still have exactly the same problems with ILS RWY 4L - from the first Version of FSDT KJFK on up to the newest Version 2.1

[virtuali]

I still have exactly the same problems with ILS RWY 4L - from the first Version of FSDT KJFK on up to the newest Version 2.1

As I've said, The ILS works correctly, as the previous screenshot confirms.

Your problem is surely caused by another scenery in conflict and of course, since it was caused by another scenery, it's still there regardless if you install JFK V1 or V2.

The most common source of AFCAD conflicts are AFCAD coming from AI Traffic packages, use the free FSX Airport Scanner program to find AFCAD duplicates at KJFK but note that, if that program doesn't report anything, it doesn't mean you don't have a scenery conflict, because a misplaced ILS can also be caused by a non-AFCAD scenery, and these must be searched for manually.

[Michael2]

I have looked into the problem further and find I have problems with the ILS on mulitple KJFK runways.  I believe it is caused by the parallel runways using the same frequency at either ends at this airport, which is true for the default scenery as well as the FSDT addon. I tried disabling the backcourse availability using an airport editor program, but this did not solve the problem.  I guess I will end up trying to change the frequencies.