Missile-target engagement altitude mismatch

[CV32]

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.

[mikmykWS]

Thanks for reporting. We'll follow up.

Mike

[Michal Pielaszkiewicz]

same with F-15 ASAT...

[AFIntel]

ORIGINAL: mikmyk

Thanks for reporting. We'll follow up.

Mike

You edited your first response! But it was so funny! [:D][:D]

[mikmykWS]

Yes.

I will be nice.
I will be nice.
I will be nice.
I will be nice

[:)]