Jump to content

Set all ILS stations to always on


Yurgon

Recommended Posts

As far as I know, airfields in DCS will only turn on their ILS with a sufficiently strong headwind for an ILS-equipped runway. This has broken many missions, including some of the tutorials that come with DCS, over the years. It also keeps prompting new pilots to post problems with ILS in specific aircraft when, in fact, the ILS in the aircraft and module works perfectly fine - it's just not powered on for the runway they're trying to approach.

 

I suggest to turn on all airfield's ILS, always, unless there are unwanted side-effects.

 

At some point in the future, it would be nice to be able to control ILS via the Mission Editor and via Combined Arms. But for the time being, I see no downside in the glideslope and localizer signals being transmitted all the time.

 

Or am I missing some problems when a runway has ILS in both directions that would interfere with each other?

  • Like 4
Link to comment
Share on other sites

+1 very sensible idea.

 

As for the ILS emitting in both directions, it would be better if the ATC system just picked an active runway (and make it as consistent map wide) and stuck with it so only one ILS system is in use at any one time.

  • Like 1

Modules I own: F-14A/B, Mi-24P, AV-8B N/A, AJS 37, F-5E-3, MiG-21bis, F-16CM, F/A-18C, Supercarrier, Mi-8MTV2, UH-1H, Mirage 2000C, FC3, MiG-15bis, Ka-50, A-10C (+ A-10C II), P-47D, P-51D, C-101, Yak-52, WWII Assets, CA, NS430, Hawk.

Terrains I own: South Atlantic, Syria, The Channel, SoH/PG, Marianas.

System:

GIGABYTE B650 AORUS ELITE AX, AMD Ryzen 5 7600, Corsair Vengeance DDR5-5200 32 GB, Western Digital Black SN850X 1 TB (DCS dedicated) & 2 TB NVMe SSDs, Corsair RM850X 850 W, NZXT H7 Flow, MSI G274CV.

Peripherals: VKB Gunfighter Mk.II w. MCG Pro, MFG Crosswind V3 Graphite, Logitech Extreme 3D Pro.

Link to comment
Share on other sites

IRL all CAT III (and most CAT I/II) runways where you have ILS for both directions will be equipped with an interlock which prevents the ILS for reciprocal runways from radiating at the same time. There are several good reasons for this, both technical and safety related. Radiating in both directions can cause intermodulation between the signals, and depending on the monitor frontend selectivity, it can cause interfere with the monitoring systems. Some runways use the same frequency for both runway directions (e.g. Heathrow RWY 09R/27L = 109.5MHz and 09L/27R = 110.3MHz), and in these cases there is no way for the monitoring system to differentiate between radiated and received signals. And from an operational point of view you don't want to encourage use of both runway directions at the same time by having the ILS switched on.

  • Like 3
Link to comment
Share on other sites

13 minutes ago, drPhibes said:

IRL all CAT III (and most CAT I/II) runways where you have ILS for both directions will be equipped with an interlock which prevents the ILS for reciprocal runways from radiating at the same time.

 

Great info, thanks a lot! 👍

 

As it stands, right now many airfields probably won't activate any ILS at all unless there is sufficient wind.

 

So if a runway has ILS in both directions, I'd be perfectly fine if only one of them is active at any given time. This should also be the same runway that the in-game ATC advises to use in the initial call. But the runways with only one ILS should have it on at all times.

  • Like 2
Link to comment
Share on other sites

''Both ways'' shouldn't really be an issue, only one will be active at any time and that's the only one that should be transmitting. Basically it SHOULD use the same triggers used to determine the active.


Edited by zhukov032186
  • Like 1

Де вороги, знайдуться козаки їх перемогти.

5800x3d * 3090 * 64gb * Reverb G2

Link to comment
Share on other sites

54 minutes ago, zhukov032186 said:

''Both ways'' shouldn't really be an issue, only one will be active at any time and that's the only one that should be transmitting. Basically it SHOULD use the same triggers used to determine the active.

 

 

Exactly.

Modules I own: F-14A/B, Mi-24P, AV-8B N/A, AJS 37, F-5E-3, MiG-21bis, F-16CM, F/A-18C, Supercarrier, Mi-8MTV2, UH-1H, Mirage 2000C, FC3, MiG-15bis, Ka-50, A-10C (+ A-10C II), P-47D, P-51D, C-101, Yak-52, WWII Assets, CA, NS430, Hawk.

Terrains I own: South Atlantic, Syria, The Channel, SoH/PG, Marianas.

System:

GIGABYTE B650 AORUS ELITE AX, AMD Ryzen 5 7600, Corsair Vengeance DDR5-5200 32 GB, Western Digital Black SN850X 1 TB (DCS dedicated) & 2 TB NVMe SSDs, Corsair RM850X 850 W, NZXT H7 Flow, MSI G274CV.

Peripherals: VKB Gunfighter Mk.II w. MCG Pro, MFG Crosswind V3 Graphite, Logitech Extreme 3D Pro.

Link to comment
Share on other sites

+1

 

If you want to create realistic or doctrinal constraints on usage, there should be script APIs and/or ME controls for that, but if you don't they should just be 100% on. As it is opaque built-in, fragile, counter-intuitive, non-doctrine triggering only ever breaks things and causes confusion for zero benefit to anyone.

 

Oh, and while we're at it, we now have working portable TACAN. Where's the portable RSNB / ИСКРА? That and things like AWLS and ICLS is stuff that should be under the mission-makers control rather than something the module-maker has to fudge in for every new map, often taking ages to make it work, and often limited only to some imagined scenario the module maker might have in mind that does not match what the mission-maker wants.


Edited by Tippis
  • Like 1

❧ ❧ Inside you are two wolves. One cannot land; the other shoots friendlies. You are a Goon. ❧ ❧

Link to comment
Share on other sites

On 12/28/2020 at 9:02 PM, Tippis said:

Oh, and while we're at it, we now have working portable TACAN. Where's the portable RSNB / ИСКРА? That and things like AWLS and ICLS is stuff that should be under the mission-makers control rather than something the module-maker has to fudge in for every new map, often taking ages to make it work, and often limited only to some imagined scenario the module maker might have in mind that does not match what the mission-maker wants.

 

Absolutely!


Edited by Northstar98

Modules I own: F-14A/B, Mi-24P, AV-8B N/A, AJS 37, F-5E-3, MiG-21bis, F-16CM, F/A-18C, Supercarrier, Mi-8MTV2, UH-1H, Mirage 2000C, FC3, MiG-15bis, Ka-50, A-10C (+ A-10C II), P-47D, P-51D, C-101, Yak-52, WWII Assets, CA, NS430, Hawk.

Terrains I own: South Atlantic, Syria, The Channel, SoH/PG, Marianas.

System:

GIGABYTE B650 AORUS ELITE AX, AMD Ryzen 5 7600, Corsair Vengeance DDR5-5200 32 GB, Western Digital Black SN850X 1 TB (DCS dedicated) & 2 TB NVMe SSDs, Corsair RM850X 850 W, NZXT H7 Flow, MSI G274CV.

Peripherals: VKB Gunfighter Mk.II w. MCG Pro, MFG Crosswind V3 Graphite, Logitech Extreme 3D Pro.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...