Matrix Games Forums

Thanks for the clarification and the scenario


Logged 16972

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.

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?

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)

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.

OK, thanks for the answers.

blu3s wrote: Thu Oct 09, 2025 3:25 pm 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.

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

blu3s wrote: Thu Oct 09, 2025 2:59 pm 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)

I finally got home and was able to test my giant scenario as per your suggestion. Nope. Grrrr. I'm on beta 1728.2. And although it worked as suggested on a small test scenario I built, it is still not working on this large scenario of mine.

As indicated previously, the long range missiles are no longer firing early as per the bug in the previous patches, but the N Korean artillery and MLRS along the DMZ are still firing around the 2 minute mark instead of waiting for their mission start times. I set the WRA to do not use in self defense, as suggested, and they're still firing.

Any other suggestions anyone?

....so we're back to "wierd stuff that happens only on that gigantic scenario" ?

Dimitris wrote: Tue Oct 14, 2025 2:25 pm ....so we're back to "wierd stuff that happens only on that gigantic scenario" ?

Lol. It appears so. Since the bug first appeared in 1676, for some reason I can't get this scenario to work right. I changed all the North Korean global WPA for the artillery and MLRS along the DMZ to do not use in self defense for all enemy land units and it still didn't stop them from firing at about the 2 minute mark.

Are there other WPA resets that might be responsible now in light of the recent suggestions and fixes I should try?

Thanks.

Okay, I think I know what's going on and that this may still be a bug.

I had run a small test scenario with North Korean artillery and MLRS along the DMZ within range of land units south of the DMZ. By clicking on 'do not fire in self defense' in the unit WRA, it worked just as mentioned in this post recently. But when I did that in my gigantic scenario, I adjusted the WRA for those units from the main 'add edit sides' menu. That did not work.

So today I went in and adjusted the self defense WRA for each unit along the DMZ in my giant scenario and that did work. But it was a time consuming pain.

So the bug may be that WRA settings for artillery and MLRS units (and who knows what else) are not being inherited by individual units like they should be. Or am I missing something?

Thanks.

Mmm units do not inherit WRA settings from other unit types, they inherit from groups, missions, or the general side WRA

blu3s wrote: Thu Oct 16, 2025 12:26 pm Mmm units do not inherit WRA settings from other unit types, they inherit from groups, missions, or the general side WRA

Right. So what I'm saying is that in my giant scenario, when I set the WRA for 'do not use in self defense' for the artillery and MLRS units along the DMZ from the general side WRA menu, it did not work. The units kept ignoring that and opened fire in self defense at the 2 minute mark. But when I directly set the WRA for each unit, then it finally worked.

Shouldn't it have worked for them by setting the side WRA?

I'll have a look but yes, if your units are set to inherit values, they should have inherited the value from the side WRA