Jump to content

Recommended Posts

Posted (edited)

I have a simple mission, L-39 starting at Mozdok, hot on runway, bit of a crosswind towards 201°. RWY 08 is chosen for me - in this case probably any runway would do, but that's not the problem. NDBs for Mozdok are tuned in, but the wrong ones are activated (R and RM codes, instead of D and DO ones). Both NDB sets have the same frequency, so L-39 tuning doesn't care, but ADF clearly shows me the way ahead instead of pointing behind me. ADF morse codes confirm the wrong NDBs as well.

Because the mission was "old", I decided to recreate it, not being sure when the ATC "makes the decision" (I hope it's when the mission is loaded, for the progress' sake) - both tracks are attached. Strangely, when I fiddle with the wind a bit, the right NDBs can be activated.

The bottom line is: Why am I on one end of the runway and NDBs are activated for the opposite runway? The logic here should be tight together. I don't know whether I'm on the wrong runway, or wrong NDBs are activated, but it should at least be consistent.

BTW: If I ask ATC for an approach, it suggests 08 which is consistent with the RWY I started on - which means it sends me to over the non-active NDBs.

mozdok-l39-wrong-beacons.trk mozdok-l39-wrong-beacons2.trk

Edited by virgo47
  • Like 1

✈️ L-39, F-4E, F-5E, F-14, F/A-18C, MiG-15, F-86F, AJS-37, C-101, FC2024 🛩️ Yak-52, P-47, Spitfire, CE2 🚁 UH-1H, Mi-8, Ka-50 III, SA342 🗺️ NTTR, PG, SY, Chnl, Norm2, Kola, DE 📦 Supercarrier, NS430, WWII, CA 🕹️ VKB STECS+Gladiator/Kosmosima+TPR ▶️ DCS Unscripted YouTube 🐛 "Favourite" bugs: 1) Object local camera fast/slow inverted, 2) Yak-52 toggles not toggling, 3) all Caucasus ATC bugs

  • 2 weeks later...
  • Recently Browsing   0 members

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