Into the Valley of Tears scenario broken?

[Phoenix100]

Is this scenario broken, I wonder? Into the Valley of Tears, from the 1973 war. It says to play from Side A but when I try that side B does nothing, ends up in virtually the same starting positions at scenario end. It tries to bridge the ditch with forward units and those success or fail messages continue throughout the scenario, but it makes no attempt to move its main force forward. Is it broken? Thanks.

[berto]

Yes, broken against an attacker AI. The remedy will be to SAI the scenario in CSME v3.00 due out hopefully later this year. (The imminent v2.30 will be upgraded to latest standards, including full CSEE [Campaign Series Event Engine] and SAI [Scripted AI] capabilities, but with very few actual scripts.)

[Phoenix100]

Ah. But did it ever work? It definitely says to play it as Side A (defenders). I'm just coming back to try the game again, having been playing lots of CSV, but does this mean that all scenarios in the game where the AI must attack don't really work?

The 'imminent' update won't cure this, I suppose, without an actual attacking script (which will come later with version 3?). But, when is 'imminent' - this month?

Thanks, Berto

[berto]

The fundamental problem with this scenario IIRC is that the legacy AI cannot "see" across waterways and AT ditches, therefore cannot "see" Objectives on the far side. The legacy AI is totally Objectives oriented. No see Objectives, no movement.

In that sense, no, it never did work (for Side A defender human play).

A kludge is to locate low-value Objectives at the crossing points. The legacy AI will be drawn to those points. Once there, the LAI can then "see" across the waterway/AT ditches more distant, "real" Objectives on the far side, and will continue forward movement.

In the new CSEE/SAI system, the new SAI is not limited to seeking out Objectives; forces can be directed anywhere for any purpose.

If this scenario is marked incorrectly for Side A (defender) play, we will fix that for v2.30. The complete fix will come in v3.00.

Sorry for the trouble.

[Phoenix100]

I see. Ok. Thanks.