Having trouble with ILS

[Nealius]

I'm having some trouble with ILS, specifically at Kutaisi. I have the frequency dialed in (109.75), turn the ILS on, landing waypoint is set to Kutaisi, APP mode, on approach for RWY 08, no HUD or ADI cues, no synthetic runway. As I pass over the outer and inner markers, the "M" flashes in the HUD, but I still get no localizer or glideslope cues. Even with the ILS/VOR volume set to max, I get no beacon tone, nor do I get tones when passing over the markers.

 

I should note I'm still running 2.5.0.14304 since the recent updates have been breaking everything.

[myHelljumper]

Are you using the APP mode ?

[Nealius]

Yes. I mentioned that in my first post...

[Frederf]

ILS are not running all the time. They turn on and off based on the wind and it is a different schedule than ATC runway selection. In some situations the ILS for 09 Kutaisi is simply not operating.

 

The only requirement for ILS reception is the system be working (M) and set to the right frequency. Turn the V/ILS volume knob up to hear the identifier tones. The ADI shows the loc/gs needles.

 

With zero wind Kutaisi's 09 ILS works with an air-started Mirage with the only change being the ILS frequency and flight into the signal range of the system.

[Nealius]

I have wind set 270° 1kt in the ME, so that should make 09 ILS active if DCS wind logic hasn't changed (i.e. the heading is backwards). I get no identifier tone when I set ILS to 109.75, set to M (on), and ILS/VOR volume on.

 

Batumi ILS works on the same mission. It seems to be a problem with Kutaisi.

Edited March 30, 2018 by Nealius

[Frederf]

Wind to 270 degrees true, 1 knot. I get localizer audio at Kutaisi. Is this the open beta or main branch?

[Nealius]

2.5.0.14304 Open Beta. I'm curious if this is an issue at one point that was fixed with the recent updates. I've avoided updates for the past couple of weeks because so many users are reporting major bugs with just about every single module I fly.

[Frederf]

If you have other ILS-capable modules you could double check if it's the same when not in the Mirage. Since Batumi works it's probably either:

 

1. 09 ILS Kutaisi frequency entirely wrong

2. system off selectively due to wind

3. system permanently off due to some bug

 

I would try a very strong wind (20kt) and all wind directions 360, 045, 090, etc.) to see if some wind causes ILS 09 to work.

[Cake]

If you have other ILS-capable modules you could double check if it's the same when not in the Mirage. Since Batumi works it's probably either:

 

1. 09 ILS Kutaisi frequency entirely wrong

2. system off selectively due to wind

3. system permanently off due to some bug

 

I would try a very strong wind (20kt) and all wind directions 360, 045, 090, etc.) to see if some wind causes ILS 09 to work.

 

Does Kutaisi even have an ILS? I can only find old info that says it has NDB approaches. Assuming it has an ILS, Some airports share some ILS components on reciprocal runways. If that were the case, they'd typically switch the ILS to the active runway (so the active runway is on the front course)... the frequency would be the same, but the identifier would be different.

 

Unless this this scenario is happening, why would the ILS be be turned off for anything other than maintenance? I don't get it.

[jojo]

Yes, Kutaisi has an ILS in DCS 2.5 Open Beta mission editor.

It did have an ILS in DCS 1.5 Open Beta.

It doesn't seem to have one currently IRL.

[Ramsay]

I have wind set 270° 1kt in the ME, so that should make 09 ILS active if DCS wind logic hasn't changed (i.e. the heading is backwards). I get no identifier tone when I set ILS to 109.75, set to M (on), and ILS/VOR volume on.

 

With wind set at 1 kt towards 270° T, the active runway at Kutaisi reported by ATC was 26 in DCS 2.5.0.15365

 

Batumi ILS works on the same mission. It seems to be a problem with Kutaisi.

 

Increasing the wind speed to 4 kt towards 270° T changed the active ATC runway to 08 at Kutaisi in DCS 2.5.0.15365.

 

However Runway 08 ILS (109.75 kHz) wasn't active (tested using M-2000C and A-10C - no audio or ADI guidance). However the inner marker (477.0 kHz), VOR (113.6 MHz) and TACAN (44X) were all working (tested using M-2000C, L-39ZA and A-10C)

 

2.5.0.14304 Open Beta. I'm curious if this is an issue at one point that was fixed with the recent updates. I've avoided updates for the past couple of weeks because so many users are reporting major bugs with just about every single module I fly.

Almost certainly a WIP issue in DCS 2.5.0.15365 as Kutaisi Runway 08 ILS worked in the same mission, tested in DCS 1.5.6 with a M-2000C

Edited March 30, 2018 by Ramsay

[Nealius]

That's odd. When I contact ATC for taxi they tell me to use 08, not 26.

[Frederf]

Does Kutaisi even have an ILS? I can only find old info that says it has NDB approaches. Assuming it has an ILS, Some airports share some ILS components on reciprocal runways. If that were the case, they'd typically switch the ILS to the active runway (so the active runway is on the front course)... the frequency would be the same, but the identifier would be different.

 

Unless this this scenario is happening, why would the ILS be be turned off for anything other than maintenance? I don't get it.

 

DCS does odd behavior with radio landing aids. It turns non-conflicting aids on and off based on the weather using different criteria than the ATC runway selection. It's possible for particular wind setups to have ATC's runway selection and the nav aid's selection be opposite directions.

 

I don't know exactly how real airports operate but I would guess that all non-conflicting radio aids would operate at all times. In DCS that's not the case. Also shared frequency aids which would have different identifiers but in DCS they use the same ones.