[FIXED B998.3] Still SLBM overload

[MrGandi]

Just updated to B998.2

I'm wondering why my subs are still firing two salvos of SLBMs at one target.
Every time the MIRVs separate midair the sub fires a second SLBM.
Is it a wrong WRA setting?

Please find an updated test scenario and a screenshot in case it's different behavior on your side.
Just load the scenario and assign one of of the subs to the strike mission.

Thanks

[TyphoonFr]

Hello,
This is not a bad WRA setting

The is a missile that has 6 nuclear warheads "SS-N-32 MIRV [150kT Nuclear]".

When you fire 1 "SS-N-32 [6MIRVx150kT nuclear]", at some point the heads separate and your missile "SS-N-32 [6MIRVx150kT nuclear]" disappears to become 6 nuclear warheads "SS-N-32 MIRV [150kT Nuclear]".
Besides, I do not see the utility, unless we can assign a different target to each head.

In the WRA you have set 1 missile "SS-N-32 [6 MIRVx150kT nuclear]" per target until destroyed.
As your missile "SS-N-32 [6 MIRVx150kT nuclear]" has disappeared and the target is not destroyed your submarine fires a new missile "SS-N-32 (6 MIRVx150kT nuclear)"

The "UGM-133 Trident II D5 [8 MIRV x W76 100kT Nuclear]" missile has 8 heads "UGM-133 Trident II D5 MIRV [W76 100kT Nuclear]"

Look at the number to the left of your target after your second missile is leaving. This is the number of ammunition that is heading towards your target.
With "SS-N-32 [6 MIRVx150kT nuclear]" you will see 7 (1 missile + 6 nuclear heads). With a Trident will be 9 (1missile + 8 nuclear warheads).

For SLBM muti-head I shoot in manual (Shift F1).

It is already good that in Command, a Trident moves towards the target and destroys it, in reality the tests sometimes reveal surprises.
With nuclear missiles, it is only the day we use them that we will know if they are so effective. In the meantime everything is only surpertition.

[font="Arial"][/font][font="Arial"][/font]

[Cik]

the AI does not recognize the MIRV units as missiles in flight to the target due to how the RV reentry phase works.

you may want to just manually assign targets instead which will fix the problem.

[ComDev]

Thanks, bug has been reproduced and fixed in B998.3 [8D]