Missile-target engagement altitude mismatch
Posted: Tue Oct 14, 2014 9:06 am
I am sure this has been reported before, but a quick look through recent threads didn't show anything.
I suspect this behaviour is persistent, because I have seen it from day one until now, and it might be a GE limitation rather than a bug.
Essentially, missiles kill targets at altitudes considerably different from their own. For example, an AIM-120 shot dives on an aircraft at 40,000 feet. The missile "hits" the target and destroys it at 47,000 feet and change. Time compression is 1:1.
Is the missile really killing the target from 7,000 feet away or is it a matter of the GE simply not reporting its last altitude?
I don't have a savegame. The behaviour is prevalent and easily repeatable.
I suspect this behaviour is persistent, because I have seen it from day one until now, and it might be a GE limitation rather than a bug.
Essentially, missiles kill targets at altitudes considerably different from their own. For example, an AIM-120 shot dives on an aircraft at 40,000 feet. The missile "hits" the target and destroys it at 47,000 feet and change. Time compression is 1:1.
Is the missile really killing the target from 7,000 feet away or is it a matter of the GE simply not reporting its last altitude?
I don't have a savegame. The behaviour is prevalent and easily repeatable.