Training mission 6 - ILS issues at Teagu
-
-
Not sure what you’re asking for OP. The ILS crosshair is on all your pics. I circled it on this one.
-
-
Not sure what you’re asking for OP. The ILS crosshair is on all your pics. I circled it on this one.
I cannot see your img but on the first img there is not ILS crosshair.
-
I’m just checked the 4.34U2, KTO map, TE, TR_BMS_06_ILS_Weather mission, I had good ILS on Taegu RWY32, successfully landed. The mission start with the Mode selector on TCN NAV, are you sure you switched it to ILS/TCN?
-
Technically speaking, when flying an ILS, the cursor has no affect on the signal, so even if you set if off, 10, 20 , 100 or 180 degrees it will always show you left or right of course based on aircraft location. This is due to how the localizer (the left/right course deviation) and your aircraft antenna interpret the signal. Now, if you fly it backward it’s called a “back course” and in that case you need to reverse the direction of your course indicator in order to get what appears to be normal indications.
-
Korea 80 is not original KTO
That’s why it probably wasn’t updated with U2, as the ILS changes refers only to KTO.Molni, can you try with straight KTO please?
-
BTW what is the function of the CRS? I changed from 180 to 0 for Kunsan and it had 0 effect on anything…
That’s a bug in BMS. Normally, if you do not set the correct CRS in the DED ILS page, the system would never be able to calculate the best course to intercept the localiser (CMD STRG)
In BMS, the system will always guide you to best intercept course for the runway if you enable CMD STRG regardless of the CRS setting input in the DED T-ILS page, but that is not correct.
In the real jet, CMD STRG will guide you to the selected T-ILS DED CRS, if that one is off, guidance to intercept the localizer will be off too.It’s different than the CRS on the HSI as this one for an ILS does not need to be set for the ILS to work fine. It just makes it a million times easier to fly on the needle when the HSI match the runway heading.
But technically the deviation from the CDi will always be from the localizer radial, even if your HSI is 90° offFor an ILS you technically do not have to set the course on runway heading, but for CMD STRG to the localizer, you normally should
-
@Red:
Korea 80 is not original KTO
That’s why it probably wasn’t updated with U2, as the ILS changes refers only to KTO.Molni, can you try with straight KTO please?
I use the U2 as a base but somehow works in core theater. I do not understand. Mea culpa.
How can be found why is not working some ILS in my theater? -
every theater has its own data and thus campaign folder.
The ILS change from U1 to U2 was made in the stations+ILS.dat file of the KTO default theater.
Chances are that the Korea 80 file were not changed and still are on U1 level with the wrong frequencySo basically you need to compare both files (BMS\Data\Campaign\stations+ILS.dat file with BMS\Data\Add-on Korea 80*\Campaign\stations+ILS.dat)
- = whatever it is called
I’m quite sure both line for Taegu will be different, and that creates the discrepancies you see in TRN 06
If you terrain is only dbase changes and airbase are the same, then simply copy the stations+ILS file from default KTO (BMS\Data\Campaign) to your terrain campaign folder
And the frequency should be correct and thus the ILS working at Taegu