[FIXED] AIM-54C stalling even at NEZ

[Naeradan]

Hi everyone,
testing the new features I found something suspicious.

Scenario: Tomcat armed with Phoenix (WRA set to NEZ) vs. oblivious, non evading Mig21 running straight at it at cruise speed.
The F14 locks on the target, identified as Unknown air contact flying at 480kt, and fires at around 40nm.
Seems in line with the new kinematic model, but after a few seconds of boosting, the Phoenix starts coasting, losing velocity, and stalls at around 20nm.
You need to lauch 3 Phoenix for the last one being launched near enough to hit the Mig, while by the definition of NEZ (the target doesn't evade and doesn't change speed) the first Phoenix should at least reach the bogey, if I understand correctly.
There is something wrong with the db entry maybe?

[thewood1]

I think there might be an issue with the direct flight path mode of the AIM-54. If I set the WRA further back, the flight is lofted and has enough energy to engage at the end. If it fires direct at 42nm, it loses all of its energy just past the halfway point. It might need a loft profile at anything under 20nm.

[Dimitris]

This has been fixed for the next update release.

[boogabooga]

There is also an issue in that the AIM-54A burn time is different between the CWDB and DB3000.

[Dimitris]

There is also an issue in that the AIM-54A burn time is different between the CWDB and DB3000.

As we recently explained, the boost times are not stored in the DB but dynamically calculated based on other properties (nominal range, weapon dimensions, weight, propulsion type etc.). So a discrepancy in boost times actually means a divergence in other data.

If you do notice such a case, please make a DB request on Github: https://github.com/PygmalionOfCyprus/cmo-db-requests