NomadActual Posted February 10 Posted February 10 On 1/10/2025 at 7:39 PM, gunterlund said: ok so I had a chance to test this out on an MP server and I must say it worked really well. I use moose to do most of my scripting and even with MIST loaded the mission did not have any issues between Moose and Mist. One thing I did is created a menu stack so I can kick in the jamming process after Ive spawned into a slot. We did Offensive Jamming towards SA-10 and SA-5 and we were able to safely get in close enough to launch HARMs etc. Was able to turn the jamming on and off via the menu which is good. Now again the big problem is in an MP server once you turn this on, leave and come back, into the same aircraft, the system is still running and the menus get doubled up and knocked out of action until you reset the mission. So there must be a way to counter that. Ive asked a couple of the MOOSE devs to look at this to see if they can convert it to a MOOSE function so we dont need both MIST and MOOSE. All props to @ESAc_matador for the great job on this. This would be MASSIVE. Best of luck!
toan Posted May 21 Posted May 21 (edited) On 1/11/2025 at 1:31 AM, gunterlund said: You probably did not start the actualy jamming component in a trigger. Hi, I loaded Mist and the EW Script in the ME, via specific triggers. Then, is it enough to have a new trigger in the ME like "EWjamm("Buddy") to invoke the jamming process for the particular aircraft having a pilot named 'Buddy' ? And how do I stop the jamming process ? It sems the F10 radio menu doesn't work for all that. Thanks for your help. Edited May 21 by toan
Recommended Posts