NeMoGas Posted May 28, 2019 Posted May 28, 2019 So I have had this issue on more occasions then I can count. The issue is I lock a target in the HUD with an AIM9X using the uncage button. I fox the first missile and the second does not auto acquire the target. This seems to happen maybe 25% of the time, maybe more. I do not think it is a masking issue as the target is in the HUD, and I'm using wing tip mounted 9X's. Is this a bug, or intended? It has got me killed many times as I fight to relock the target.
Svend_Dellepude Posted May 28, 2019 Posted May 28, 2019 Using jhmcs to slave the 9X works everytime. Somehow it doesnt seem so eager to want to track the radar lock. [sIGPIC][/sIGPIC] Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.
foxwxl Posted May 30, 2019 Posted May 30, 2019 same here when using radar slave mode, the Aim9 does NOT have the correct tone (this happens more often AFTER the 1st AIM9 launched) Deka Ironwork Tester Team
macedk Posted May 30, 2019 Posted May 30, 2019 early release and no hard info on what is bugged or not. We have to live with it until we get hard info whether it is bugged or not. OS: Win10 home 64bit*MB: Asus Strix Z270F/ CPU: Intel I7 7700k /Ram:32gb_ddr4 GFX: Nvidia Asus 1080 8Gb Mon: Asus vg2448qe 24" Disk: SSD Stick: TM Warthog #1400/Saitek pro pedals/TIR5/TM MFDs [sIGPIC][/sIGPIC]
EAF602 Red Posted May 31, 2019 Posted May 31, 2019 Think the AIM9x has to be on outboard pylons to be at its most effective, if it's on the inner pylons it doesn't have the same flexibility, that might be the issue. so I read somewhere Red
Svend_Dellepude Posted June 1, 2019 Posted June 1, 2019 I always have it outboard and still have problems. Will see if i can get a track uploaded. [sIGPIC][/sIGPIC] Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.
Recommended Posts