This actually works pretty well now, I think.
The only issue is that the change so that ready times now are added to the preset time, can make older scenarios harder than the desinger intended, but that is easily fixed in the editor.

Phalanx only mange 1 or 2 shots against subsonic missiles and each shot only has a 1% chance to hit.
The test scenario has two diffrent types of missiles but with the same result.

In this test, the mission cap1 has the WRA for self defence against Guided Weapon is set to: Do not use
It is inherited by the flights assigned to the mission, but not by the individual aircrafts

They are suppose to wait until the mission is activated. Many scenarios has inactive missions at the start. In this example the mission designer has manualy set waypoints that the ships should follow until a specific time when the mission is activated.

Ships that are assigned to inactive missions, RTB at the begining of the scenario

This is an old annoying bug.

https://forums.matrixgames.com/viewtopi ... 2#p5187962

Aircrafts doesn't fire Anti Radiation missiles at ships (with radar on) automatically anymore. I tried with SEAD mission and strike/intercept missions. Manually you can.

Aircrafts on intercept or strike mission sometimes ignore bingo and continue to attack until they run out of fuel.

In this save a few Iranian F-14 crashes because of this

This is still an issue with 1825.15

This is basicly fixed in 1825.2, except that the readytime of the new loadout will override the one the mission designer set.
So in this example if you set an loadout with a 3h readytime it will override the 5hours the mission designer intended for the Hornets to become available

No I don't

Here's a comparison to 1776

Much slower here to

Changing loadouts causes strange inconsistent ready times.

One example: If the loadout for the two F/A-18C with time to ready 5 hrs is changed to: AGM-88BHarm Short-Range, the time to ready will be 1 hr but it should be 6 hrs

The new variable burnout speed on boast-coast weapon is not saved after creating a scenario.

The submitted test scenario was created with the opion ticked, but it doesn't save.
To test you can open the test scenario in editor mode and enable the option: variable burnout speed on boast-coast weapon ...

Looks good

Okay, I believe that I understand it now.









But in this example the ship turns on its OECM, thats why it say Jamming next to the missiles. But this has nothing to do with the 20% DECM protection. It will get that even if the OECM is forced off.



This sensor is both OECM and DECM at the ...

Here is an example where OECM from ships was usefull in attack.
Every amraam got jammed and failed to lock on (after going pitbull) to incoming russian anti ship missiles because of OECM

Another video. OECM off in the Spruance. Tu-22M not jammed with radars on, will detect the warship with precision and fast.

After the missiles are launched, the Spruance will turn them on in defense mode jamming the russian AC and the missiles. In this case was successful, it is the same ...

The changes are reflected

The settings under the General tab that is not set to inherited changes when cloning a mission.

v 1776