William Betson wrote: Sun Jan 25, 2026 3:03 am If anyone has achieved success against the T80s, I'd be interested to know how that person did it.

Nuke them!

Consider this little trick:
Make a very short move, perhaps one hex, using Hasty.
Then, in the same command list, do all the rest of the overall move using either Deliberate or Assault.

That might speed up the overall move. I don't think this little workaround is prevented yet, but I know the dev ...

I only played campaigns during the private beta because you folks wanted me to. If I had my way, I would skip them.

I definitely agree with Zumwalt. This is a classic case of an infinite software loop.

I spotted and reported the same thing several times during the beta. Seems like the bug still exists.

Eventually, the unit gets out of the infinite loop generally when the opposing units move, or the looping unit is killed!

I think the filename in the link to the public beta installer is incorrect in the first post. That para is "There's a new public beta update installer available at the following download link: HERE." After a bit of sleuthing, I think the link should be to FlashpointCampaignsSouthernStorm-UpdateComp ...

Update to add that you can also create scenarios set in different years by modifying the nationals data files (location is for a steam install):
C:\Program Files (x86)\Steam\steamapps\common\Flashpoint Campaigns Southern Storm\Modules\Common\Data

In the latest patch I think we added the ...

OK, I understand. To paraphrase, I think you are saying that giving the AI (really the scenario designer) the ability to do optimum placements makes up for shortcomings in the capability of the AI. As you say "it cannot properly select the best terrain for defense or the best field of vision." That ...

Scenario: High Sticking
I have found that the AI has a definite advantage in this scenario (and possibly others). It appears that the AI can make initial deployments that are simply not available to a human player. Some of these AI deployments are extremely advantageous. For example, the AI places ...

By the way, the changes are excellent. I really appreciate the SOP manager improvements. The little graphics effects are nice, but not really essential as far as I am concerned. All the bugfixes have definitely improved things. I like the Canadian scenarios, being as both my spousal unit and I were ...

Thanks!

The installer was a bit confused by the identical release number, but all is good.

I note that the release number for this complete release is the same as the earlier beta version. Both are 2.1.3.7735. Is there any difference between the two releases, other than the fact that one was beta?

Presumably via a spotter. The mortar certainly had no LOS, being as it was dug-in in deep defilade. I let the FSCC do all the work, only playing around with the SOP. I wouldn't expect the FSCC to assign a blind neutralizing fire mission.

Yeah, that is my read as well, from some research. Still, the targets selected were all mobile (that is, not dug-in, just stopped briefly). Some of the lighter armoured stuff like recon or headquarters units should have suffered more than they did.

I suppose one of the aspects of my question is ...

Having never fired a mortar, I have a question about the effectiveness of the mortars in the game, specifically the M106A2 American self-propelled mortars. They are 107 mm (4.5 inch) mortars that should be able to drop considerable ordnance on a target. In several games, the mortars fire as ...

I am encountering a very similar error in "Brothers in Arms" scenario. Also running 2.1.2.7120 and the update check tells me I'm running on the latest version.

Three Czech tanks units spawned in the middle of the NATO controlled area and ran rampage in my rear. The bug does not appear to be fixed ...

Thanks, Jeff. I had not considered the direct fire mode for the artillery.

So, HOLD and ON CALL are incompatible orders. Perhaps prevent the user (or the AI) from issuing both simultaneously. Are there any other pairs or sets of incompatible orders?

Anyway, I do not want to stir up a hornet's ...

Thanks, Charles. That still leaves the question of why the AI could not change the order. I will leave that with you and await the next update.

I appreciate your prompt responses!

Just to be clear, I did not set up the HOLD, then ON CALL. The scenario or the AI did it. The save game files are from a "computer plays both sides" game. I did nothing to any unit. I did pause and resume several times to save the game, but that is the only interaction I had with the battle progress ...

I thought the HOLD order means that a unit will dig in and defend vigorously if attacked. In addition, the ON CALL order should mean that the unit is prepared to accept fire missions from whoever issues them. It would seem logical that an artillery unit could be subject to holding a position, and ...