LEI-JX Posted August 24, 2020 Posted August 24, 2020 The target is in the range, my awacs said there was a target, but my radar cannot see it. And if F16 has the AACQ function? just like the F18 one.
QuiGon Posted August 24, 2020 Posted August 24, 2020 60nm is quite a distance for a fighter sized target. The F-16 radar is not really the most powerful radar in the world ;) Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
SCPanda Posted August 24, 2020 Posted August 24, 2020 Your target is too far or its RCS is very low (such as an F-5). Also try to scan 1 bar with tight azimuth. Your target could also be manuvering and your datalink did not update. If it is not flying straight towards you, you will have a hard time acquiring a target that far away. Also keep in mind F-16's A-A radar is still WIP.
SCPanda Posted August 24, 2020 Posted August 24, 2020 Another possibility could be the target has been shot down and is falling from the sky, and your datalink did not update. Your AWACS will still call out the target since it is still in the air. Since it is falling from the sky, it is decreasing altitute rapidly and your radar might have a hard time acquiring the target. Anyway, there are so many possibilities that can explain why this happended.
Raven (Elysian Angel) Posted August 24, 2020 Posted August 24, 2020 Another possibility could be the target has been shot down and is falling from the sky, and your datalink did not update. Your AWACS will still call out the target since it is still in the air. This happens quite frequently in DCS, indeed. Spoiler Ryzen 7 9800X3D | 96GB G.Skill Ripjaws M5 Neo DDR5-6000 | Asus ProArt RTX 4080 Super | ASUS ROG Strix X870E-E GAMING | Samsung 990Pro 2TB + 990Pro 4TB NMVe | VR: Varjo Aero VPC MT-50CM2 grip on VPForce Rhino with Z-curve extension | VPC CM3 throttle | VPC CP2 + 3 | FSSB R3L | VPC Rotor TCS Plus base with SharKa-50 grip | Everything mounted on Monstertech MFC-1 | VPC R1-Falcon pedals with damper | Pro Flight Trainer Puma OpenXR | PD 1.0 | 100% render resolution | DCS graphics settings Win11 Pro 24H2 - VBS/HAGS/Game Mode ON
LEI-JX Posted August 24, 2020 Author Posted August 24, 2020 I checked my Tacview, The SU27 was not manuvering, I was at 42,000 ft, 0.95M The target SU27 was at 29,000ft coming in hot I locked the SU27 about 45nm And I fired my Aim120C 35nm away, after 1min and 24seconds, target SU27 splashed.
SCPanda Posted August 25, 2020 Posted August 25, 2020 Nice splash. I honestly have no idea why you cannot lock the Flanker until you get to 45nm, because I have had so many solid locks on Flankers or similar targets at around 60-70nm. Sometimes even around 70-80nm. Maybe it's the WIP radar behaving inconsistently. I do found it is easy to lose long range locks tho.
SCPanda Posted August 25, 2020 Posted August 25, 2020 Another guess from me is that you are at 42k ft and your target is at 29k ft, so your radar have to look down to find the target, and terrian background could have affected your radar's ability to acquire the target. It is easier to lock a target coming hot at you when both of you are at similar altitude.
Recommended Posts