Matrix Games Forums

Hi, I noticed that the active radar homing missiles have two different behaviors.

I setup a scenario, every BVR missile will be fired at 25nm, shooter will follow missile up (because there is a bug will cause F-14 to put the target outside the radar arc during crank, I will report this later)

One group like AIM-120D, AIM-54C, R-77 will go pitbull after the target is inside radar effective range.


Another group like AIM-120C, MICA, PL-12 behavior more like a SARH, they will not enable it's radar even hundred meters away from the target.
But if you let the shooter turn off radar after the missile left rail then the 2nd group of those ARH missiles will enable their radar.

OR,

if the shooter lose the track of the target, then missiles will turn on their radar too.


for example this one, due to Typhoon's doppler radar lose the tracking of the maneuvering target, the AMRAAM C enable radar at last minute. However it is too late and the missile overshot.

Also seen this on some launches of SAMs with ARH. This causes many misses, many more than should be misses.
AIM-260 seems to do this too on occasion with a very very low pH as a consquence.
It is almost as if the 'go active' command is not sent via the launching platforms datalink...

Hi

This problem has been going on for a long time. I have reported it on a couple of occasions.

However, despite not going pitbull, the missile is guided to the target but the behavior is not realistic.


Regards

Hi, testing this scenario on 1328.12 some of the missiles that were mentioned goes pitbull withou any issues. I've encounter the issue on AA-12 that will be investigated.

Thank you

https://imgur.com/a/2WLPGN4

Logged 0015417

Thanks
I have updated the game to 1328.12 this morning
FYI
Got to update the DB to V503
if keep the DB at V502, the issue is still there
BTW, the final PH formula has been adjusted again?

Tcao wrote: Tue Nov 21, 2023 2:24 pm
if keep the DB at V502, the issue is still there

I was using your scenario with DB502 so it's weird that you have a different behaviour with the DB change.

Issue appears to be fixed at the moment, should that not be the case, please reach back to us