JNelson Posted August 31, 2018 Posted August 31, 2018 Me and a buddy were testing and noticed that even when the F-18 was killed first it still guided the Aim-7 on to target. At Mission start + 24:36 there is one incident where the AIM-7 impacts my friend 4 seconds after my aircraft is destroyed and mission start + 28:59 where the missile impacted my friend 14 seconds after I am destroyed. We could not reproduce the same result with the matra 530 it seemed to loose lock after death. Both instances above resulted in a spin that should have easily taken the radar out of gimbal limits even if the radar wasn't destroyed. Thanks Track file: https://drive.google.com/open?id=19LnmmH2w1WZtd9JZCyLKKobVBSd4qlK4 Tacview: https://drive.google.com/open?id=1qxJqZ9n6C5r9WCJbJAM83NPCe3pGV7SU Community A-4E-C
nighthawk2174 Posted September 2, 2018 Posted September 2, 2018 I've seen this behavior as well on several occasions +1
Svend_Dellepude Posted September 2, 2018 Posted September 2, 2018 Same thing in FC3. An old issue. Probably something to do with the radar memory timer. [sIGPIC][/sIGPIC] Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.
JNelson Posted September 2, 2018 Author Posted September 2, 2018 Same thing in FC3. An old issue. Probably something to do with the radar memory timer. Yea I known it's been around for a while but it is exacerbated by the increased performance of the AIM-7 and what with all the changes I thought best to bring it up. Community A-4E-C
Recommended Posts