laertesson Posted March 26, 2022 Posted March 26, 2022 (edited) I have experienced this with every single flight I have used George Down Long (re-scan area). When I don't use this command, I never get the MSL NOT READY indication. Edited March 26, 2022 by laertesson
Bailey Posted March 26, 2022 Posted March 26, 2022 I also get MSL NOT READY indication and have trouble getting George to fire on things DCS VoiceAttack Profiles | My Mods and Utilities on ED User Files | DiCE: DCS Integrated Countermeasure Editor DCS Update Witching Utility | DCS-ExportScripts for Stream Deck Community Github Library | Kiowa Integrated Overlays
Wizard1393 Posted March 26, 2022 Posted March 26, 2022 (edited) I've had this a couple of times. Seamed to me you have to be pretty much perfectly lined up with the designated target to be able to fire. EDIT: If using LOAL mode. Edited March 26, 2022 by chrisofsweden GPU: PALIT NVIDIA RTX 3080 10GB | CPU: Intel Core i7-9700K @ 4,9GHz | RAM: 64GB DDR4 3000MHz VR: HP Reverb G2 | HOTAS: TM Warthog Throttle and Stick OS: Windows 10 22H2
H0RN9T_ Posted April 20, 2022 Posted April 20, 2022 (edited) Same here (solo seat, MP) i shot 2 or 3 hellfires and next hellfire was "NOT READY". "re-wasing" didnt help I can give you track file no problem, but there is 1 big problem ... this is 1 big desync, it shows that i didnt even fire 1 hellfire and i am doing "circles", maybe one time bug idk TRACK FILE: https://www.mediafire.com/file/akvs0mox00tg5at/Georgia_At_War_v3.0.24_evening-20220420-225500.trk/file (skip to about 00:12:00 in game time) Edited April 20, 2022 by H0RN9T_ 1
ED Team NineLine Posted April 20, 2022 ED Team Posted April 20, 2022 Is this only seen in Multiplayer as solo pilot or Multicrew then? Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug**
Recommended Posts