Jump to content

Recommended Posts

Posted
On 1/24/2023 at 1:54 AM, Hallsy said:

I took a look through the script and couldn't find the death association. Let me know if you have any luck. The defensive jamming is awesome and very effective.

lookup at (jammer) table, then do table.remove(jammer, unit) upon unit destruction. i hope you can list that table and code removal, either coded in script or by trigger in ME. 

there's a trigger action at line 69, uncomment that and look at dcs.log for list of active jamming planes. again --> mist.utils.tableShow(jammerplanes) --> that should be like mist.utils.tableShow(jammer) as it looks like dev has changed variable definition. try that.

Posted
On 1/24/2023 at 1:54 AM, Hallsy said:

The defensive jamming is awesome and very effective

its actually a giant SAM shield that I'm no fan of. That makes your survival skills downgraded. there are always some more exciting and rewarding ways to dodge radar SAMs. At last, the real threat are those silent ones.

  • 4 weeks later...
  • 2 weeks later...
Posted
On 1/26/2023 at 6:07 PM, jackmckay said:

lookup at (jammer) table, then do table.remove(jammer, unit) upon unit destruction. i hope you can list that table and code removal, either coded in script or by trigger in ME. 

there's a trigger action at line 69, uncomment that and look at dcs.log for list of active jamming planes. again --> mist.utils.tableShow(jammerplanes) --> that should be like mist.utils.tableShow(jammer) as it looks like dev has changed variable definition. try that.

So for those who are still new at this LUA thing remove the dashes and look at the log or do we need to change the line to what you have shown? {mist.utils.tableShow(jammer)}??

Posted
On 3/6/2023 at 2:34 PM, RayBurge said:

So for those who are still new at this LUA thing remove the dashes and look at the log or do we need to change the line to what you have shown? {mist.utils.tableShow(jammer)}??

im not that old in lua too, but yes, uncomment that line and check dcs log for extra message lines. for short code test you need debug console like dcs bios, witchcraft or dcs eclipse debugger or something, just to check if the table has client module inside to work properly. then upon death of unit those table should be purged of unnecessary clients. it takes some skill but its not that hard to code it.

if you uncomment that line in script, on around line 69 that has tableShow, dcs.log will show jamming units in log lines so you can check who is using script.

 

  • 2 months later...
  • 2 months later...
Posted (edited)

The script is working with you fellow pilots after latest beta update? just to check if i´m doing something wrong (although it´s the same mission i edited before the update) or if it is in reality an issue.

 

Thank you in advance,

F.

Edited by fagulha
Typo

About carrier ops: "The younger pilots are still quite capable of holding their heads forward against the forces. The older ones have been doing this too long and know better; sore necks make for poor sleep.'

 

PC: 14th I7 14700KF 5.6ghz | 64GB RAM DDR5 5200 CL40 XMP | Gigabyte RTX 4080 Super Aero OC 16 GB | Thermalright Notte 360 RGB | PSU Thermaltake Though Power GF A3 Snow 1050W ATX 3.0 /  1 WD SN770 1TB M.2 NVME + 1 SSD M.2 2TB + 2x SSD SATA 500GB + 1 Samsung 990 PRO 4TB M.2 NVME (DCS only) | Valve Index| Andre´s JeatSeat.

  • 4 weeks later...
Posted
15 hours ago, RayBurge said:

At fagulha, have you had a better time for this im wondering if it was working fully now?

 

I did not tried since last time i posted here. Going to test in my free time in 2 days. But the mod isn´t updated since 2017, so, i doubt it´s working.

About carrier ops: "The younger pilots are still quite capable of holding their heads forward against the forces. The older ones have been doing this too long and know better; sore necks make for poor sleep.'

 

PC: 14th I7 14700KF 5.6ghz | 64GB RAM DDR5 5200 CL40 XMP | Gigabyte RTX 4080 Super Aero OC 16 GB | Thermalright Notte 360 RGB | PSU Thermaltake Though Power GF A3 Snow 1050W ATX 3.0 /  1 WD SN770 1TB M.2 NVME + 1 SSD M.2 2TB + 2x SSD SATA 500GB + 1 Samsung 990 PRO 4TB M.2 NVME (DCS only) | Valve Index| Andre´s JeatSeat.

Posted

yeah thanks, for the life of me and my little know how getting the re spawn in a bird that crashed is still not working. one day it will im sure.

  • Like 1
  • 1 month later...
Posted (edited)

Hello guys, also frustrated that I can't really play a real electronic war. I turned towards the triggers, to simulate penetration into enemy territory.
here is the formula to enter into ME.
With this formula, you create a random countdown of 5 to 25 minutes, which makes you invisible to SAM threats, and which stops invisibility randomly.

 

 

Here is the formula :

Random Countdown

Once > Time Less than 5 > Set Flag 1 Random Value from 50 to 100
Switched Condition >Time Since Flag 1 is 30 seconds > Flag 1 Decrease 1
Once > Flag 1 Equals 1 > Activate Group or FLAG or Action PRIORITY.

 

En sorry for my English.

Jab_Electronic-War-JammingV3.miz

Edited by The_Jab
  • Thanks 1
  • 4 weeks later...
  • 2 months later...
Posted

Hi Matador,

This is an amazing script! Has anyone managed to get it to work after death? Whenever a client dies or reslots, the script fails until the server resets. I have been looking through the lua, but my untrained eyes can't find the culprit.

Thank!

  • 3 weeks later...
  • 8 months later...
Posted

How does one install this? I have it downloaded but don't know where to put the LUA or well, really anything...Never messed with scripting or stuff like that. Definitely need a For Dummies break down on how to make this work.

Former SSG US Army

UH-60A/L/M Crewchief

"2 To Fly!"

Posted (edited)
On 10/13/2024 at 4:21 PM, H60MTI said:

How does one install this? I have it downloaded but don't know where to put the LUA or well, really anything...Never messed with scripting or stuff like that. Definitely need a For Dummies break down on how to make this work.

You need to create a Trigger within Mission Editor to load the .lua file (there´s a manual explaining how it works in the first page of this thread). But there´s more into it.

Said that, my humble advice is to you to learn how to use Mission Editor first before start using scripts. There´s a lot of Youtube tutorials about Mission Editor and scripts for DCS.

Enjoy.

Edited by fagulha

About carrier ops: "The younger pilots are still quite capable of holding their heads forward against the forces. The older ones have been doing this too long and know better; sore necks make for poor sleep.'

 

PC: 14th I7 14700KF 5.6ghz | 64GB RAM DDR5 5200 CL40 XMP | Gigabyte RTX 4080 Super Aero OC 16 GB | Thermalright Notte 360 RGB | PSU Thermaltake Though Power GF A3 Snow 1050W ATX 3.0 /  1 WD SN770 1TB M.2 NVME + 1 SSD M.2 2TB + 2x SSD SATA 500GB + 1 Samsung 990 PRO 4TB M.2 NVME (DCS only) | Valve Index| Andre´s JeatSeat.

  • 1 month later...
  • 1 month later...
Posted (edited)

 

On 11/29/2024 at 11:43 AM, RayBurge said:

My concern was with the death of a client and the script not working so it seems someone got it fixed how? @MangoMan?

One think I noticed is in an MP server if you join the jamming aircraft then leave the slot and rejoin it, it will double up the menu option for jamming and make it inoperable.

does anyone know if its possible to turn the jamming off. In particular if an AI Aircraft is doing offensive jamming?

Edited by gunterlund
Posted
1 hour ago, Ken_Waters said:

I have this script loaded with MIST into a mission, however the menu does not show up. am i missing a step?

 

You probably did not start the actualy jamming component in a trigger. 

Posted

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. 

  • Like 1
  • 2 weeks later...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...