Jump to content

Kobuleti ILS does not work


Recommended Posts

Kobuleti ILS isnt working. Can aynone confirm?

It works for the AV-8B's AWLS with 0 wind, but if there is a 5 kts headwind, although runway 07 is the active runway, 07 ILS is turned off.

 

Seems similar to this NDB bug, so is probably related.

 

Tested DCS 2.5.0.15365


Edited by Ramsay

i9 9900K @4.7GHz, 32GB DDR4, RTX2070 Super 8GB, 1TB NVMe, 6+4TB HD, 1+1TB SSD, MSFFB2 joystick, X52 Pro Throttle, TIR5, Win 10 Pro x64, 1920X1080

Link to post
Share on other sites
It works for the AV-8B's AWLS with 0 wind, but if there is a 5 kts headwind, although runway 07 is the active runway, 07 ILS is turned off.

 

Seems similar to this NDB bug, so is probably related.

 

Tested DCS 2.5.0.15365

 

Just tested with no wind and got it to work. Maybe this is it.

Link to post
Share on other sites

ILS will switch on and off for different wind but not at the same condition that active runway (ATC) changes so it's possible for ILS to be configured as if active runway is X when ATC says it is Y.

 

In Kobuleti's case since it doesn't have ILS for both directions when it switches directions you simply get nothing.

Link to post
Share on other sites
ILS will switch on and off for different wind but not at the same condition that active runway (ATC) changes so it's possible for ILS to be configured as if active runway is X when ATC says it is Y.

 

In Kobuleti's case since it doesn't have ILS for both directions when it switches directions you simply get nothing.

AFAIK

 

• The ILS changes direction depending on the magnitude of the wind and doesn't take wind direction into account.

 

The behaviour in 2.5 is different to 1.5.8, etc. and appears to be a bug.

i9 9900K @4.7GHz, 32GB DDR4, RTX2070 Super 8GB, 1TB NVMe, 6+4TB HD, 1+1TB SSD, MSFFB2 joystick, X52 Pro Throttle, TIR5, Win 10 Pro x64, 1920X1080

Link to post
Share on other sites

Note:

 

Kobuleti 07 ILS is ON for 0 kts and +7 kts headwinds and OFF between 1 - 6 kts headwinds.

 

ATC also has a discontinuity at a 1 knot headwind as it changes to runway 25 but switches back to runway 07 for a 2 knot headwind.

 

Wind direction was towards 250°T and always appropriate for ATC's default RWY 07

i9 9900K @4.7GHz, 32GB DDR4, RTX2070 Super 8GB, 1TB NVMe, 6+4TB HD, 1+1TB SSD, MSFFB2 joystick, X52 Pro Throttle, TIR5, Win 10 Pro x64, 1920X1080

Link to post
Share on other sites

It's as you say. It would be simpler if all airports were weird in the same way but this is odd behavior different than Vaziani. All 21 airports probably need checking individually for ATC and landing aid function for their "wind maps," not a short task.

Link to post
Share on other sites
  • 1 year later...

Is this now broken in a different way? I'm setting a 7 knot headwind on runway 07 (wind direction blowing towards 250 in the mission editor), I fly a circuit and hit the B3B (RTN) waypoint dead on, and no ILS.

 

 

P.S. Tried it with 0kt wind too and that didn't work either.


Edited by Neutrino
Link to post
Share on other sites

Probably worth noting that if I set the winds to 0kts ATC sets the active runway to 250 (which is the runway without ILS) so that seems different from what some of the last posters have said about how they got it to work.

Link to post
Share on other sites
Probably worth noting that if I set the winds to 0kts ATC sets the active runway to 250 (which is the runway without ILS) so that seems different from what some of the last posters have said about how they got it to work.

 

Please post a track or your mission as I can't replicate your issue in Open Beta 2.5.5.31917

 

attachment.php?attachmentid=211453&stc=1&d=1559938511

 

Kobuleti

ATC 133MHz, 262MHz

TACAN X67

 

RWY 07 (64°M / 70°T)

ILS 111.50

OM 870 kHz, IM 490 kHz

1262182821_C-101EBILSKobuletiScreen_190607_203335.thumb.jpg.65b132da59e507deba46d789400b98a2.jpg

i9 9900K @4.7GHz, 32GB DDR4, RTX2070 Super 8GB, 1TB NVMe, 6+4TB HD, 1+1TB SSD, MSFFB2 joystick, X52 Pro Throttle, TIR5, Win 10 Pro x64, 1920X1080

Link to post
Share on other sites
Here's my mission. Su-25T ramp start at Kobuleti.

Lol, the Su-25T doesn't have western ILS equipment, so can't receive the signal**.

 

The Su-25T is equipped with a Russian equivalent, PRMG, it'll work at:

 

• Mozdok RWY 08/26

• Maykop RWY 04*

• Krasnodar-Center RWY 09

• Krymsk RWY 04/22

 

*Note: With zero wind, DCS's ATC defaults to RWY 22 which doesn't have PRMG

 

**Note: DCS didn't always differentiate between Western and Russian ILS systems but that changed several years ago.

 

Here's a free flight mission I've made for Krymsk RWY 04 with working PRMG (ILS) for the Su-25T

 

It's set to use Georgian aircraft / English ATC but you can change the aircraft/airbase to Russian in the ME, if you prefer DCS's native Russian ATC, etc.

 

Tested in Open Beta 2.5.5.31917


Edited by Ramsay

i9 9900K @4.7GHz, 32GB DDR4, RTX2070 Super 8GB, 1TB NVMe, 6+4TB HD, 1+1TB SSD, MSFFB2 joystick, X52 Pro Throttle, TIR5, Win 10 Pro x64, 1920X1080

Link to post
Share on other sites
To stop me from making the same mistake again How do you tell from the mission editor which aircraft are compatible with which airfields?

It's not so easy in the mission editor but if you look closely, you'll see that PRMG airfields have channel numbers next to the localiser center line rather than a ILS frequency.

 

You should note that, in DCS, the Su-25T is not wholly incompatible with Non-PRGM airbases, just that you won't get active ILS needles on the HSI or the small HUD guidance circle.

 

For example, on your sample picture

 

attachment.php?attachmentid=211498&d=1559983835

 

• The red glide slope and localizer flags have cleared on the HSI, showing the Su-25T recognises Kobuleti's active ILS.

• The HSI shows the desired runway course

- Numerically i.e. 070 = 70°T

- With the large double needle

• The thin HSI needle (ADF ?) points to the airbase - in your picture the double and thin needles are lined up so the runway is ahead and you are on it's center line.

• The HSI's DME = 009, showing you are 9 km from the airfield.

• The ADI Flight Director is giving steering guidance - at DME = 9 km and 520 m you are :

- on the localizer/desired course (vertical needle centered)

- slightly high (horizontal needle slightly low) i.e. at 9 km, a 3° Glide Slope = 50m per km, so 9 km * 50 m = 450 m

 

I'm not sure if what is in DCS is by design but IMHO, it's sufficient to learn basic ILS and radio navigation before moving to a 'full' module.

 

Note: if you overfly the runway or making several passes in the Su-25T, you'll often have to cycle the navigation mode (Enroute\Return\Landing), so the Landing(NOC) mode instruments switch/operate correctly.

 

This is a explanatory chart I created several years ago:

 

RxIGHzO.jpg

 

Tested in Open Beta 2.5.5.31917


Edited by Ramsay
The raw ILS data on the ADI scales is unreliable in 2.5.5

i9 9900K @4.7GHz, 32GB DDR4, RTX2070 Super 8GB, 1TB NVMe, 6+4TB HD, 1+1TB SSD, MSFFB2 joystick, X52 Pro Throttle, TIR5, Win 10 Pro x64, 1920X1080

Link to post
Share on other sites
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...