GrEaSeLiTeNiN Posted April 5, 2019 Author Posted April 5, 2019 1 Yes, it's the HAFU being a triangle and normally red. 2 No, if you have an F/F or SURV donor already saying it's hostile. 3 You need NCTR enabled on the RDR ATTK format and you need to be nose on nose or nose on tail about 30 degrees; the radar needs to be able to get a good look at the engine fanblades Thanks for the replies. Just to clarify: 1,2. If the HAFU symbol is yellow and has a "table" on the top half but a "V" on the bottom half, it is already a hostile. Why do we need to further interrogate and depress SSS over it to turn it red? Is that necessary? See video - 3. I did have NCTR on and the Su27 was facing me and very close. But still no name ID on SA page bottom right. Thanks! AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 64GB G.SKILL TRIDENT Z4 neo DDR4 3600Mhz | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4 TM Warthog HOTAS | TrackIR 5 | Windows 10 Home x64 | My HOTAS Profiles
Jak525 Posted April 5, 2019 Posted April 5, 2019 (edited) Thanks for the replies. Just to clarify: 1,2. If the HAFU symbol is yellow and has a "table" on the top half but a "V" on the bottom half, it is already a hostile. Why do we need to further interrogate and depress SSS over it to turn it red? Is that necessary? See video - 3. I did have NCTR on and the Su27 was facing me and very close. But still no name ID on SA page bottom right. Thanks! The bottom is a what a donor sees it as. The top is what your aircraft designates it as and what the color is from. It's not "necessary" - the HAFUs are for pilot situational awareness, they don't tell the plane what to do or anything. That's interesting. With NCTR checked and you being in an STT lock it should work. Edited April 5, 2019 by Jak525
Ramsay Posted April 5, 2019 Posted April 5, 2019 Thanks for the replies. Just to clarify: 1,2. If the HAFU symbol is yellow and has a "table" on the top half but a "V" on the bottom half, it is already a hostile. It has been identified by a third party (AWACS or other aircraft) as hostile. Why do we need to further interrogate and depress SSS over it to turn it red? You still need to confirm the target is a hostile before opening fire i.e. via IFF, NCTR or visually Is that necessary? See video - ATM DCS's ROE are hard coded, you don't *need* to follow them but if you don't, you'll have the 'unknown' square, rather than 'hostile' diamond in the HUD to remind you. 3. I did have NCTR on and the Su27 was facing me and very close. But still no name ID on SA page bottom right. IIRC NCTR requires a STT lock, if you visually ID the hostile, you don't need IFF. i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
GrEaSeLiTeNiN Posted April 5, 2019 Author Posted April 5, 2019 IIRC NCTR requires a STT lock, if you visually ID the hostile, you don't need IFF. I did have it STT locked with NCTR and the Su27 was in front of me already but still no ID name in SA page. Not sure why it didn't work. AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 64GB G.SKILL TRIDENT Z4 neo DDR4 3600Mhz | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4 TM Warthog HOTAS | TrackIR 5 | Windows 10 Home x64 | My HOTAS Profiles
Jak525 Posted April 5, 2019 Posted April 5, 2019 I did have it STT locked with NCTR and the Su27 was in front of me already but still no ID name in SA page. Not sure why it didn't work. You did cursor over the target on the SA page right? You won't show any info without that. But if it did show as unknown then your NCTR just didn't work. Might've just been the angle or something. Test it again.
GrEaSeLiTeNiN Posted April 5, 2019 Author Posted April 5, 2019 You did cursor over the target on the SA page right? You won't show any info without that. But if it did show as unknown then your NCTR just didn't work. Might've just been the angle or something. Test it again. Yes cursor was over target on SA. Will try again. Probably an angle issue. AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 64GB G.SKILL TRIDENT Z4 neo DDR4 3600Mhz | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4 TM Warthog HOTAS | TrackIR 5 | Windows 10 Home x64 | My HOTAS Profiles
QuiGon Posted April 5, 2019 Posted April 5, 2019 Yes, DCS handles this correctly. When interrogating on the SA page, you can only interrogate tracks with the top-half of the HAFU showing, meaning tracks that are detected by your own radar. Alright then, thanks! :thumbup: Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
Rainmaker Posted April 5, 2019 Posted April 5, 2019 I did have it STT locked with NCTR and the Su27 was in front of me already but still no ID name in SA page. Not sure why it didn't work. Pretty sure this is already reported in the bug forum as being an issue...track hostile with no print ID on SA page.
Banzaiib Posted April 5, 2019 Posted April 5, 2019 LTWS has a much larger scan volume... so not useless.
Khamul Posted April 5, 2019 Posted April 5, 2019 quick question, please: on the RDR page with LWTS if I lock with TDC multiple tgts how do I clean/undesignate them in case? If I press the undesignate button nothing happened and the tgts keep locked. TU NE CEDE MALIS SED CONTRA AUDENTIOR ITO _________________________________________ Asrock Fatal1ty Gaming K6+, i5-6600K, 32 GB DDR4, Asus GTX 1070 Strix, SSD 500GB, HDD 1TB, Win 10 x64, Monitor LG Ultrawide 29UM67, Soundblaster Z+Sennheiser Game One, HOTAS Warthog, TFRP Thrustmaster, TrackIr
Ramsay Posted April 5, 2019 Posted April 5, 2019 quick question, please: on the RDR page with LWTS if I lock with TDC multiple tgts how do I clean/undesignate them in case? If I press the undesignate button nothing happened and the tgts keep locked. The Attack Radar MFD reset button (PB14), resets L&S and DT2 designations. i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
GrEaSeLiTeNiN Posted April 6, 2019 Author Posted April 6, 2019 (edited) quick question, please: on the RDR page with LWTS if I lock with TDC multiple tgts how do I clean/undesignate them in case? If I press the undesignate button nothing happened and the tgts keep locked. I believe Sensor Control has to be on Radar page and you hold down Undesignate for about a sec? Update/Correction: On the Radar page, It seems undesignate only unlocks completely an STT that was obtained by AACQ. In the case of an STT obtained by two TDC depresses, it only removes the STT but there is still the soft lock that cannot be removed except by Reset button (PB14). Edited April 6, 2019 by GrEaSeLiTeNiN AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 64GB G.SKILL TRIDENT Z4 neo DDR4 3600Mhz | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4 TM Warthog HOTAS | TrackIR 5 | Windows 10 Home x64 | My HOTAS Profiles
Khamul Posted April 6, 2019 Posted April 6, 2019 I believe Sensor Control has to be on Radar page and you hold down Undesignate for about a sec? Update/Correction: On the Radar page, It seems undesignate only unlocks completely an STT that was obtained by AACQ. In the case of an STT obtained by two TDC depresses, it only removes the STT but there is still the soft lock that cannot be removed except by Reset button (PB14). Great, thanks! I'll give it a try TU NE CEDE MALIS SED CONTRA AUDENTIOR ITO _________________________________________ Asrock Fatal1ty Gaming K6+, i5-6600K, 32 GB DDR4, Asus GTX 1070 Strix, SSD 500GB, HDD 1TB, Win 10 x64, Monitor LG Ultrawide 29UM67, Soundblaster Z+Sennheiser Game One, HOTAS Warthog, TFRP Thrustmaster, TrackIr
GrEaSeLiTeNiN Posted April 6, 2019 Author Posted April 6, 2019 (edited) Why is the HAFU tail pointing down in the SA page but pointing up in the Radar page? Edited April 6, 2019 by GrEaSeLiTeNiN AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 64GB G.SKILL TRIDENT Z4 neo DDR4 3600Mhz | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4 TM Warthog HOTAS | TrackIR 5 | Windows 10 Home x64 | My HOTAS Profiles
Fisherman82 Posted April 9, 2019 Posted April 9, 2019 Is LTWS on needed to display contacts from donors on the SA page? I would think it should not but I dont seem to get them with it off. I would like to use LTWS off until I learn the basics of the radar better but still have AWACS give me the big picture on the SA page to give me better situational awareness Skickat från min D5503 via Tapatalk
QuiGon Posted April 9, 2019 Posted April 9, 2019 Is LTWS on needed to display contacts from donors on the SA page? I would think it should not but I dont seem to get them with it off. I would like to use LTWS off until I learn the basics of the radar better but still have AWACS give me the big picture on the SA page to give me better situational awareness Skickat från min D5503 via Tapatalk It's not needed and D/L works fine without LTWS for me. Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
blkspade Posted April 10, 2019 Posted April 10, 2019 Thanks for the replies. Just to clarify: 1,2. If the HAFU symbol is yellow and has a "table" on the top half but a "V" on the bottom half, it is already a hostile. Why do we need to further interrogate and depress SSS over it to turn it red? Is that necessary? See video - The key reason you should absolutely be interrogating still, is that the DL has a delay, and the radar isn't absolutely precise about the contact you lock up. If for some reason you have a friendly merged with that contact that isn't on the DL network, and possibly in a blind spot of donors/AWACS, you could end up firing on said friendly. I have had the F-18 radar jump from a know hostile to friendly that crossed the LOS that I only knew was even there due to being on comms. http://104thphoenix.com/
GrEaSeLiTeNiN Posted April 11, 2019 Author Posted April 11, 2019 The key reason you should absolutely be interrogating still, is that the DL has a delay, and the radar isn't absolutely precise about the contact you lock up. If for some reason you have a friendly merged with that contact that isn't on the DL network, and possibly in a blind spot of donors/AWACS, you could end up firing on said friendly. I have had the F-18 radar jump from a know hostile to friendly that crossed the LOS that I only knew was even there due to being on comms. I see thanks AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 64GB G.SKILL TRIDENT Z4 neo DDR4 3600Mhz | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4 TM Warthog HOTAS | TrackIR 5 | Windows 10 Home x64 | My HOTAS Profiles
Recommended Posts