Radio message initiator question

[Shahdoh]

I am wanting to send a message back to the client that initiates a radio call from the comm menu. Is this even possible? Right now the message goes out to all.

 

Thanks

[Flagrum]

I am wanting to send a message back to the client that initiates a radio call from the comm menu. Is this even possible? Right now the message goes out to all.

 

Thanks

What about a triggered action "RADIO TRANSMISSION"?

[Shahdoh]

Seems you can only send audio that way. I need to send text back to just the requester of the data. If it can be done, please, educate me.

 

Thank you.

[MTrenda]

you may want to look at the triggered actions on the unit itself.

 

thanks

 

76th Falcon

[Druid_]

Iirc use

 

MESSAGE TO GROUP groupname. If it's not in the GUI trigger list then there is a lua equivalent

trigger.action.outTextForGroup(GroupId groupId, string text, Time delay)

[Shahdoh]

Thanks Druid, unless I am over thinking this, how do I get the group ID of the person that initiated the Comm message?

 

Example:

Player A hits \ to open comms menu, presses F10, selects option to request data.

 

Is this tied to an event ID or something else I can get the group ID of the comms initiator?

(To many client aircraft to enter these in the mission editor, need to use LUA)

[number3]

I'm also wondering if this is possible using scripts.

 

Trying to figure out who (whether it be a unit or group, doesn't matter in my case) initiated the message.

 

I want to add a menu item that reports on the current status of the attacking ground forces, but I don't want to push the status message to everyone in the coalition, because some people may have missed the message or didn't finish reading it in time and I want to give them the option to replay the message without bothering everyone else who is flying.

 

Any ideas?

[Joyride]

Using the ME you can add F10 menu items specific to that group (client) and then have a unique flag for each group/client when they press the F10 command.

 

For example, you add an F10 menu item "Request Sit Rep" to each and every client, using the "Radio Item Add for Group". If 10 clients, you'd have 10 lines of triggers, with 10 unique flags. When one of those flags turns true, there is a second trigger line which sends a "Group Msg" to that group (client) only.

 

A bit cumbersome if you have numerous F10 messages and many clients, but if only a "sit rep" type situation this works very quickly easily.

 

Where I use scripts for this is when I get into F10 submenus, which the ME GUI can't do.

[Joyride]

Thanks Druid, unless I am over thinking this, how do I get the group ID of the person that initiated the Comm message?

 

Example:

Player A hits \ to open comms menu, presses F10, selects option to request data.

 

Is this tied to an event ID or something else I can get the group ID of the comms initiator?

(To many client aircraft to enter these in the mission editor, need to use LUA)

 

I went down the same road trying to tie the F10 keypress to an "event" so that an "initiator" could be ID'ed, but not aware of any way to do this. If someone else has figured it out this would be handy, indeed.

[number3]

Using the ME you can add F10 menu items specific to that group (client) and then have a unique flag for each group/client when they press the F10 command.

 

For example, you add an F10 menu item "Request Sit Rep" to each and every client, using the "Radio Item Add for Group". If 10 clients, you'd have 10 lines of triggers, with 10 unique flags. When one of those flags turns true, there is a second trigger line which sends a "Group Msg" to that group (client) only.

 

A bit cumbersome if you have numerous F10 messages and many clients, but if only a "sit rep" type situation this works very quickly easily.

 

Where I use scripts for this is when I get into F10 submenus, which the ME GUI can't do.

 

Thanks. I was hoping to avoid that solution, but whatever works.

 

I'm guessing that you are using a continuous trigger to monitor the status of the flag and once triggered, you set the flag back to zero (or whatever value).

 

In that case is there a performance hit adding many continuous triggers to the ME? Would it be better to call mist.scheduleFunction(), where you can control the period of function calls?

[Joyride]

I'm guessing that you are using a continuous trigger to monitor the status of the flag and once triggered, you set the flag back to zero (or whatever value).

 

No continuous trigger, you can use a switched condition. So, if Client #13 pushes F10 that turned flag #683 true, message is sent, and same trigger turns flag #683 false. All set to repeat again if everything is switched condition.

[ENO]

So glad I found this. Never used the radio item add before and couldn't get my head around it. Thanks guys!