GGTharos Posted January 16, 2019 Posted January 16, 2019 The IFF system in the hornet right now only works if a target is inside the HUD. This particular IFF system uses an electronically steered beam in order to cover almost the full radar AZ. It is this specific system, and the relevant information is listed: https://www.baesystems.com/en/download-en/20180518194500/1434555671810.pdf What happens: IFF only works (identifies) contacts in front of the aircraft, well inside the HuD What should happen: IFF should identify aircraft throughout its entire AZ/EL coverage (Note: I do realize there are complexities with it that might not be modeled right away, but the AZ/EL coverage is a big deal and should be easy enough to make work). [sIGPIC][/sIGPIC] Reminder: SAM = Speed Bump :D I used to play flight sims like you, but then I took a slammer to the knee - Yoda
Harker Posted January 16, 2019 Posted January 16, 2019 Isn't that the case for a while now? Did something change? The Hornet's IFF is limited right now and only works for contacts inside the HUD's FOV, but it's definitely WIP. Of course, you're right about how it should work. The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. 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
GGTharos Posted January 16, 2019 Author Posted January 16, 2019 I am aware that it is WIP, I just believe (perhaps incorrectly) that exanding the AZ/EL is literally as simple as tweaking a couple of parameters in a lua file, since this is how such things have been traditionally defined. There's no reason to keep this sort of limitation basically. I'm not asking for anything extra/fancy like a contact ID 'sticking' to the contact after interrogation when it leaves the IFF limits etc. [sIGPIC][/sIGPIC] Reminder: SAM = Speed Bump :D I used to play flight sims like you, but then I took a slammer to the knee - Yoda
Recommended Posts