ohcrapBEARS Posted January 26, 2021 Posted January 26, 2021 Hey guys. I've noticed that since the update that changed the Phoenix behavior to make them perform more realistically, I've run into an occasional issue where the WCS just never tells the missile to go active, at least as far as I can tell. In these instances, I'm not losing track of the target in TWS. I'll watch the TTI countdown as normal but it'll never flash to indicate the missile going active, and the missile will just continue flying straight ahead indefinitely. The problem is kind of hard to recreate as it seems to be fairly random when it happens, however it seems to be more common at closer ranges, ie: <30nm at around 20,000ft.
QuiGon Posted January 26, 2021 Posted January 26, 2021 A track file would help. 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!
captain_dalan Posted January 28, 2021 Posted January 28, 2021 MP or SP? Modules: FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, F-14A, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, MiG-15, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map, Marianas map, Syria Map, Super Carrier, Sinai map, Mosquito, P-51, AH-64 Apache, F4U Corsair, WWII Assets Pack
miromurin Posted January 28, 2021 Posted January 28, 2021 SP. but it happened just few times to me. not sure why.
captain_dalan Posted January 30, 2021 Posted January 30, 2021 Did happen to me a couple of times but only in MP. Wasn't sure if it was a bug or feature, as i could not repeat the occurrence in controlled conditions. Modules: FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, F-14A, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, MiG-15, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map, Marianas map, Syria Map, Super Carrier, Sinai map, Mosquito, P-51, AH-64 Apache, F4U Corsair, WWII Assets Pack
ohcrapBEARS Posted January 30, 2021 Author Posted January 30, 2021 (edited) Went back and managed to recreate the bug, or at least I think it's a bug, and I attached a track file and will have a youtube link for actual video footage as well. Worth mentioning is that this is in single player too so there's not some desync stuff going on or anything like that. My theory is that the radar is actually losing track of the target briefly, but in this instance, it should then divert to having a simulated track. Instead, this never happens and the WCS never tells the missile to go pitbull at all. I tested this on the PG BVR instant action mission, but it's modified to have an AWACS so data link could potentially be a factor as well, but I genuinely have no idea. It's pretty easy to recreate because it'll happen pretty often if you crank more than 20 or so degrees in either direction. I also tested this in the newest open beta, this being version 2.5.6.60645. Video file is linked below https://youtu.be/pJYlZcNT0lI AIM-54 bug.trk Edited January 30, 2021 by ohcrapBEARS 1 1
AH_Solid_Snake Posted February 2, 2021 Posted February 2, 2021 I wonder if theres some interplay between the datalink and TWS track, it looked like right around 1:18 into your video the datalink track and your TWS track diverged for a second and you got 3 vector lines while the target seemed to be going into a right hand turn. Would you mind repeating your test with the datalink off? 1
Recommended Posts