Amraam and EOS bug?

[Battle_Rattle]

Apologies before I begin but I searched and couldn't find topics on these two events...

 

I was online flying a CAP and was downed by an AIM-120. There was no warning at all before i was struck... It's my understanding that an AIM-120 will always go active off the rail? Was wondering why I recieved no warning.

 

Also, I was trailing a team mate and was matching his speed using the EOS. He dipped below a mountain ridge for about 10 seconds and the EOS stayed locked on him. This actually happened several times as I followed him. I noticed that when he went below the ridges the radar and "F" HUD symbols would begin flickering.

 

Any experience with these problems?

[Gazehound]

You wont get much warning if the AMRAAM was fired in TWS mode, or you were banked - the RWR does not work perfectly over 30deg. ECM also interferes with launch wanings) Also, is it possible that a bandit saw you WVR and fired point blank?

The F means that your radar was having to come on and track the freindly. Do not knowingly lock up freindlies in eos or radar as they cannot properly sense other threats if your radar comes on to compensate. Also they may lose a lot of altitude/energy trying to find whats locking them up.

[Battle_Rattle]

Thanks Gazehound

 

A couple of things:

 

1) The Radar automatically turns on to supplement a wavering EOS signal? That's new to 1.1 and quite odd if I may say so. At any rate my friend was fully tracked through a mountain.

 

 

2) I was flying straight and level in the time leading up to the amraam hit. Must have been ECM of someones interfering with the warning (i cant honestly remember if mine was on.)

 

 

Really enjoying 1.1 ....

[Weta43]

Even if you were level - if you are fired upon from from outside of the 30 (?) degee "doughnut" that the RWR can see, you won't get a warning, so if the missile was coming from above or below you wouldn't get a warning.