How would I set the client's Su-25 to start in a specific state? and turn off mudspike callouts?

[Skuva]

I'm making a campaign in which some missions are mostly calm flights. But as there is an AWACS and some ground radars, when you play it you get the typical radio spam from AWACS every minute telling you there are bandits 300km away and RWR noises from friendly stations.

 

Most of it can be solved by manually toggling the "RWR Mode" and "Receive Mode". But I want those to be already properly set when the player hops into the aircraft. That means when the player starts the aircraft electronics the RWR is "off" (lock/launch only) and the Receive Mode is in "player's communication" state.

 

I also would like to know a way to shut up the wingman calls on mudspikes, If I set RWR to only function when I'm being painted I don't want the wingman calling out every single radar in the entire map every 10 seconds.

 

Is it possible to do any of this just through the editor, or will I need to get into lua scripting?

 

Complementary info:

The AWACS is already in a different frequency from the player's flight, but it still keeps getting in contact about bandits.

[Rudel_chw]

1 hour ago, Skuva said:

Most of it can be solved by manually toggling the "RWR Mode" and "Receive Mode". But I want those to be already properly set when the player hops into the aircraft. That means when the player starts the aircraft electronics the RWR is "off" (lock/launch only) and the Receive Mode is in "player's communication" state.

...

Is it possible to do any of this just through the editor, or will I need to get into lua scripting?

 

 

You can do it using the Editor's Trigger system, to set the RWR Mode you'd use one like this:

 

 

For the Comm Mode I used this:

 

 

How to interpret this: The command for the RWR Mode is 286, I got that from enabling a Mission Editor option that shows the commands on the Controls Page as a tooltip:

 

 

The option is on the /DCS/MissionEditor/MissionEditor.lua file and it's on its 4th line .. set it to true, like this:

 

OPTIONS_ADD_COMMAND_CODES_TO_TOOLTIP = true

 

For the Comm Mode, the set command is double because the key has to be pressed twice to get into the proper mode.

I'm attaching a sample mission where you can try this.

Best regards,

 

Eduardo

 

test.miz

Edited April 21, 2021 by Rudel_chw

[Skuva]

Thank you so much, this solves most of my problems and gave me some new ideas.

 

The mudspike AI callouts I managed to create a menu toggle. Adding "1. Silence=off" and "2. Silence=On" to the Triggered Actions of the player's flight, then creating a trigger to add radio options to mute and unmute (with their respective flags), and 2 other trigger for each of those flags with Task Push action. This completely mutes the wingman, but at least the player gets to choose when to hear it.

Edited April 24, 2021 by Skuva
adding solution for AI wingman