Skynet: An IADS for Mission Builders

[Kazansky222]

This is great! love the added harm detection mechanic!

[Bananabrai]

Very nice, sounds great.

 

I still need unwrap my brain and draw the IADS layout that I want in my mission

And then I need to join the Discord :book:

 

Another thing, if I add a blue jammer, that works for blue and against red, correct?

Was a bit confused by the english description.

 

The word emitter is used quite a few times.

The Stand-Off jamming A/C is an emitter, as a SAM site is as well.

Both are emitting...

 

Maybe I am the only one who was confused.

[flywaldair (Skynet dev.)]

Very nice, sounds great.

 

I still need unwrap my brain and draw the IADS layout that I want in my mission

And then I need to join the Discord :book:

 

Another thing, if I add a blue jammer, that works for blue and against red, correct?

Was a bit confused by the english description.

 

The word emitter is used quite a few times.

The Stand-Off jamming A/C is an emitter, as a SAM site is as well.

Both are emitting...

 

Maybe I am the only one who was confused.

 

The jammer will jam the IADS it is connected to in the code, so theoretically you could jam blue on blue. Anyway the jammer is fairly simple. The other elements in the iads are more realistic.

 

emitter is based on the context in the documentation so yes it is used to describe a radar or jamming unit.

 

Du kannst mir auch auf deutsch schreiben!

[Loneagle]

Hi guys I've tried everything to add EW radars but I can't, even getting all SAMs and set them like EW radars doesn't work...

 

this is the code I'm using

 

do
--Create an instance of the IADS
redIADS = SkynetIADS:create('IRAN')

---debug settings remove from here on if you do not wan't any output on what the IADS is doing by default
local iadsDebug = redIADS:getDebugSettings()
iadsDebug.IADSStatus = true
iadsDebug.samWentDark = true
iadsDebug.contacts = true
iadsDebug.radarWentLive = true
iadsDebug.noWorkingCommmandCenter = true
iadsDebug.ewRadarNoConnection = true
iadsDebug.samNoConnection = true
iadsDebug.jammerProbability = true
iadsDebug.addedEWRadar = true
iadsDebug.hasNoPower = true
iadsDebug.harmDefence = true
iadsDebug.samSiteStatusEnvOutput = true
iadsDebug.earlyWarningRadarStatusEnvOutput = true

--add all units with unit name beginning with 'EW' to the IADS:
redIADS:addEarlyWarningRadarsByPrefix('EW')

--Add all groups begining with group name 'SAM' to the IADS:
redIADS:addSAMSitesByPrefix('SAM')

--Add Command Center
commandCenter = StaticObject.getByName('C3I2-Bandar-Abbas')
redIADS:addCommandCenter(commandCenter)

--Get all SAMs
redIADS:getSAMSites():setHARMDetectionChance(100):setActAsEW(true)

--Add SA-10 point defense
local SA15B = redIADS:getSAMSiteByGroupName('SAM-SA15-002')
redIADS:getSAMSiteByGroupName('SAM-SA10'):addPointDefence(SA15B):setHARMDetectionChance(100):setIgnoreHARMSWhilePointDefencesHaveAmmo(true)

--Activate the radio menu to toggle IADS Status output
redIADS:addRadioMenu()

-- Activate the IADS
redIADS:activate()

end

I appreciate any help about it.

Edited June 4, 2020 by Loneagle

[Bananabrai]

Maybe a stupid question, but did you make sure:

 

The group name of your EW site/sites start with "EW"?

The group name of your SAM sites start with "SAM"?

 

Did you load the scripts in the follwoing order?

 

1. load MIST

2. load skynet-iads-compiled.lua

3. load skynet-iads-setup-YOUR-SCRIPT.lua

 

 

I always do it that way:

1st triggger: once | time more (5) | do script 1(ex. MIST) + text to confirm trigger worked

2nd triggger: once | time more (10) | do script 2(ex. CTLD)+ text to confirm trigger worked

3rd triggger: once | time more (15) | do script 3(ex. MOOSE)+ text to confirm trigger worked

...

[example above not correct/represantative for CTLD, MIST or MOOSE]

[stormrider]

1- Is it possible to make a SAM operating autonomously to sporadically light up?

2- Is it possible to make a IADS within another IADS in hierarchy? For example: 3 individual sector IADS formed by, let's say, 3x SA-2 + 3x SA-3 + 1x EW + 1x Command-Center and linked together by a central Command-Center, so once this central commander is destroyed, the individual sector IADS stop sharing contacts within each other.

Edited June 9, 2020 by stormridersp

[stormrider]

Hi guys I've tried everything to add EW radars but I can't, even getting all SAMs and set them like EW radars doesn't work...

 

this is the code I'm using

 

do
--Create an instance of the IADS
redIADS = SkynetIADS:create('IRAN')

---debug settings remove from here on if you do not wan't any output on what the IADS is doing by default
local iadsDebug = redIADS:getDebugSettings()
iadsDebug.IADSStatus = true
iadsDebug.samWentDark = true
iadsDebug.contacts = true
iadsDebug.radarWentLive = true
iadsDebug.noWorkingCommmandCenter = true
iadsDebug.ewRadarNoConnection = true
iadsDebug.samNoConnection = true
iadsDebug.jammerProbability = true
iadsDebug.addedEWRadar = true
iadsDebug.hasNoPower = true
iadsDebug.harmDefence = true
iadsDebug.samSiteStatusEnvOutput = true
iadsDebug.earlyWarningRadarStatusEnvOutput = true

--add all units with unit name beginning with 'EW' to the IADS:
redIADS:addEarlyWarningRadarsByPrefix('EW')

--Add all groups begining with group name 'SAM' to the IADS:
redIADS:addSAMSitesByPrefix('SAM')

--Add Command Center
commandCenter = StaticObject.getByName('C3I2-Bandar-Abbas')
redIADS:addCommandCenter(commandCenter)

--Get all SAMs
redIADS:getSAMSites():setHARMDetectionChance(100):setActAsEW(true)

--Add SA-10 point defense
local SA15B = redIADS:getSAMSiteByGroupName('SAM-SA15-002')
redIADS:getSAMSiteByGroupName('SAM-SA10'):addPointDefence(SA15B):setHARMDetectionChance(100):setIgnoreHARMSWhilePointDefencesHaveAmmo(true)

--Activate the radio menu to toggle IADS Status output
redIADS:addRadioMenu()

-- Activate the IADS
redIADS:activate()

end

I appreciate any help about it.

 

 

 

 

I'm also having the exact same issue. It won't include the EW.

 

 

Here's my setup code:

do

--create an instance of the IADS
redIADS = SkynetIADS:create('Kari')

---debug settings remove from here on if you do not wan't any output on what the IADS is doing by default
local iadsDebug = redIADS:getDebugSettings()
iadsDebug.IADSStatus = true
iadsDebug.samWentDark = true
iadsDebug.contacts = true
iadsDebug.radarWentLive = true
iadsDebug.noWorkingCommmandCenter = true
iadsDebug.ewRadarNoConnection = true
iadsDebug.samNoConnection = true
iadsDebug.jammerProbability = true
iadsDebug.addedEWRadar = true
iadsDebug.hasNoPower = true
iadsDebug.harmDefence = true
---end remove debug ---

--add all units with unit name beginning with 'EW' to the IADS:
redIADS:addEarlyWarningRadarsByPrefix('EW')

--add all groups begining with group name 'SAM' to the IADS:
redIADS:addSAMSitesByPrefix('SAM')

--add a command center:
commandCenter = StaticObject.getByName('Command-Center')
redIADS:addCommandCenter(commandCenter)

--activate the radio menu to toggle IADS Status output
redIADS:addRadioMenu()

--activate the IADS
redIADS:activate()    

 end

 

 

Edit: I guess I fixed it by naming the unit with the prefix EW, instead of the group.

Edited June 9, 2020 by stormridersp

[Boagord]

We are using this script since a while now, it works great! Is it possible to add a border system?

 

 

IE :

 

Sam will engage intruders only ( Opposite force inside a zone)

 

If some unit has been hit there is no more border

 

 

It's just an idea

[Loneagle]

Edit: I guess I fixed it by naming the unit with the prefix EW, instead of the group.

 

 

I'll try thank you a lot!

[flywaldair (Skynet dev.)]

thanks for the feedback guys.

 

For support please join the discord group:

https://discord.gg/tmquky

 

I have a backlog of roughly 20 new features I like to add, unfortunately the Summer weather and VFR Flying are keeping me from developing the script at the moment ;-)

[flywaldair (Skynet dev.)]

1- Is it possible to make a SAM operating autonomously to sporadically light up?

2- Is it possible to make a IADS within another IADS in hierarchy? For example: 3 individual sector IADS formed by, let's say, 3x SA-2 + 3x SA-3 + 1x EW + 1x Command-Center and linked together by a central Command-Center, so once this central commander is destroyed, the individual sector IADS stop sharing contacts within each other.

 

 

Currently there is no Hierarchy supported. Also sporadical light up is not implemented at the moment.

[Loneagle]

Edit: I guess I fixed it by naming the unit with the prefix EW, instead of the group.

 

 

It works, thanks a lot!

[Cake]

thanks for the feedback guys.

 

For support please join the discord group:

https://discord.gg/tmquky

 

I have a backlog of roughly 20 new features I like to add, unfortunately the Summer weather and VFR Flying are keeping me from developing the script at the moment ;-)

 

Bummer, you were so close to it becoming self aware. :robot:

[Scotch75]

Hey Folks,

 

 

@tigair, great work with this project, well done!

 

 

I'm trying to make a simple SEAD mission using SkyNet, Wrench's carrier script (got that working ok), and Hervirek's PG Template (https://www.digitalcombatsimulator.com/en/files/3310678/) as a test. Hervirek has provided a setup lua in the download called IRANtsky.lua.

 

 

Trying to follow the instructions on the GitHub, I have loaded MiST, loaded the skynet-iads-compiled.lua, and IRANsky.lua as per the example screenshots. I can't get SkyNet to activate.

 

 

Could you please have a look at the attached mission to see what I have done wrong?

 

 

Many thanks

Scotch

SkyNet PG_Test.miz

[flywaldair (Skynet dev.)]

@Skotch75:

Thank you, I am happy to see that mission builders are using the script.

 

I have my DCS setup at work, so unfortunately I can not look at the mission at the moment.

I believe you have already joined the discord group? https://discord.gg/MQGPup

Im sure someone can help you there.

Edited June 28, 2020 by tigair

[flywaldair (Skynet dev.)]

Bummer, you were so close to it becoming self aware. :robot:

 

:thumbup::thumbup:

[flywaldair (Skynet dev.)]

Skynet Update, see first post of thread.

[flywaldair (Skynet dev.)]

Update: Develop branch now features a Moose A2A Dispatcher connector:

https://github.com/walder/Skynet-IADS/tree/develop

 

Check the demo-missions folder.

 

Documentation will follow

[ESAc_matador]

Hello tigair. Did you see what I did for jamming? It takes a lot of factors for proper jamming... It may be interesting to have a look.

 

Also, what is the main differences with the old Grimes IADS script?

[flywaldair (Skynet dev.)]

Hi, I had a look at you script, quite a lot of functionality in it. I have sort of stopped working on the jammer since the scripting engine is very limited so simulate jamming. Besides there is very little public information on how jamming works IRL and what the effects are on different radar systems.

 

Skynet has more setup options including power sources and connection nodes. Check out the documentation on gitHub: https://github.com/walder/Skynet-IADS

[flywaldair (Skynet dev.)]

Moose A2A Dispatcher connector is now in the release build, check GitHub link in first post of thread.

[IceFire]

Hey!

 

I really love your script, most excellent!

 

The only problem I'm having with it is that an SA-15 for point defense does not pre-deploy to be ready to shoot. Is it possible to fix that or are there any workarounds? I use the setup before activation command but it seems to make no difference.

 

Thanks!

 

Edit: found a workaround. Just set the state to RED at the beginning of the mission and they unfold and are ready at the start.

Edited July 11, 2020 by IceFire

[flywaldair (Skynet dev.)]

Thanks, great to hear!

 

Try setting up the IADS like this, it will allow the SAM sites 30 seconds to warm up before their state is frozen and the IADS spools up:

 

redIADS = SkynetIADS:create('Enemy IADS')
redIADS:addSAMSitesByPrefix('SAM')
redIADS:addEarlyWarningRadarsByPrefix('EW')
redIADS:setupSAMSitesAndThenActivate(30)

 

When calling:

redIADS:setupSAMSitesAndThenActivate(30)

 

You must not also call:

redIADS:activate()

 

The second call will cancel the warm up.

 

IF you need further support join the Discord group: https://discord.gg/pz8wcQs

[Knock-Knock]

redIADS = SkynetIADS:create('Enemy IADS')

 

 

Is it required to name the 'create', even when using a IAD setup for both coalitions?

[flywaldair (Skynet dev.)]

no