[Fixed + WAD]1.08 Build 1676 Enemy Mission Start Times Ignored

[blu3s]

Thanks for the clarification and the scenario


Logged 16972

[Nikel]

I found another example.

Russian sub Severodvinsk armed with UGST torpedos.

2 training targets, a sub and a ship.

Mission to strike the 2 targets, activated 5 minutes after the scenario start.

However the training sub attack will start inmediately, while the surface ship will only be attacked when the mission starts.

There is no interference due to 2 targets, if you remove the sub, the attack on the ship will happen when the mission is activated. If you remove the ship, the attack on the sub starts inmmediately.

TT.gif (2.72 MiB) Viewed 93 times

[Nikel]

The Belgorod, armed with a nuclear torpedo, Status-6, that may attack land targets.

Is also correct, starting the attack when the mission is activated.

So the type of weapon torpedo is affected by the bug only attacking other subs, but not attacking surface or land targets?

BT.gif (1.65 MiB) Viewed 82 times

[blu3s]

The case with the mortar is WAD. The mortar has self-defense set to max range, so that's why the weapon is firing. Change the self-defense range and it should respect the activation time. (At least it does on B1746)

[blu3s]

And the case for the sub is also WAD, the (hostile) submarines are treated as opp targets regardless of the doctrine (that has been that way during at least 8 years now)


So regarding the scenario, check the WRA of the arty units, missiles, etc to make sure they are not firing in self-defense.

[Nikel]

OK, thanks for the answers.

[Tred]

And the case for the sub is also WAD, the (hostile) submarines are treated as opp targets regardless of the doctrine (that has been that way during at least 8 years now)


So regarding the scenario, check the WRA of the arty units, missiles, etc to make sure they are not firing in self-defense.

Hmm. Thank you. I'm out of town for a while, but I'll try that when I get home. Anyone know why that might suddenly be the case after the 1676 patch, but didn't do it before then?

Thanks again everyone.

[blu3s]

Because self-defense range was not working for some unit types and now that is fixed