Scenario design question regarding emissions and alert state

[1nutworld]

Hey everyone I am looking for some help as I am attempting to design a scenario where one side has it's radars on with various intermittent settings for each radar and SAM's as defense to protect said radars and HVT's in the scenario, but the SAM radars are off until obvious hostile intent is shown.

What I would LIKE to do and I don't know if it is possible (presuming so using lua) that once the attacking force reaches a specific range from targets, or possibly can activate based on number of contacts on the attack, the SAM radars which have been not operating can become active, also on various intermittent settings, until a 2nd distance, closer to the targets is reached, at which point they stop intermittent settings and go fully active.

I was wondering how this type of layered defense could be enabled.

Thanks in advance.

[KLAB]

https://www.matrixgames.com/forums/view ... hp?f=10236
Not sure if this is what you mean... but..
At first glance just having a non user side which has the relevant zones linked to trigger events in the editor would appear simplest.
So Zone A of the non-player side surrounds your Blue side radar circled at whatever direction or distance you want e.g 30nm from the radar and as soon as Red side enters the zone Blue side does X Y or Z. The LUA for changing emission status is covered a lot in the above link and in the specific LUA pages and there may be some code (pretty sure the questions been asked) already for changing the emissions status on detection of any given unit . .
K

[thewood1]

You might be able to do it without lua using the event manager to select and deselect missions based on ship entry into a zone. You get very specific on zone entry as to side, type, or unit. Then build any number of missions with different EMCON settings. You can pick and choose which mission gets loaded based on detection levels.

A way of doing it that is in some ways easier and some ways more complex is to use the event trigger to run a single lua line that loads a new ROE template with different emissions. That is easier in some ways because a template can be used on multiple types of units. But getting the template and lua line just right can be a little complicated.

Also...one more complication is that loading templates can only be done unit by unit. Where as the swapping of entire missions allows large collections of units and groups to be included.

[1nutworld]

https://www.matrixgames.com/forums/view ... hp?f=10236
Not sure if this is what you mean... but..
At first glance just having a non user side which has the relevant zones linked to trigger events in the editor would appear simplest.
So Zone A of the non-player side surrounds your Blue side radar circled at whatever direction or distance you want e.g 30nm from the radar and as soon as Red side enters the zone Blue side does X Y or Z. The LUA for changing emission status is covered a lot in the above link and in the specific LUA pages and there may be some code (pretty sure the questions been asked) already for changing the emissions status on detection of any given unit . .
K

I'll have to look this over this weekend when I am off work and see if there are things I can use. Thanks for sharing that link. I keep forgetting that was created.

[1nutworld]

You might be able to do it without lua using the event manager to select and deselect missions based on ship entry into a zone. You get very specific on zone entry as to side, type, or unit. Then build any number of missions with different EMCON settings. You can pick and choose which mission gets loaded based on detection levels.

A way of doing it that is in some ways easier and some ways more complex is to use the event trigger to run a single lua line that loads a new ROE template with different emissions. That is easier in some ways because a template can be used on multiple types of units. But getting the template and lua line just right can be a little complicated.

Also...one more complication is that loading templates can only be done unit by unit. Where as the swapping of entire missions allows large collections of units and groups to be included.

I will have to spend some time looking over event manager and finding out how to best utilize that function. That wasn't anything I was thinking of being able to use. So thank you for that suggestion

[thewood1]

So my first paragraph is wrong. Missions can't have intermittent sensor. My mind is getting old. I think I knew that at one time and forgot. It actually makes no sense unless I'm missing something. I just tried what you are trying to do and that issue put a stop to it.

And even the simple lua option won't work by loading templates into ROE easily. I think that lua function got removed at some point.

So I'll continue to play around with it and see what comes of it. May the devs can explain the reasoning behind limiting intermittency in missions. It seems like a pretty basic function.

[thewood1]

I went the event/lua route. It keeps the amount of lua to simple single lines. I have set this scenario to roughly test the concept. There are three events: enter an outer zone that triggers intermittent radar, enter an inner zone and full radar, then an exit the outer zone and radar shuts off. Each event has single line of lua code that activates on the zone triggers. Works fairly well, but would be simpler if you could load intermittent radar missions.

Again, its rough but shows the concept working.

[Blast33]

Thanks, I was working on the same issue, but to have a concrete example is so handy