Talvid Posted January 31, 2021 Posted January 31, 2021 I flipped my ADF switch to COMM1 and punched in 000.525 MHz, to set up nav to an NDB beacon, and pressed enter, all I got was ERROR on the UFC display. I also tried COMM2 and 000.718 MHz, while rolling the channel to Manual, and still got the ERROR message. I remember this working before the last stable update, it placed a bubble on my HSI showing the direction of the beacon. Bug? or am I doing something wrong? VR rig -
ED Team BIGNEWY Posted January 31, 2021 ED Team Posted January 31, 2021 Please add a track replay showing the issue, some beacons will turn off depending on wind direction. Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
drPhibes Posted January 31, 2021 Posted January 31, 2021 The last time I checked, the ADF in the F-18 wasn't compatible with regular NDBs. It uses the COM radio, which can't tune to frequencies below ~100MHz. 1
Talvid Posted March 27, 2021 Author Posted March 27, 2021 Copy all. I found that the ADF works fine when I punch in a beacon freq that is in 100s of Megahertz. I'm guessing these are VOR indicators. And it works, it places a bubble on my HSI that points in the direction of the beacon. I even figured out that after I turn ADF off I can hit the squelch UFC option button to turn off that incessant static sound. VR rig -
Recommended Posts