[Update 1567.6]Overshot, peter out, automatic fire and the frustration caused by these.
Posted: Mon Nov 27, 2023 8:33 pm
Please see Post #4
the bug is still here
it is making stealth vs stealth A/C battle quite annoying in 1567.6,
****************************************************************************************************
This seems to be a bug
I would like to present you with a scenario that is likely to cause some kind of frustration. A pair of F-22 armed with AIM-260 and AIM-9X intercept a lone J-20. For demonstration purposes the PL-15s have been removed, only SRAAM PL-10 kept in bay (with default 50% WRA). AIM-260’s WRA is set at 35nm, 2 rounds per target. At this distance, however, AIM-260 failed to acquire the J-20 so they overshot ( a little bit OT, AIM-260’s interception point seems to be way above the J-20 but that could be a WAD, need some more observation and testing). Now here is the frustrating part. If you leave the AI to do the automatic fire, it will never release 2nd salvo of missiles. As you can see from the screen, missile overshot happened at 225313. Then at 225354, 40 seconds later, the distance closed to 4nm. F-22 still refuse to auto fire , and J-20 released the PL-10 !
Bring up the attack dialog, it shows both AIM-260 and AIM-9X can be fired at this moment.
Lucky for F-22, they shake off the PL-10 and make a sharp turn. The first two AIM-260 also peter out. So the F-22s automatically fired one AIM-260 and one AIM-9X, finishing the dogfight in the blink of an eye.
Scenario have been attached
In short, after the first salvo of missile overshot, current system will put the target as “ have already been engaged “ and will not auto engage again until the pervious fired missiles disappear from the map.
A similar scenario can frequently happen in a stealth fighter vs stealth fighter scenarios, since the effective engage range is short while the missiles have very long range.
In a non-stealth fighter BVR scenarios, this might also happen but unfortunately, while observed that for several times, I don't have a save or a screenshot.
the bug is still here
it is making stealth vs stealth A/C battle quite annoying in 1567.6,
****************************************************************************************************
This seems to be a bug
I would like to present you with a scenario that is likely to cause some kind of frustration. A pair of F-22 armed with AIM-260 and AIM-9X intercept a lone J-20. For demonstration purposes the PL-15s have been removed, only SRAAM PL-10 kept in bay (with default 50% WRA). AIM-260’s WRA is set at 35nm, 2 rounds per target. At this distance, however, AIM-260 failed to acquire the J-20 so they overshot ( a little bit OT, AIM-260’s interception point seems to be way above the J-20 but that could be a WAD, need some more observation and testing). Now here is the frustrating part. If you leave the AI to do the automatic fire, it will never release 2nd salvo of missiles. As you can see from the screen, missile overshot happened at 225313. Then at 225354, 40 seconds later, the distance closed to 4nm. F-22 still refuse to auto fire , and J-20 released the PL-10 !
Bring up the attack dialog, it shows both AIM-260 and AIM-9X can be fired at this moment.
Lucky for F-22, they shake off the PL-10 and make a sharp turn. The first two AIM-260 also peter out. So the F-22s automatically fired one AIM-260 and one AIM-9X, finishing the dogfight in the blink of an eye.
Scenario have been attached
In short, after the first salvo of missile overshot, current system will put the target as “ have already been engaged “ and will not auto engage again until the pervious fired missiles disappear from the map.
A similar scenario can frequently happen in a stealth fighter vs stealth fighter scenarios, since the effective engage range is short while the missiles have very long range.
In a non-stealth fighter BVR scenarios, this might also happen but unfortunately, while observed that for several times, I don't have a save or a screenshot.