Customisation of MAWS-Slaved Countermeasure Release

Would you like the ability to set the release pattern for MAWS-slaved CMs?
  • Yes
  • No
0 voters
If yes, which method would you prefer (please read the suggestion before choosing an answer)
  • MAWS uses the periodic countermeasure release settings
  • MAWS has its own customisable release setting
  • A secret third thing
  • I voted no
0 voters

At present, the Missile Approach Warning Systems in-game can have countermeasure slaving enabled, in which case they use the below release pattern:

Spoiler

IMG_0789

When both flares and chaff are selected as countermeasures, the MAWS will release 32 countermeasures over the course of 4 seconds (which in my experience is the typical release time).

While some aircraft can afford this, others are more limited and as a result 2 MAWS alerts can deplete their entire countermeasure stores. However, over a longer match even aircraft with a relatively high number of countermeasures can also find themselves running out, and with a large number of missiles launched on both sides it might not even take that long.

Most people (that I’m aware of) simply disable slaving and use the MAWS alert to help with awareness, dropping countermeasures themselves as they feel is needed.

I propose that the MAWS slaving should be customisable, allowing people to set patterns that work best for them and the aircraft they use.

One option is for the MAWS to use the periodic countermeasure release settings we already have in-game. This wouldn’t require any new UI elements, as the parameters can already be set in the spawn screen. This would require the player to tweak the settings each time they changed aircraft which might not be perfectly convenient (I personally would lean towards suggesting the addition of player-made presets to help streamline the process).

Another option is for each MAWS to have its own customisable release settings. This would “save” the pattern, and for planes that share a system (such as the Typhoon) the pattern would be shared across the relevant aircraft. This would allow for release patterns that work best for each specific aircraft (for example, the high CM count on the Harrier GR.7 would allow for a larger density to be released, while the Typhoon’s relatively smaller count can release more sparingly). The downside here would be the potential UI clutter, either requiring space in the spawn menu or the options menu.

I welcome alternative ideas for the implementation as well, these two are the ones that come to mind for me and I’d be happy to hear more input on how the feature could realistically function.

In summary, allowing the players to choose the release pattern for CMs slaved to the MAWS system would turn the feature from mostly being an inconvenience to being an attractive aspect of aircraft that carry such systems.

Thank you for your consideration.

1 Like

Was needed a year ago, so please Gaijin, add this ASAP

2 Likes

Is this historical or does this not exsist?
If this can be done IRL then +1
if it can’t, -1

i’d like to see some sort of fusion with the rwr as well so its not dumping flares for radar guided missiles and not dumping chaff for ir guided missiles

They need to fix MAWS so it doesn’t trigger off flying into friendly chaff first. As long as this isn’t fixed I’ll keep the MAWS slaving disabled.
It’s a good suggestion nonetheless.

What is about different automatic countermeasure release program against different threats under control of combined MAW+RWR+… sensors?

This will mean multiple countermeasure programs (or patterns). There is not only the difference between radar and infra-red homing missiles, but the difference between different missile systems. How player would configure them? Should entire logic of automatic countermeasure release be configured? I can’t image how UI should look like in this case.

1 Like

Just an option to slave MAWS to countermeasure series program would be nice. Countermeasure series already exist and offer enough customization/options.

image

If there are 5 different countermeasure programs for different threats?
Panel for change settings for each?
What if player is not happy that the same chaff release program is used against AIM-7F (SARH illumination detected from F-4J) and AIM-120 and also would prefer to not use any automatic chaff release against AIM-7E (SARH illumination detected from F-4E)?

The 5 different countermeasure programs for different threats should remain the same. The only thing that should change is the amount of countermeasures being used left up to the players. The biggest complaint about the MAWS implementation is that it goes through half of your countermeasures just to deal with one threat. Countermeasure series can reduce the amount of countermeasures used while sufficiently decoying the threat.

I think this is something that should be considered only after implementation of slaving MAWS to periodic countermeasure series. Complaints regarding countermeasure programs may die down after the implementation of slaving MAWS to periodic countermeasure series and players may find it sufficient for their needs. It is possible the extra features requested may be resolved with the implementation of countermeasure series for MAWS.