IFF in multiplayer

[diavolaccio]

Hello, i never experienced any issue with IFF in single player, but I'm having some problems in multiplayer (104th server): AWACS is spamming BRA of enemy and my area is clear, i got several contacts on screen (40km preset) from 10 to 30 km to my position , then i decide to IFF interrogate them and one of them is marked not friendly , interrogate again , still not friendly ... so I SST lock him and prepare the 530s and took him down only to learn from the message that it was a friendly F15... during the next hour i had same problem several times (i hold fire instead:P) with contacts that should be blue to me marked neutral/hostile .. is that a common thing in m2k? Afaik IFF in DCS is pretty simple binary thing, so if properly used (nosewheel/IFF button and IFF rotary on left side panel to the rightmost position) should always work, isnt it?

[myHelljumper]

The mirage uses nautical miles not kilometers, are you sure you are talking about km ? :)

 

I have no problems with IFF in multiplayer, it is always right. you locked the right guy ?

 

You should provide us a track or a tacview because I can't see what the problem could be right now.

Edited May 24, 2017 by myHelljumper

[QuiGon]

Afaik IFF in DCS is pretty simple binary thing, so if properly used (nosewheel/IFF button and IFF rotary on left side panel to the rightmost position) should always work, isnt it?

 

I haven't flown much lately, but IIRC it wasn't the rightmost position for the rotary, but the second rightmost position (just one click to the right from the default position). I can be wrong though, but it might be worth a try.

[myHelljumper]

I haven't flown much lately, but IIRC it wasn't the rightmost position for the rotary, but the second rightmost position (just one click to the right from the default position). I can be wrong though, but it might be worth a try.

 

IIRC it does not matter, the two positions do the same.

[Chrinik]

It´s also not on the left side panel, it´s on the right, right above the counter meassure program selector.

[Pheonix0869]

I had a situation once where i locked a confirmed enemy and then sent a fox 1. A friendly, in a most unfortunate fashion, trying to saddle said enemy, flew into the flight path of the missile and ended up being destroyed. I only learned of this by replaying the track and then reviewing the tacview of the replay. Of course, the guy wasn't on comms either, which frankly helps immensely with confirming FoF. I believe, irl pilots are not allowed to rely on IFF alone, unless there is some verbal confirmation that their target is a bandit, and not just a bogey. Tacview is free and helps understand mistakes made... and further more, understand wacky 1/1000000 things that could have gone wrong. Being on comms and communicating with other pilots in the area provides better SA in order to be more certain your target is a hostile.

[Flyingsix]

Hello, i never experienced any issue with IFF in single player, but I'm having some problems in multiplayer (104th server): AWACS is spamming BRA of enemy and my area is clear, i got several contacts on screen (40km preset) from 10 to 30 km to my position , then i decide to IFF interrogate them and one of them is marked not friendly , interrogate again , still not friendly ... so I SST lock him and prepare the 530s and took him down only to learn from the message that it was a friendly F15... during the next hour i had same problem several times (i hold fire instead:P) with contacts that should be blue to me marked neutral/hostile .. is that a common thing in m2k? Afaik IFF in DCS is pretty simple binary thing, so if properly used (nosewheel/IFF button and IFF rotary on left side panel to the rightmost position) should always work, isnt it?

 

I had exactly the same situation yesterday. Two times. After the teamkills I got kicked (also @104th).

 

The first kill was a non-jamming contact and i choose the “standard” lock-on procedure via RWS->TWS->STT. The IFF panel was set to CONT.

The second kill was a jamming contact. I’m not sure if the jamming blips showing diamonds if it’s a friendly guy. Maybe you have an answer for that. But nevertheless I followed the sporadically trace (dashed trace-line) on the VTB and switched to horizontal close combat mode. After some minutes of search I got a track. I IFF’ed him and there was no diamond and no “A” in the HUD. Shoot him down and got kicked.

 

Maybe it’s a misinterpretation or it is a bug. Don’t know. But I will try to keep an eye on it with tacview.

Edited January 6, 2018 by Flyingsix

[jojo]

I had exactly the same situation yesterday. Two times. After the teamkills I got kicked (also @104th).

 

The first kill was a non-jamming contact and i choose the “standard” lock-on procedure via RWS->TWS->STT. The IFF panel was set to CONT.

The second kill was a jamming contact. I’m not sure if the jamming blips showing diamonds if it’s a friendly guy. Maybe you have an answer for that. But nevertheless I followed the sporadically trace (dashed trace-line) on the VTT and switched to horizontal close combat mode. After some minutes of search I got a track. I IFF’ed him and there was no diamond and no “A” in the HUD. Shoot him down and got kicked.

 

Maybe it’s a misinterpretation or it is a bug. Don’t know. But I will try to keep an eye on it with tacview.

 

Are you sure you performed correctly the interrogation ? (you have dashed line at the top of the VTB during interrogation: under the scan zone line).

[Flyingsix]

Are you sure you performed correctly the interrogation ? (you have dashed line at the top of the VTB during interrogation: under the scan zone line).

 

In my opinion, yes. But I suspect we're talking about two different things. If I understood your post in the right manner, then you're talking about the interrogation line (a bent line on top of the VTB, as you described it) and that I must not confuse it with any other lines.

 

I mean the dashed straight line which appears sporadically, when the radar is scanning against a jamming aircraft and sometimes getting an echo strong enough to display a trackable contact on the screen. Then you can see a straight dashed line from the origin to the contact for some seconds. This line also moves in relationship to your actual longitudinal direction. If this straight line has an other function, than please correct me :doh:

 

But to confirm the correct usage of IFF...

 

1) pressing the interrogation button (NWS-Button)

2) looking at the VTB and see the bent line in the top (confirmation that actually the interrogation is running)

3) checking for diamond- or non-diamond-aircrafts

 

and the last point, if I've actually locked on a target...

4) checking for an blinking "A" on the HUD (A = friendly)

 

Greetz

[jojo]

In my opinion, yes. But I suspect we're talking about two different things. If I understood your post in the right manner, then you're talking about the interrogation line (a bent line on top of the VTB, as you described it) and that I must not confuse it with any other lines.

 

I mean the dashed straight line which appears sporadically, when the radar is scanning against a jamming aircraft and sometimes getting an echo strong enough to display a trackable contact on the screen. Then you can see a straight dashed line from the origin to the contact for some seconds. This line also moves in relationship to your actual longitudinal direction. If this straight line has an other function, than please correct me :doh:

 

But to confirm the correct usage of IFF...

 

1) pressing the interrogation button (NWS-Button)

2) looking at the VTB and see the bent line in the top (confirmation that actually the interrogation is running)

3) checking for diamond- or non-diamond-aircrafts

 

and the last point, if I've actually locked on a target...

4) checking for an blinking "A" on the HUD (A = friendly)

 

Greetz

 

You got it right, that's what I meant.

 

To do a "blank" interrogation in scan during "fence in" (check dashed line at the top of VTB) is a good practice. It's easy to forget to turn on IIFF, and during the fight you won't have the time to check if IIFF is actually running or not.

It does worth trying in SP with IA and in MP with your buddies to confirm if the case only happens in MP or in SP too.

 

So far no problem for me in SP.

[TXGrunt]

Same issue here... I was kicked the other day from the 104th server due to friendly fire twice! The RWR was showing 29 (Mig 29) I saw him on radar, double checked IFF and interrogated. He came up as non-friendly via the HUD as there was not an "A" indicated and in the Radar screen as there was not a diamond present. I also confirmed that I was interrogating by the dashed lines at the top. I locked him up and it was a friendly F15...

 

This happened twice on the server before being kicked.

Edited January 10, 2018 by TXGrunt

[Azrayen]

Would anybody provide a track?

I guess that would help Razbam to reproduce first, then understand and finally fix this (if needed).

 

I never encountered this one and am currently unable to fly DCS.

[Raven (Elysian Angel)]

On our server the only people having issues with friendly fire are the ones that did interrogate but didn't turn on the IFF system (they didn't have the power switch set to CONT).

 

I have never had problems with it myself, as far as I remember.

[Flyingsix]

Would anybody provide a track?

I guess that would help Razbam to reproduce first, then understand and finally fix this (if needed).

 

I never encountered this one and am currently unable to fly DCS.

 

Presently Tacview is not working on my system with its actual version. Have to wait for the fix. Then I will make a track.

[jojo]

Presently Tacview is not working on my system with its actual version. Have to wait for the fix. Then I will make a track.

 

I think Azrayen was talking about DCS track.

 

TacView is for you/ us to understand the tactical situation.

 

DCS track is needed by Razbam/ ED to check what events happened within DCS World to track bugs.

[Flyingsix]

I think Azrayen was talking about DCS track.

 

TacView is for you/ us to understand the tactical situation.

 

DCS track is needed by Razbam/ ED to check what events happened within DCS World to track bugs.

Oh, I see! :doh:

[D4n]

What I always do is check if there are double green bars on the side of locked contact on radar screen... (friendly)