Joni Posted December 8, 2020 Posted December 8, 2020 When interrogating a neutral coalition contact with an AWACS present it shows ambiguous both in top and bottom HAFU (correct). After a while it turns into a hostile top HAFU and bottom ambiguous HAFU (incorrect) when it should remain double ambiguous. Track attached. neutral iff bug.trk Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5
Joni Posted December 8, 2020 Author Posted December 8, 2020 The bug happens when the neutral contact is set as L&S. If a different one is set as L&S then it goes back to double ambiguous brackets. Track attached. neutral iff bug2.trk Please don't hate me for the spam, I just discovered that the bug exists for anything that is set as L&S and doesn't reply to mode4. No matter if is neutral or enemy, it will always show enemy red chevron HAFU if set as L&S. Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5
Joni Posted December 9, 2020 Author Posted December 9, 2020 I don't know if it helps, but I saw that turning NCTR off solves the issue, which is strange since the tests I conducted were cold aspect (in track attached as well). What also draw my attention was the fact that the NCTR print isn't working, it does't show the type in SA page. So NCTR is actually contributing to the IFF (during cold aspects too) but it isn't showing what type of print it gets. It would also be good if NCTR didn't recognize a passenger aircraft as hostile. Thanks. neutral iff bug2 nctr.trk Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5
Harker Posted December 9, 2020 Posted December 9, 2020 See this: tl;dr the NCTR part of the ROE matrix is bugged since the beginning and doesn't need STT. I don't know if this has anything to do with NCTR marking neutral coalition aircraft as hostile. It shouldn't do that, anyway. Seems like the NCTR part needs some work, with respect to which aircraft it recognizes as hostile, now it magically knows. I tested with a Blue Hornet vs a Red and then a Neutral Hornet. Both the Red and the Neutral F-18s were flagged as hostile by NCTR. A Mode 4 IFF interrogation gets no reply, so they're marked as Hostile. The current ROE matrix without donors is supposed to be "No/Wrong Mode 4 IFF response + NCTR hostile print = Hostile". How does an F-18 get marked as hostile by NCTR, when it could very well be a friendly F-18 with its IFF transponder off? There should be aircraft that are marked as hostile by NCTR and aircraft that are not, regardless of coalition, at the very least other Hornets. 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
Joni Posted December 9, 2020 Author Posted December 9, 2020 (edited) 17 minutes ago, Harker said: Seems like the NCTR part needs some work, with respect to which aircraft it recognizes as hostile, now it magically knows. I tested with a Blue Hornet vs a Red and then a Neutral Hornet. Both the Red and the Neutral F-18s were flagged as hostile by NCTR. A Mode 4 IFF interrogation gets no reply, so they're marked as Hostile. The current ROE matrix without donors is supposed to be "No/Wrong Mode 4 IFF response + NCTR hostile print = Hostile". How does an F-18 get marked as hostile by NCTR, when it could very well be a friendly F-18 with its IFF transponder off? There should be aircraft that are marked as hostile by NCTR and aircraft that are not, regardless of coalition, at the very least other Hornets. I'm ok with all of this, otherwise it would not work nicely, I think ED made the right call on that aspect. NCTR with STT shows the correct type of print picked up in SA page, with no STT it just contributes to the ROE picture but doesn't show print. This needs to be corrected. On top of these, I think the first thing to address is the fact that NCTR makes a neutral coalition hostile. Then they can work on the broken part of NCTR itself (angle, L&S thing, etc.) This is my opinion though, I just hope this thread was useful at least. Thanks for the other thread link, I didn't find it before. Thanks. Edited December 9, 2020 by JohnnyQ Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5
ED Team BIGNEWY Posted December 9, 2020 ED Team Posted December 9, 2020 Hi, this is covered in another report, AWACS are reporting Neutral aircraft and will ID them as hostile when declare is used on NCTR Thanks Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Joni Posted December 9, 2020 Author Posted December 9, 2020 Thanks. On FC3 aircrafts, neutral are showing as enemies. No NCTR or awacs. Maybe it helps. Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5
Recommended Posts