Jump to content

Gudauta NDB (XC) inop


Midnightzulu

Recommended Posts

According to the mission editor and Lino Germany's beacon map, there should be an NDB just off Gudauta Rwy33 on frequency 395.0, identifier XC. In the F-86 I tune 395 (verified by the kneeboard) and get an AIE (.- .. .) ident with no bearing info (bearing needle spins around indefinitely). If i tune just a little higher, still on 395 and into 396, I get a very strong ID of

SH (... ....) with a bearing of 355 degrees. Out of curiosity I took off and followed the bearing until I got North of Maykop. The needle was still pointing North.

 

Couple things:

 

1. XC doesn't seem to exist in game, or at least not tunable in the Sabre.

 

2. Wherever SH is, its signal is way too strong to be able to receive a good ID and strong bearing from a station somewhere North of Maykop while at the foot of a 12000ft mountain range on the ramp at Gudauta.

 

Please (re)comision XC NDB and fix the signal strength of SH NDB.

Link to comment
Share on other sites

Not seeing the issue, is there any wind that might disable the Gudauta NDB ?

 

attachment.php?attachmentid=189186&stc=1&d=1530814258

 

I'm sat on runway 33, with the NDB behind, the radio compass is pointing at 180°, i.e. confirming the NDB is behind.

 

Tested in the L-39ZA and F-86F in DCS Open Beta 2.5.2.17836

F-86F_ADF_Gudauta_2_5_2_18736_Screen_180705_185218.jpg.b3ac0e00fc057cf62ff04074ff92c8b5.jpg

i9 9900K @4.7GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 10 Pro x64, 1920X1080

Link to comment
Share on other sites

Had the winds set from the NW (343) at 4kts. Just to see what would happen I set the winds to calm and still have the same issue. I can see winds affecting which ILS is up, but NDBs, VORs, and TACANs should be unaffected by runway in use issues. Not sure why I'm seeing this issue. Not running any mods. I'm updating the stable version right now and will have a look there to see if its the same. Wondering if there are other settings in the mission editor I need to look at?

Link to comment
Share on other sites

Worked it out. No bug. Apparently it was something I had loaded into the mission. When I just dropped a single aircraft onto the ramp, everything worked fine. I'm wondering what could've caused the issue though. I think all I had loaded were a wingman, a HUMVEE, a half dozen static Sabres and a single static Huey. Somehow the mission generated the phantom NDB that was overpowering the one I was trying to tune. I'll start removing things from the original mission one by one to troubleshoot I guess.

Link to comment
Share on other sites

Had the winds set from the NW (343) at 4kts.

That will do it - there is a bug in DCS 2.5.x that effects most (all?) Caucasus airbases where the runway ILS/PRMG/NDB's turn off or switch direction compared to the 'active' runway, for light headwinds (1 to 6 knots).

 

Setting a 4 knot ground wind towards 163° (from 343°), disabled Gudauta's XC NDB and I saw a spinning ADF needle for 395 kHz and a phantom signal at 396 kHz.

 

Increasing ground wind speed to 6 kts, re-enabled the XC NDB.

 

Tested in DCS 2.5.2.17836


Edited by Ramsay

i9 9900K @4.7GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 10 Pro x64, 1920X1080

Link to comment
Share on other sites

  • 1 year later...
  • Recently Browsing   0 members

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