0xDEADBEEF Posted December 2, 2015 Posted December 2, 2015 Since I've only been on the 27 for a couple of months, i waited with posting this. I've just had a sortie that made me very certain about my observation. Sometimes switching on the Radar while having a lock on IRST will incorrectly show a friendly as Enemy (A in the HUD instead of AFR). I've had it a couple of times since the last 1.5 Update, but always accounted it to user error (Teamkills are really embarassing). Right now I've been flying a sortie on Nevada, I only had friendlies around which I confirmed on the Radar. Then a red F15 popped up on my 12 from below within gunrange, I EO-locked it, switched on radar and my Jaw dropped because the A stood in place missing the FR. I switched off Radar off and on again to confirm, still a solid A. So I foxed him. Then was still very unsure why he was enemy, switched on radar again and see, theres the missing FR, just after I foxed, I just killed a friendly from behind. Earlier today I got teamkilled by another red Su27 who as well claimed that he was 100% sure he used Radar to check and it said I'm hostile. I don't know if this is another realism thing (if it is, be so kind and let us know) or as I suspect a bug.
Redacuragsr Posted December 2, 2015 Posted December 2, 2015 Yea I can confirm, I had that happen too a couple of times.
karambiatos Posted December 2, 2015 Posted December 2, 2015 Did the target have ECM on did you have burn through? A 1000 flights, a 1000 crashes, perfect record. =&arrFilter_pf[gameversion]=&arrFilter_pf[filelang]=&arrFilter_pf[aircraft]=&arrFilter_DATE_CREATE_1_DAYS_TO_BACK=&sort_by_order=TIMESTAMP_X_DESC"] Check out my random mods and things
sLYFa Posted December 2, 2015 Posted December 2, 2015 Then a red F15 popped up on my 12 from below within gunrange, I think thats close enough to burn through... i5-8600k @4.9Ghz, 2080ti , 32GB@2666Mhz, 512GB SSD
Frostie Posted December 3, 2015 Posted December 3, 2015 Make sure you don't IFF in gunmode, IFF has never worked in gunmode. "[51☭] FROSTIE" #55 'Red 5'. Lord Flashheart 51st PVO "Bisons" - 100 KIAP Regiment Fastest MiG pilot in the world - TCR'10 https://100kiap.org
0xDEADBEEF Posted December 3, 2015 Author Posted December 3, 2015 I can't send 73's in gunmode ;) But yes, you're correct!
Santi871 Posted December 3, 2015 Posted December 3, 2015 Yeah this has been a bug that's there for as far as I can remember (probably since release), it's happened a couple times to me but luckily it's not that common
Beamscanner Posted December 21, 2015 Posted December 21, 2015 Did the target have ECM on did you have burn through? don't think the ECM jammers employed on these bad boys operate in that freq. range. Also, we'd see IFF issues elsewhere if that was the case.
Mecrutio Posted December 21, 2016 Posted December 21, 2016 IFF help I have been experiencing this myself lately. Team kills are piling up and this needs to stop. I went thru the noob growing pains learning how to properly IFF with the 27. While I am still new(ish) to implementing the 27 effectively, I have confidence that my last TK was not from my lack of skill. The mission has Blue and Red fighters heading to the same bullseye location. Took off on track to Bulls, angles 6 in the 27. Apon discovering several enemies apporaching I disengaged radar, engaged EOS and went for the mountains. With each lock of the EOS, I would turn on radar and check AFR/A for IFF. One popped up as "A", the HDD recognized it as enemy and was coming from the direction of the opposing team. He was high and cruising fast with no ECM. Needles to say, after he was splashed I received the TK message as was subsequently kicked. I feel like I did everything properly, outside of announcing my intentions to my target. My next tactic is to hard lock then type into the team chat "Raygun" and wait for the response. ( I use TS religiously BTW, many do not ) Does anyone have any advice? Gigabyte Tech. 990FXA-UD3, AMD FX-8350 8 Core, 16 Gig RAM @ 2200 Mhz, Radeon X480, Oculus Rift
DarkFire Posted December 22, 2016 Posted December 22, 2016 I have been experiencing this myself lately. Team kills are piling up and this needs to stop. I went thru the noob growing pains learning how to properly IFF with the 27. While I am still new(ish) to implementing the 27 effectively, I have confidence that my last TK was not from my lack of skill. The mission has Blue and Red fighters heading to the same bullseye location. Took off on track to Bulls, angles 6 in the 27. Apon discovering several enemies apporaching I disengaged radar, engaged EOS and went for the mountains. With each lock of the EOS, I would turn on radar and check AFR/A for IFF. One popped up as "A", the HDD recognized it as enemy and was coming from the direction of the opposing team. He was high and cruising fast with no ECM. Needles to say, after he was splashed I received the TK message as was subsequently kicked. I feel like I did everything properly, outside of announcing my intentions to my target. My next tactic is to hard lock then type into the team chat "Raygun" and wait for the response. ( I use TS religiously BTW, many do not ) Does anyone have any advice? Sounds like you did everything correctly. Looks like there's an IFF bug that needs to be squashed. System Spec: Cooler Master Cosmos C700P Black Edition case. | AMD 5950X CPU | MSI RTX-3090 GPU | 32GB HyperX Predator PC4000 RAM | | TM Warthog stick & throttle | TrackIR 5 | Samsung 980 Pro NVMe 4 SSD 1TB (boot) | Samsung 870 QVO SSD 4TB (games) | Windows 10 Pro 64-bit. Personal wish list: DCS: Su-27SM & DCS: Avro Vulcan.
Schmidtfire Posted December 22, 2016 Posted December 22, 2016 +1. This has happened a few times for me in MP. Im sure that I did IFF properly. Seems to be a bug.
ShuRugal Posted December 23, 2016 Posted December 23, 2016 throwing in my +1 as well; I know of two instances where I have TK'd on a confirmed hostile RAEO lock, both times with 27R. It should be impossible for me to make such a teamkill, because I never shoot in manual override.
Mecrutio Posted December 28, 2016 Posted December 28, 2016 Belay my last. I reviewed the track and I didn't use my radar on that one. Guess I got excited! Gigabyte Tech. 990FXA-UD3, AMD FX-8350 8 Core, 16 Gig RAM @ 2200 Mhz, Radeon X480, Oculus Rift
Recommended Posts