Feature Request: Allow overlay comms (e.g. AWACS) without being in DCS (e.g. for use with LotATC)

[HomeFries94]

Just a request to allow the overlay to govern radio frequencies in lieu of DCS Export. Useful with LotATC (which doesn't require DCS to even be on the system, much less running). This allows for integrated ATC and AWACS support.

Implementation: either have a checkbox in the overlay to supersede export.lua, or automatically supersede as long as DCS is not running. Can disable server side if cheating or spamming is a concern.

[Quax456]

This would be a much better solution than the foreward Observer.
Shure I'm an owner of LotATC but its relay cool to control the combat, isn't it?

[ciribob]

Exactly as you describe is how I've been toying with implementing it.

The most important part being the server side control which'll be off by default

The main reason I haven't is there is no way of guaranteeing you're on one side or the other so if a server allows this, it'll also have to allow spectator audio and turn off coalition security which might confuse people.

[HomeFries94]

Good point about the side control. I normally fly coop so I don't think intuitively about such things.

To this end, here are some possible control ideas:

1. Have the client choose a side before joining the server. This would obviously be overridden if the client jumps into an aircraft or ground unit, but could be a control against arbitrarily switching sides.
2. Server side option to require a timeout when jumping between sides as a client with no export file.

EDIT: Perhaps the control could be within the spectator audio option itself. Allowing spectator audio for a client without export.lua would provide access to whatever side is selected by the client, and disabling spectator audio would disallow the client from superseding export.lua. I'm not sure how coalition security works (I assume this is the encryption), but I would think that assigning status like CA for whatever side is selected in the client would work itself out. In fact, if different sides use different encryption keys, then this information could keep such a client out of enemy comms without requiring the controls I described earlier in this post.

I'm just trying to think of ways to keep the pain of implementation to a minimum.

[HomeFries94]

Any headway on this, Ciribob? It would be a huge benefit for large multiplayer events.

[szporwolik]

I came here just to put this feature request in only to find out it's already here. :)

@ciribob please - runing the LotATC + DCS Simpleradio without need to run DCS would be a great deal for the community, please think about. If PvP mission are concern maybe for the beginning just put the On/Off option on the server to allow/disallow direct connections.

Guys from LotATC are handling it with the simple config file allowing to set seperate (hidden at the server) passwords for RED and BLUE.

Please think about - as mentioned, this would be a great game changer for most of us ATC guys. 👍

[MorpheusXAUT]

I definitely like the side-password idea, should be pretty straight forward to implement. Not direct LotATC integration for the beginning, but making SRS usable without DCS running as a start (if enabled on the server).

I'll be looking into this in the next days.

[MorpheusXAUT]

First version done and to be released as a beta version for testing in the near future 😃

[szporwolik]

Dude, that's a really great news - thank you for all the effort! :)

[MorpheusXAUT]

A beta version containing this feature has been release - if you're using the 1.5.3.1 prerelease, you'll be able to try it out before the final stable release, be aware that you will not be able to use the 1.5.3.1 server with older clients or the other way around.
Any feedback would be highly appreciated!

[ciribob]

in latest release 1.5.3.2

[HomeFries94]

Thanks for this!