Be able to add/remove F10 radio menus/commands/submenus PER UNIT

[TEMPEST.114]

as the title says. 

The current restriction on doing it PER GROUP is not working in so very many scenarios. It's too excessive.

[TEMPEST.114]

Actually I really, really need this to be added asap. My script / concept doesn't work if I can't change the menu system PER UNIT rather than group. 

I know a work around would be every player unit would be it's own group but because you restrict the callsigns for the flights to a set list, that restricts the number of players. And yeah, sometimes I need a flight of more than one person... 

This shouldn't be too hard to quickly put in, but by the stars I really need it... Please?!

[TEMPEST.114]

Almost 2 years later, and STILL this has been completely ignored. 

PLEASE add this. 

[DD_Friar]

@Elphaba - You need to cast your net a bit wider, have a look at the excellent by @cfrag DML Tool Box.

One of the options you can use is Radio Menus (see below)

null

Edited March 6, 2024 by DD_Friar

[TEMPEST.114]

Thanks but I know all this.

There is still a critical need to be able to send / receive messages to/from a UNIT i.e. player in MP and in SP.

And it needs to be native not via a 3rd party library.

It's impossible to drive a narrative or issue specific instructions to an individual unit until ED add this feature. There is no reason for it not to exist. It's just a forced limitation, much like the inability to have more than 4 ships in a group or have mixed units in a group. No reason except artificial limitations. 

Edited March 6, 2024 by Elphaba

[cfrag]

19 minutes ago, Elphaba said:

No reason except artificial limitations. 

I believe that we all can agree that the reason for this is that DCS's abilities/disabilities in these things stem from the fact that their mission API has grown organically over the past decade rather than having been engineered. So IMHO the entire tree of accessors for mission designers to players is currently lacking and looks a bit bolted together. It would indeed be a boon for mission designers if we can have a unit-specific missionCommands branch. The outTextForXXX and outSoundForXXX trees have received a unit branch, even if the outSound branch still appears to be flaky in MP. But I think we can agree that those methods are also more a kludge than a designed solution to communicate, so here's hoping that ED can find the time to engineer a new, better suited API to communicate with players.

[TEMPEST.114]

Hear, hear.

[Maverick87Shaka]

A little UP also from me on this topic.
Per UNIT radio menu it will be extremely useful to even optimize more the popular CTLD script, and will be extremely useful for the upcoming C-130J / CH-47.
So far we're forced to use single unit per group as a workaround and it's completely a waste of callsign

[rob10]

9 hours ago, Elphaba said:

. No reason except artificial limitations.

Completely agree this would be AWESOME to have available, but not sure I agree with the above statement.  I have no idea how the background programming works, but as cfrag said, on the mission editor side I think it's a bit cobbled together rather than well planned out.  It wouldn't surprise me if they can't easily allow this because of the way units are "grouped".  There's a bunch of other stuff that is only changeable for the whole group, so seems like that might be the level at which it computes things (likely to save resources).  So while I'm sure it's possible to do this, I don't think it's necessarily a quick and easy change to make.

[TEMPEST.114]

11 minutes ago, rob10 said:

Completely agree this would be AWESOME to have available, but not sure I agree with the above statement.  I have no idea how the background programming works, but as cfrag said, on the mission editor side I think it's a bit cobbled together rather than well planned out.  It wouldn't surprise me if they can't easily allow this because of the way units are "grouped".  There's a bunch of other stuff that is only changeable for the whole group, so seems like that might be the level at which it computes things (likely to save resources).  So while I'm sure it's possible to do this, I don't think it's necessarily a quick and easy change to make.

Each unit has it's own uniqueness. I've been able to write a script that can address an individual unit within a group. It runs afoul of the artifical limitations from ED on how and when the menus are redrawn as it can change references in the background due to the update. 

It's really not a hard fix - much like the broken winds - it's just no one ever gets round to it in favour of other things - things that aren't always as big a win as fixing the wind for example.