Bravo Posted February 19, 2016 Posted February 19, 2016 Hi, Ive been doing some testing with the AIM-9M from an A-10C towards different targets, Flares, SUU-2, M-257, HIP and A-10C. My findings are; Both in 1.5.2 and 2.0.1 The AIM-9M Will find and track the HIP, A-10C and also a already fired AIM-9. The AIM-9M will NOT lock onto flares dropped by the target(HIP, A-10C) prior to launch. The AIM-9M will NOT acknowledge SUU-2 or M-257. In 1.5.2 BUT! if flares are dropped after launch the missile will go for the flares and pass straight through them. It wont hit the flare and explode but continue straight and hit the ground. in 2.0.1 I observed something different, Im not sure if the code is new or not, but my guess is that it is a little different. The AIM-9M would after launch track the Flares and after passing the flare change course drastically for flares dropped by FW, while start diving towards the ground when passing flares dropped by RW. There was a TV show that aired a couple of years ago on TV where you could see an RNoAF F-16 fire an AIM-9L at a flare where it hit and exploded near the flare. Im not sure if this is the deal with AIM-9M but I am curious to if you have some comments to this? I noticed that in 2.0.1 It will track the Sun which I think is Awesome. I did not test this is 1.5.2 I believe, that pending on the seeker head the angle towards the sun it will be able to track a target vs the sun will be different. This I have not tested as I do fly anything else that can fire other missiles(Not known with how the SU-25 works, so not tested) But when I steer the seeker towards a Flare, SUU-2 or M-257 it is unable to acquire them. Seeing how the AIM-9 track flares after launch why does it not acknowledge them prior to launch? If locked onto a aircraft and the computer logic says follow the movement, OK but this seems so complex I doubt it true, then you should have the logic in the missile and not in the aircraft and thereby it should not track flares the way they what it does even after launch. If it sees "profiles" that looks like aircrafts, the same should be true. It would ignore flares dropped unless then look like the profile of an aircraft. but also lock onto flares with "profile" prior to launch. And when the flare, SUU-2 or M-257 is the only heat source it sees it should acknowledge and track it as well should it not? These sources are just a extremely tiny sun or just another heat source like the fumes from a aim-9 already fired? Im not a engineer or have that much insight but logically I am wondering if this is a bug, not implemented at this time or to classified to modell? To te ED team, Thanks for making a awesome simulator for us!
Espéce De salaud Posted February 20, 2016 Posted February 20, 2016 Regarding the aim9 expolding near the flare is some kind of proximity detonation thing, it is surprising that that still happens or how you tell the missile (or it figures out) when to detonate on impact or near it.
Bravo Posted February 20, 2016 Author Posted February 20, 2016 according to open sources, imcluding http://www.f-16.net/f-16_armament_article1.html Most of the Aim -9 prior to the L used magnetic field proximity fuzes but not exclusively those. the AIM-9L uses a Gallium-Arsenide laserdiodes and corresponding photodiodes that notices when light is reflect back to it. while the later L and M has improved counter countermeasures, this may be why its modelled that the missile continues after passing the flare. But even with ICCM I find it odd that the missile will not recognize flares or other heat sources prior to being launched at an aircraft. it seems to be coded to only be affected by countermeasures after launch, but I dont know and Im curious to if this is the case and if this bug can easily be corrected if this is the case
xaoslaad Posted February 20, 2016 Posted February 20, 2016 I'm 99.999% certain I've seen heaters track flares prior to launch.
Bravo Posted February 20, 2016 Author Posted February 20, 2016 Do you remember if it was from an A-10 or other A/C?
Recommended Posts