Lose the lock in BVR mode and where's IFF on Su-27 ?

[Majesco]

I fly the Su-27 and sometimes have some problems with radar:

in BVR mode, onboard radar find a target then i lock on target, direct to the target's bearing but suddenly lose the signal of target on the HUD & also on the radar, try to re-scan some times but no way to find him :( . why ???

Does the target turn off his radar or what else ?

 

Another thing relates to online play: in LOFC manual, i find that Sukhoi planes have IFF system - Interrogate Friend or Foe but don't know where it located on the Su-27's control panel. So it makes me difficult when playing online: I don't know who's friend & who's enemy if allied aircrafts were in front of me and enemies turned ECM on because:

 

As we known: on the HUD of Su-27, in BVR mode allied planes indicated by 2 lines and enemies indicated by 1 line. But if enemy turned ECM on, his signal on the HUD will be winked, i'm afraid of giving a mistake lock on a friend if he was in front of me, how to realize which kind of aircraft as in the F-15C's VSD ? ?? :pilotfly:

[Groove]

Lomac Manual, page 25:

 

When the fire control sensor detects a target, it is represented by a small, horizontal row of dots

on the HUD. “Friendly” targets responding to the radar’s identification system (IFF) are represented

by a double row.

 

As you already recognized, there is no other IFF option, besides Situational Awareness :D

[GGTharos]

You have to wait until you burn through the jammer - the jammer will conceal your target's identity.

[159th_Viper]

... But if enemy turned ECM on, his signal on the HUD will be winked, i'm afraid of giving a mistake lock on a friend if he was in front of me, how to realize which kind of aircraft as in the F-15C's VSD ? ?? :pilotfly:

 

Lock him up and transmit over Comms/Team-Chat "raygun": If no "buddy-lock" brevity response, Splash the Contact.

 

Purpose will be two-fold: One, will teach people to use E.C.M. "Sparingly" and two, will teach/encourage the use of Brevity Codes on-line, thus facilitating better Comms :)

[X-man]

After burn through, look at the left side of the HUD. If there's an F on there, it means your locking a Friendly (english HUD)

[mcnab]

I fly the Su-27 and sometimes have some problems with radar:

in BVR mode, onboard radar find a target then i lock on target, direct to the target's bearing but suddenly lose the signal of target on the HUD & also on the radar, try to re-scan some times but no way to find him :( . why ???

Does the target turn off his radar or what else ?

 

Your contact prolly got shot down or went really low, using terrain masking, or turned away ie. made a 180 degree turn..or, it was a UFO.

[Aeroscout]

After burn through, look at the left side of the HUD. If there's an F on there, it means your locking a Friendly (english HUD)

 

I had an issue with this. I was flying the Su-27 with English HUD. A person was flying towards me in a valley. I locked him up in BORE, with no "F" on HUD, but it was a TK (My first one ever :doh::cry:)

 

Well, a little wile later, I was RTB, and another person was coming straight at me at 12 o'clock. I cocked him up in BORE, no"F." I checked it BVR any way and it was friendly... is this a bug? or does it not work head on?

 

BTW, i did see the F in other situations, but not head on.

 

I feel so bad about this mistake, and I want to know if it was my mistake, or the computers. (If it was my mistake, I'll take full responsibility)

[Force_Feedback]

You need radar for IFF, EOS is passive.

[Ironhand]

I had an issue with this. I was flying the Su-27 with English HUD. A person was flying towards me in a valley. I locked him up in BORE, with no "F" on HUD, but it was a TK (My first one ever :doh::cry:)

 

Well, a little wile later, I was RTB, and another person was coming straight at me at 12 o'clock. I cocked him up in BORE, no"F." I checked it BVR any way and it was friendly... is this a bug? or does it not work head on?

 

To amplify what FF has stated...

 

Partly, I think you have a misunderstanding of how the A2A system is designed to work. The system defaults are set for stealth. When you first enter any A2A mode, radar is not turned on. In the case of BVR you have to physically set the radar to: ON. In the case of the WVR modes (VS, BORE, and HELMET), the system defaults to the IRST sensor (EOS). Since heat signatures do not provide IFF information, you have to actively engage the radar for IFF. My guess is that, when you entered BORE, only the IRST sensor was active. Turning on your radar would have solved your IFF problem. I've never had difficulty with IFF--head on or whatever.

 

Rich

[Aeroscout]

Thanks so much! That would have saved me a lot of embarrassment.

 

Thanks, It's my fault then.