Jump to content

[NO TRACK OR VIDEO INCLUDED] IFF issue


ravenzino

Recommended Posts

I'm sort of ok with IFF for all the time until tonight.

 

I was on Hoggit GAW server, as I always recently. It was all ok until I get into approx. 30nm to Beslan where there're a lot of ground units and a handful of enemy fighters not far away.

So when I'm heading towards Beslan, I can't IFF any contacts on my radar page: move cursor upon, depress the button on my HOTAS to IFF, and the contact remains yellow. Tried to IFF another targets, yellow the same. Tried to lock one of those targets, yellow the same.

I tried almost all the some 6-8 contacts within 40nm, none of the attempts gave me either friendly or foe response, all of them remain yellow... yes, at that point of time, I was staring at a radar page that's full of yellow marks...

 

It scared me, so I turned away. When I was heading opposite of my original direction, there came in new contacts on my radar page, and then the IFF started to work properly...

 

I turned in again, IFF works ok at start, but not for long. When I was pursuing a bandit, an unknown contact popped up at my 10 at about 10nm. I try to IFF, it remains yellow... so I switch to F10 map, and realised it has to be a foe. Right when I switched back to F1 view, I saw a missile flying towards me from it at close proximity...

 

Well, next thing I know is I'm staring at my broken hornet with my broken heart...

 

Could it be a bug?

 

 

Edit: Please see the following link for track file:

https://drive.google.com/file/d/1R5Wm_ps1sTwH2GB4wamz8Uq4K46ILFOO/view?usp=sharing


Edited by ravenzino

i9-9900K, G.Skill 3200 32GB RAM, AORUS Z390 Pro Wifi, Gigabyte Windforce RTX 2080 Ti, Samsung 960 Pro NVMe 512G + 860 Pro 1T, TM Warthog HOTAS, VKB T-Rudder, Samsung O+

F/A-18C, F-16C, A-10C, UH-1, AV-8B, F-14, JF-17, FC3, SA342 Gazelle, L-39, KA-50, CEII, Supercarrier Preordered. (Almost abandoned: CA - VR support please?)

PG, NTTR

Link to comment
Share on other sites

Did you perhaps fly out of range of AWACS or some other link16 source? Enemy (red) verification requires two sources of info, which could be your own NCTR and link 16, but that would require you to be close and at the proper aspect to the target. Most commonly, an AWACS best serves as that second data source.

Link to comment
Share on other sites

To add to this, in this game at least you can assume yellow is enemy, because friendly identification only requires one source, and there are no neutral targets in the game today. Someone correct me there if I'm wrong.

Link to comment
Share on other sites

To add to this, in this game at least you can assume yellow is enemy, because friendly identification only requires one source, and there are no neutral targets in the game today. Someone correct me there if I'm wrong.

 

That's correct, yellow after IFF button means enemy in game.

Or their/your IFF not functioning/off

Link to comment
Share on other sites

Link to track file added

i9-9900K, G.Skill 3200 32GB RAM, AORUS Z390 Pro Wifi, Gigabyte Windforce RTX 2080 Ti, Samsung 960 Pro NVMe 512G + 860 Pro 1T, TM Warthog HOTAS, VKB T-Rudder, Samsung O+

F/A-18C, F-16C, A-10C, UH-1, AV-8B, F-14, JF-17, FC3, SA342 Gazelle, L-39, KA-50, CEII, Supercarrier Preordered. (Almost abandoned: CA - VR support please?)

PG, NTTR

Link to comment
Share on other sites

Did you perhaps fly out of range of AWACS or some other link16 source? Enemy (red) verification requires two sources of info, which could be your own NCTR and link 16, but that would require you to be close and at the proper aspect to the target. Most commonly, an AWACS best serves as that second data source.

 

Hmmm, very good point......

Though I thought it could be quite rare to encounter such out-of-range situation, it was indeed about 210nm away from AWACS...

 

IIRC, there were multiple friendly fighters (F/A-18 and/or F-14) nearby closer to those bandits, so theoretically they should be used as the second source by my IFF? I guess this didn't work well might because the targets I tried to IFF were also unknown to them?

i9-9900K, G.Skill 3200 32GB RAM, AORUS Z390 Pro Wifi, Gigabyte Windforce RTX 2080 Ti, Samsung 960 Pro NVMe 512G + 860 Pro 1T, TM Warthog HOTAS, VKB T-Rudder, Samsung O+

F/A-18C, F-16C, A-10C, UH-1, AV-8B, F-14, JF-17, FC3, SA342 Gazelle, L-39, KA-50, CEII, Supercarrier Preordered. (Almost abandoned: CA - VR support please?)

PG, NTTR

Link to comment
Share on other sites

That's correct, yellow after IFF button means enemy in game.

Or their/your IFF not functioning/off

 

The latter case is what I fear of... I don't want to make a team kill and get kicked because their IFF is not on or properly functioning...

 

... or maybe that's not my problem?:music_whistling:

i9-9900K, G.Skill 3200 32GB RAM, AORUS Z390 Pro Wifi, Gigabyte Windforce RTX 2080 Ti, Samsung 960 Pro NVMe 512G + 860 Pro 1T, TM Warthog HOTAS, VKB T-Rudder, Samsung O+

F/A-18C, F-16C, A-10C, UH-1, AV-8B, F-14, JF-17, FC3, SA342 Gazelle, L-39, KA-50, CEII, Supercarrier Preordered. (Almost abandoned: CA - VR support please?)

PG, NTTR

Link to comment
Share on other sites

The latter case is what I fear of... I don't want to make a team kill and get kicked because their IFF is not on or properly functioning...

 

 

 

... or maybe that's not my problem?:music_whistling:

Well, it's their responsibility to configure their IFF properly and it's your responsibility to have a positive target ID before you fire.

IRL, a fighter wouldn't extend beyond AWACS coverage or at least without first setting up a local surveillance network by working with other friendly platforms nearby. The problem is that communication with other players is difficult at best, in DCS.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Link to comment
Share on other sites

I was flying with you during that mission phase(UZI 31). We were out of range of the AWACS datalink so we had to rely on our internal IFF and fighter to fighter DL (Which is limited in what they can contribute like you are). No mode 4 response means unknown and friendlies were giving a positive mode 4 response straight away. Getting a bit closer and at a good aspect I was getting NCTR sniffs that were accurate. What's a little confusing is unknown or friendly is the same square box in the HUD so you have to sneak a glance at your radar to check the symbology there.

 

Luckily we had a human GCI for a period that was great for declares.


Edited by Zomba

I don't test for bugs, but when I do I do it in production.

Link to comment
Share on other sites

I was flying with you during that mission phase(UZI 31). We were out of range of the AWACS datalink so we had to rely on our internal IFF and fighter to fighter DL (Which is limited in what they can contribute like you are). No mode 4 response means unknown and friendlies were giving a positive mode 4 response straight away. Getting a bit closer and at a good aspect I was getting NCTR sniffs that were accurate. What's a little confusing is unknown or friendly is the same square box in the HUD so you have to sneak a glance at your radar to check the symbology there.

 

Luckily we had a human GCI for a period that was great for declares.

 

Hey buddy, thanks for the confirmation! Didn't expect myself to be on that weird spot... Guess I shall start to learn to work without AI AWACS...

i9-9900K, G.Skill 3200 32GB RAM, AORUS Z390 Pro Wifi, Gigabyte Windforce RTX 2080 Ti, Samsung 960 Pro NVMe 512G + 860 Pro 1T, TM Warthog HOTAS, VKB T-Rudder, Samsung O+

F/A-18C, F-16C, A-10C, UH-1, AV-8B, F-14, JF-17, FC3, SA342 Gazelle, L-39, KA-50, CEII, Supercarrier Preordered. (Almost abandoned: CA - VR support please?)

PG, NTTR

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...