Sunshadow Posted January 13, 2019 Share Posted January 13, 2019 Hi! I set up a scenario to practice AA radar: One TU-161 at 15000ft is flying at a distance of 140nm towards me. I'm also at 15000ft. So it should be no problem for the radar to detect the enemy plane with the default settings. But it didn't happen. I tried to change 1-6 bars, radar scale, changed elevation, width between 20-140 degrees, checked scanning altitude with the TDC at the known position - no signal. At about 80 nm I finally got an unstable contact(switched to 32 seconds of display time) but it disappeared all the time. Is this caused by radar jamming, wrong radar settings or bugs? I9 9900K @ 5Ghz | MSI Z390 Gaming Carbon Pro | KFA2 GTX 1080 Ti | 64 GB Kingston HyperX 2666Mhz | Samsung 960 EVO M.2 NVMe 250GB SSD | Pimax 5K+ | Warthog HOTAS | MFG Crosswind | Wheelstand Pro Flight Link to comment Share on other sites More sharing options...
backspace340 Posted January 13, 2019 Share Posted January 13, 2019 140nm is optimistic for the radar we've got in the Hornet - you should start picking large planes up at 100nm or so. Even at 100nm you'll need the radar set to high PRF, a narrow scan (20/40 degrees) and maybe a 2 bar scan to pick it up reliably. Link to comment Share on other sites More sharing options...
Sunshadow Posted January 13, 2019 Author Share Posted January 13, 2019 Hmmm... I had a 40 degree scan with 2 bars and moved the TDC cursor to the position of the enemy plane to be sure that the enemy is inside the scanned altitude... Have to try it again ;-) I9 9900K @ 5Ghz | MSI Z390 Gaming Carbon Pro | KFA2 GTX 1080 Ti | 64 GB Kingston HyperX 2666Mhz | Samsung 960 EVO M.2 NVMe 250GB SSD | Pimax 5K+ | Warthog HOTAS | MFG Crosswind | Wheelstand Pro Flight Link to comment Share on other sites More sharing options...
Recommended Posts