IFF & interrogation Tutorial - F-15E Strike Eagle
HTML-код
- Опубликовано: 9 мар 2024
- The video is a run through of the Strike's IFF and Interrogator system. It's a very powerful and completely user customizable system to be able to ID both friends and bad guys.
The best part of this is the Radar Coder at Razbam did a superb job of modeling the IFF and interrogation system well above and beyond the DCS norm. Currently other RB modules as well as AI can take advantage of this expanded capability. The "RCG" (Radar Chicken God) has offered to share this IFF baseline for free, NST with other Devs to hopefully work towards a common IFF system among DCS modules to move beyond the "magic" DCS mode 4 IFF.
Hope you guys and gals enjoy it.
Chad Mudhen: *casually locks contacts at 85nm*
I mean.... You can lock the drones at that distance. You used to be able to see ordinance come off of the other jets at that distance in LO and VCTR. She's pretty happy to show contacts at well above 120nm, but your interigation won't reach that far. Strangely the NCTR does, but that could just be early release things.
@@looneyhoonzinc what is the max range for the interrogator?
@@looneyhoonzinc NCTR is radar interrogation by checking the placement and proportions of visible engine intake nacelles. since this is based on radar reflections coming off the fanblades of the intakes, and in comparison of a loaded database of known engine placements on hostile aircraft and taking the range into account one can extrapolate the source of 2 reflection points and the spacing at range calculating which kind of aircraft it is, without it ever tranferring its iff code, hence it is called Non Cooperative Target Recognition, if i remember right. I may be wrong on certain details but this is the general principle. Hope i learned you something :)
Edit: NCTR mode only works in frontal (hot) aspects and during a STT track.
@@s0tze I wanna say it's like 80nm but it depends on aspect atm. If their nose on you can get close to 85-90.
@@gryphus-0171 ah, Indeed I did. Thanks for the pro tip amigo! Guess that's why the switch being flipped on is part of the starting procedures
I'm impressed how deep the systems in this bird are modeled. It's amazing, love it.
this needs to be extended to every module in DCS
Yep, at the moment - its only available among the Razbam modules. But the Dev who coded this has offered to share it to try to make it more universal in DCS. No takers yet but we'll see.
@@notso4966I believe it was mentioned that the Mirage F1 also use the same system razbam made as of the latest version too.
it won't matter until mission planners start utilizing it.
Me as a mission planner: You can mess with the IFF settings?!
Thanks so much! I never would have figured that out.
The NCTR ENABLE switch is off by default. I personally turn it on and set AUTO ID PDT for EID in DCS, which makes it possible to auto identify both the Mode 4 or whatever else and NCTR at the same time.
I think there needs to be a way to set these things that isn't overwriting the Pilot name field. Old missions may not be updateable to do this due to scripts relying on previously inputted name values.. Even new missions we rely on specific pilot/unit names. #FF_M2=1234 #FF_M3=7700 isn't distinctive enough, really, to be all that useful do a designer.
I think ED needs to add this inside the ME on one of those tabs like the datalink tab.
Agree. This is just the only way to work around the current ED system.
Understood! I hope ED might incorporate this IFF system soon!@@notso4966
This is awesome, and really shows how good Galinette is at this stuff. One caveat I found while setting codes up in the editor for a mission, this only works if the AI units are the same coalition as you. E.g. if you set up neutral or red aircraft to Squawk, they won't return anything to the 15 on blue coalition. Was really disappointing to find this out especially since there is no way to turn mode 4 off for AI units. It makes using IFF in conjunction with RoE difficult since players will always know something is blue because of the ED magic mode 4... It's really ridiculous in our combat flight sim that we don't have a proper IFF system and it is up to one guy a 3rd party dev to do some crazy work around to have a function core to aviation as a whole.
Edit:
After further testing. Doing a normal interrogation seems to work, but doing a correct code interrogation does not. And after even further testing this only happens to Mode 3. Mode 2 and Mode 1 can be correct code interrogated across coalitions.
This is awesome. Thank you, I've been having a hard time getting this down to query bogies. Having to rely on NCTR hasn't been ideal to date!
Great video 👍. I had no idea you could set IFF codes in the ME. Need a tutorial on how that works...
Perhaps the initial part would suffice for everyone if it's addressed in the title so that mission makers can find it easily.
Epic, thanks Notso
My hat off to the coder. Great video, as always. Will be great to see this on the SA page, if that is how is called on the 15. This module is certainly setting a STD that the many developers should try to match.
this is fascinating
Thank you, this is very helpful
Sweet, sweet. Cleared to switch.
25:30 lol. these tutorials are great!
Yeah nice but a good Datalink is very much higher on my wanted list for the F15...
Well I'll be damned, IFF is actually interesting
Yes it would be brilliant to have this as the DCS default. Added capability by specific 3rd parties is great to get things moving but as you said the downside of that is, that it puts more pressure on mission makers.
NOTSO❤️
Such an AMAZING tutorial. One of the best ever!
Thanks Notso!
Thanks
Thx 👍👍
This is awesome stuff, but man it just makes me want Datalink even more.
Good stuff! I'd have to watch this a few times to digest the info. I have two questions. in the IFF side, do you know if the reply light is already modeled? In the light test when the toggle is switched on, many places light up but not the REPLY light. I'm not sure how to test this light indicator. I don't know how to set up mission to force another aircraft to interrogate me to observe if my REPLY lights up or not. Second question is about the main warning panel. In DCS Bios it describes most of the lights as white, 2 yellow, 1 green. In the game it is mostly yellow, 2 darker yellow, no white. Can you comment on which is correct? I'm trying to build the panel and don't know in real life if they are mostly white or yellow.
im right on random server like greyflag etc, i just set Mode 4 A in Int and IFF and im good to go ?
great video, this helped me a lot. do you have a video on the intricacies of working against enemy jamming?
No sorry. Not today, OSI. :-)
In the vid, you have assigned mode 3 squawks to several tankers. How did you do that? I looked in the ME and did not find a place where that could be inserted. Thanks, always find your vids extremely informative
Its in the very first couple of min while I'm in the ME screen. Add it under "pilot name".
Notso, will the Eagle get some kind of indication in the hud when you lock a friendly?
Yes. It should already have it, but its not been implemented yet. When added, you will get a circle or diamond flashing for 5 sec inside the TD box if it returns a friendly replay.
Feels like you jumped around a fair bit, there's a few things I'm not entirely clear on. What is each mode used for and how does RoE work?
It seems like certain units set different codes in a given mode to differentiate them, but what mode is used for what?
In the video you use M1 for the package, M3 for different tankers and M2 for wingmen. I take that to mean that M2 is used to designate a specific flight, so why are the tankers then using M3 instead? What are the differences in usage of M2 and M3? Is M3 just used for locating single ship assets like the tanker or AWACS?
Is there a mode that has to be set the same for everybody to identify them as friendly?
I'm assuming that this is M4 as you said it would be set for a given ATO, but could you clarify?
Can M2 and M4 be set on the ground in the kneeboard or only by the mission editor?
Is the RoE always all returns that are all negative or can it change from day to day and be only negative returns in certain modes (regardless of positives in others)?
With my understanding so far, it seems that M1, 2 & 3 are simply telling us about the contact itself and only M4 tells us if it's friend or foe. That's immersive for mil simmers who want to use RoE in their scenarios, but would that not also mean that regular multiplayer servers are just going to continue to use the magic mode 4?
There is NO set way to use the Modes 1-3. Some conflicts used them, some only used Mode 4 and all the rest were turned off. Its up to YOU and/or the Mission maker to use the IFF modes. Typically, Mode 3 is used for civilian airplanes and Mil jets will have Mode 3 turned on in peacetime to ID themselves to ATC. In combat, Mode 3 is usually turned off. Mode 1 is typically assigned to all the players on the ATO while Mode 2 is usually assigned to individual players on the ATO. Mode 3 is usually assigned inflight by ATC. But again, they can all be used in various ways, so there is no hard set standard. I was using both M2 and 3 as examples only for the purposes of the tutorial. There's a 1000 ways to skin that cat.
QUESTION: why not just use TACAN to find the tanker?
I'm guessing here, but I don't think TACAN is encrypted, meaning anyone can home in on it even if they don't know what it is. I doubt TACAN is used during wartime.
@@0BuLLeT01Also others can spoof it, pretending to be your tanker.
PvP Servers are finally going to be safe from clueless players.
You won't be ever safe from clueless players... now even less, since with the new iff system you have to think about it more rather than less 😉
@@felixx75 exactly, realistic simulations need thinking and considerations! War thunder champs will fratricide us all in dcs :)
you are extremely optimistic
Safe? You mean killed by people who have no clue about this system...
"promosm"
I’m gonna need to watch this a few more times to understand. Till then, my apologies to all future friendly fire victims. 🫡