BigEye EWR Script

[leonardo_c]

the venerable EWRS Script by Steggles has recently stopped working and the original repository is no longer maintained.

since the original code does not shine for readability, at least in my lua skills, I decided to start a new implementation from scratch based on Moose. (requires at least Moose 2.9.3)

https://gitlab.com/quelcertoleo/big-eye-ewr

As any of these scripts, many options can be customized. Features:

* zero-configuration on mission editor, no need for group naming prefixes, EWR/AWACS/Radars are added to the set based on coalition

* international system or imperial configurable per client unit through F10 Menu

* reports every 15, 30 or 60 seconds configurable per client unit through F10 Menu

* GCI mode makes the player available for Intercept Tasks per client unit through F10 Menu

* switch to 12-hour format for reporting when units closer than 5 miles

* friendly picture

* speed and altitude cutoffs to simulatore older, less capable systems

* NCTR recognition can be enabled optionally to determine threat type

The format is compact, non invasive of precious screen space and TTS compliant.

Comparison Metric and Imperial units:

Feel free to contribute, I have already planned a set of features that I'd like to have, in order of priority:

* automatically focus reports on nearest contact after merge

Edited March 3 by leonardo_c
update

[leonardo_c]

Added Bogey Dope functionality in Develop branch

https://gitlab.com/quelcertoleo/big-eye-ewr/-/commit/d41394e4caec2072ba14aa794085bd5102c8a975

[leonardo_c]

Pushed Friendly Picture in Develop branch

https://gitlab.com/quelcertoleo/big-eye-ewr/-/tree/develop?ref_type=heads

[leonardo_c]

Pushed GCI feature in Develop Branch, this one is particularly nice.

1) Subscribe to tasking -> EWR will assign the highest priority threat that has entered protected airspace (a Moose ZONE_POLYGON defined in Mission Editor)

2) when contact is closer than 5nm the report format will change and switch from bearing in degrees to 12-hour clock format

3) when target is destroyed (either by player or by any other event) the GCI tasking will be closed

https://gitlab.com/quelcertoleo/big-eye-ewr/-/tree/develop?ref_type=heads

Edited December 8, 2023 by leonardo_c

[leonardo_c]

New version 0.0.5 published

changelog:

0.0.5 - Added Speed cutoff to filter slow movers, Checked for client to be reported to being alive
0.0.4 - remove requirement for ZONE_POLYGON objects defining airspaces

https://gitlab.com/quelcertoleo/big-eye-ewr

happy new year :)

[leonardo_c]

Pushed a new version in develop branch.

Contacts are now ordered by distance and not threat level and a configurable cutoff distance has been added. This cutoff distance can be configured through F10 menu.

https://gitlab.com/quelcertoleo/big-eye-ewr/-/tree/develop?ref_type=heads

[jojo]

On 1/18/2024 at 3:15 AM, leonardo_c said:

Pushed a new version in develop branch.

Contacts are now ordered by distance and not threat level and a configurable cutoff distance has been added. This cutoff distance can be configured through F10 menu.

https://gitlab.com/quelcertoleo/big-eye-ewr/-/tree/develop?ref_type=heads

Thank you for your work  

Would it be possible to provide a simple demo mission please ?

I tried to make a simple mission with your script, with an AWACS.

I get the options through F10 menu, I get message like scanning and so on…but it isn’t reporting me any contact despite the basic AWACS giving me contact through radio.

EWR.gciMaximumRange = 100000 -- meters

Is it 100km from the detecting unit or from the fighter ?

Thanks

Edited February 25, 2024 by jojo

[Bazz_Mulder]

I have the same problem, it looks fine and reporting friendlies but not enemies 

[SilentGreen]

I have had a short look into the script; it seems like you have to modify the prefixes for the filter, that builds the detection-network in order for it to work:

-- prefixes used in mission editor for EWR units
EWR.blueCoalitionRadarPrefixes = { "Blue AWACS", "Blue SAM", "Blue EWR" }
EWR.redCoalitionRadarPrefixes = { "Red AWACS", "Red SAM", "Red EWR" }

... or, instead of modifying the prefixes, just name the units / groups in your ME accordingly, your AWACS for example "Blue AWACS 001".

Hope that helps

[Bazz_Mulder]

That was it! Thanks, it was not clear to me what to do with prefixes.

[[BSD] Solex]

Hello Leonardo, 

Is there a simple mission available? Iam not the worlds greatest .Lua hero

 

Thnx!

Solex

[leonardo_c]

1 hour ago, [BSD] Solex said:

Hello Leonardo, 

Is there a simple mission available? Iam not the worlds greatest .Lua hero

 

Thnx!

Solex

soon(tm)

jokes aside, I'll push a simple mission to the repo, again, soon (tm).

thanks.

[[BSD] Solex]

Thank you!

[leonardo_c]

https://gitlab.com/quelcertoleo/big-eye-ewr

test mission added in tag 0.0.6

also, no more prefixes are required, awacs/ewr/sams will automatically be added to the detection group based on coalition (blue/red)

[Jackal84]

Hello. First of all thanks for the script! I have a question regarding a small issue I am facing. During the missions the script is creating multiple entries "BigEye EWR" in the radio menu with one of them being functional and the rest just being empty. Any idea why? Thanks

[leonardo_c]

2 hours ago, Jackal84 said:

Hello. First of all thanks for the script! I have a question regarding a small issue I am facing. During the missions the script is creating multiple entries "BigEye EWR" in the radio menu with one of them being functional and the rest just being empty. Any idea why? Thanks

are you using multiple client airplanes in a single group? if that's the case, nothing I can do about it because it's a well known dcs "feature".

if that's not the case, please enable debug flag and search this log message in DCS.log.

https://gitlab.com/quelcertoleo/big-eye-ewr/-/blob/main/bigeye_ewr.lua?ref_type=heads#L821

EWR client setup for group etc etc etc

 

Edited May 14, 2024 by leonardo_c

[Jackal84]

Hi, thanks for the reply. Each airplane is a group itself. I will check your suggestion and I´ll come back to you.

[Jackal84]

21 hours ago, leonardo_c said:

are you using multiple client airplanes in a single group? if that's the case, nothing I can do about it because it's a well known dcs "feature".

if that's not the case, please enable debug flag and search this log message in DCS.log.

https://gitlab.com/quelcertoleo/big-eye-ewr/-/blob/main/bigeye_ewr.lua?ref_type=heads#L821

EWR client setup for group etc etc etc

 

 

So I turned on debug mode, I get into the mission and choose a slot. I get this in the log:

2024-05-15 10:23:43.941 INFO    SCRIPTING (Main): EWR client setup for group 80 CAS AV8B 

Few minutes later while I'm still inside the plane, I get a second entry in the radio menu and this in the log:

2024-05-15 10:28:15.934 INFO    SCRIPTING (Main): EWR client setup for group 80 CAS AV8B 1

[leonardo_c]

thank for the test. So one client joins at 10:23 and another one at 10:28. I'll review the code to see if there is some overlap with the names of those client groups.

it is very strange however that apparently both groups have same ID (80) and that's clearly the reason why there are double entries.

now, why there is a duplicate ID is unclear for now.

Edited May 15, 2024 by leonardo_c

[leonardo_c]

2024-05-15 19:38:28.281 INFO    SCRIPTING (Main): EWR client setup for group 116 CAS AV8B
2024-05-15 19:39:04.337 INFO    SCRIPTING (Main): EWR client setup for group 124 CAS AV8B 1

there was no way for me to replicate this issue.

tried joining and rejoining, using some weird regexp in unit or group name, no way.

in the cpde, it's a very simple call to

local playerGroupId = client:GetClientGroupID()

and the moose implementation of that API is a very simple

-- This updates the ID.
  self:GetDCSGroup()

and from moose discord, as I thought, it's an API issue, very strangely, when you request a :Get() it will also update the ID as side effect.

apparently nothing I can do. but again, I use the same code on many missions and it's the first time I get notified about this problem, is perhaps this script running on a server?

I don't know how the internals work to generate those IDs, but after several annoyances with lua.random not being really random perhaps the group name could be a bit more different from one group to another.

Edited May 15, 2024 by leonardo_c

[leonardo_c]

https://gitlab.com/quelcertoleo/big-eye-ewr/-/tree/develop?ref_type=heads

 

 

a lot of improvements in the latest dev branch, I've been testing it for quite a while now and haven't found any issue so will likely release official.

• target heading to aspect Hot, Cold, Flanking
• remove bulls reference
• TTS compliant
• add altitude cutoff
• NCTR option

[Bazz_Mulder]

Bulls was nice. Can It be there as a selectable option?

[leonardo_c]

unfortunately, to avoid making the code too complex, it is either we have aspect in Hot, Cold, Flanking or we have bulls. I opted for the first.

otherwise you will have Hot, Cold, Flanking respect to bulls and it seemed awkward to me when I tested it. to avoid having too many if branches in code it was removed.

[Bazz_Mulder]

Understood, I was not aware of this, makes perfect sense. Thank you.

Is it possible to add a short sound when a message appears on the screen, like the radio transmission end sound in srs?

Edited May 28, 2024 by Bazz_Mulder

[leonardo_c]

0.0.7 is merged to main branch, have fun.