Small Scen VS AI

[tarkalak]

Double post.

[tarkalak]

These are the combat reports for two attacks I did on Moulmein. Most of the loses were taken by a chines Prov division and a horde of small (and crappy) units. The indian brigades that suffred in the last combat in Sittang are not yet fully healed at Rangoon, but I will probably push them forward anyway.


26.04.1942

---------------------------------------

Ground combat at Moulmein (55,55)

Allied Deliberate attack

Attacking force 27472 troops, 319 guns, 437 vehicles, Assault Value = 1104

Defending force 21959 troops, 142 guns, 100 vehicles, Assault Value = 389

Allied adjusted assault: 1361

Japanese adjusted defense: 757

Allied assault odds: 1 to 1 (fort level 3)

Allied Assault reduces fortifications to 2

Combat modifiers
Defender: terrain(+), forts(+), preparation(-)
Attacker:

Japanese ground losses:
1570 casualties reported
Squads: 0 destroyed, 70 disabled
Non Combat: 1 destroyed, 39 disabled
Engineers: 3 destroyed, 40 disabled
Guns lost 26 (1 destroyed, 25 disabled)

Allied ground losses:
2959 casualties reported
Squads: 15 destroyed, 257 disabled
Non Combat: 0 destroyed, 30 disabled
Engineers: 4 destroyed, 14 disabled
Guns lost 36 (2 destroyed, 34 disabled)
Vehicles lost 11 (1 destroyed, 10 disabled)


01.05.1942

---------------------------------------

Ground combat at Moulmein (55,55)

Allied Deliberate attack

Attacking force 31083 troops, 318 guns, 434 vehicles, Assault Value = 1207

Defending force 20851 troops, 140 guns, 100 vehicles, Assault Value = 279

Allied adjusted assault: 795

Japanese adjusted defense: 343

Allied assault odds: 2 to 1 (fort level 2)

Allied Assault reduces fortifications to 1

Combat modifiers
Defender: terrain(+), fatigue(-)
Attacker:

Japanese ground losses:
1976 casualties reported
Squads: 1 destroyed, 113 disabled
Non Combat: 0 destroyed, 86 disabled
Engineers: 62 destroyed, 6 disabled
Guns lost 17 (4 destroyed, 13 disabled)

Allied ground losses:
2274 casualties reported
Squads: 7 destroyed, 268 disabled
Non Combat: 2 destroyed, 22 disabled
Engineers: 3 destroyed, 13 disabled
Guns lost 22 (1 destroyed, 21 disabled)
Vehicles lost 16 (1 destroyed, 15 disabled)

[tarkalak]

And the next shock attack kicks them out. Well all of them exept for a single unit that stays at Moulmein and stops my tanks from pursuing.

I will sort out the units and start to pursuit.

Also my first (and only) dedicated engineer unit have made the treck from india to the Valey and is packing for Moulmein. That should help with the repair of the Airfield and with Forts.

Also I tried a sweep with the now trained recruits and they managed to lose 2 for 1 Oscar. No pilots were harmed though and one of the recruits got 4-5 XP for his kill. I will put them on CAP to train XP now.

[tarkalak]

. Double post.

[tarkalak]

The scenario is almost drawing to an End.

I found out, the hard way of course, that divided units, that are left to Upgrade allowed, might just take updates that don't have enough devices for all the A,B,C parts. End result: Cannot recombine.

Only the Chinese are dividable though.

[tarkalak]

Japanese sympatysers put the wrong road sign at Pegu!

I know that units might decide to take other roads to target (due to supply roads and stuff) but these guys were showing an arrow east.

So why did that happen and how to avoid it in the future?

[tarkalak]

Final Score.

[traskott]

[:)] Good scenario!! Now, time to move to the GC [:D]

[tarkalak]

[:D]

I think I will now do the Japanese side for Burma. GC for later.

[HansBolter]

They are taking along and convoluted road and trail route to the destination rather than through the dense terrain.

Sometimes the AI for routing does things like that. To avoid it you have to break the movement orders down to individual hexes rather than assigning a destination multiple hexes away.

[tarkalak]

This was not the case.

They went into Moulmein and ended their movement there.

The sequence of events was:
1. Those units (1/BFF, Chinese Div, one of the Burma Rifles and one of my HQs) were sitting in the dot base northeast of Sittang Bridge.
2. I ordered them to move to Chiang Mai, following 1/BFF.
3. They showed an arrow east as well as distance 0/92, Direction: E
4. After they walked 46+ miles they ended up at Sittang Bridge with: Target Chiang Mai, Distance Traveled 0/46, March direction SW.
5. A few days later they moved into Moulmein and had no move orders there.

So they didn't go towards Chiang Mai at all.

Also somewhere in between I reconquered Moumein. I doubt that this had any influence though.

[BBfanboy]

ORIGINAL: tarkalak

This was not the case.

They went into Moulmein and ended their movement there.

The sequence of events was:
1. Those units (1/BFF, Chinese Div, one of the Burma Rifles and one of my HQs) were sitting in the dot base northeast of Sittang Bridge.
2. I ordered them to move to Chiang Mai, following 1/BFF.
3. They showed an arrow east as well as distance 0/92, Direction: E
4. After they walked 46+ miles they ended up at Sittang Bridge with: Target Chiang Mai, Distance Traveled 0/46, March direction SW.
5. A few days later they moved into Moulmein and had no move orders there.

So they didn't go towards Chiang Mai at all.

Also somewhere in between I reconquered Moumein. I doubt that this had any influence though.

First, know that the movement pip that is shown on the display is for the first unit in the stack. Others in the stack may not be following the same route and there is a much smaller movement pip for them, but your may need a magnifying glass to see it! Most commonly this happens when, in rough country, armoured units show their preference to follow roads while non-armoured unit may move cross-country because they can do so more efficiently.

In your case it looks like an unseen enemy unit moved into the adjoining hex that the units were marching toward. When a unit is set to move multiple hexes it will avoid the enemy until it gets to its target hex. The AI for LCU movement does not impose the detour until the LCUs are about to change hexes because the enemy unit may move out, leaving an empty hex that would allow the movement to continue.

When the enemy did not move out of that hex in time, your stack had to find a way around and that way was through Sittang Bridge.
So your units got to Sittang Bridge but by then, the enemy unit had changed hexes and now blocked the new path that the AI had calculated to get to Chiang Mai. At this point I think the AI did not have the coding to figure out another path so it stopped.

That is my take on it, with the few bits of info I have.

[tarkalak]

I will need to take more time looking at it, probably next week. I have set up the autosave to daily, so I should be able to check.

The 4 units were the only ones in Pyangoing, or whatever that hex east of Pegu is called.

I was so annoyed when I saw that that I actually reset to May 2nd and ordered the units to march to the next hex directly. They met no enemies there and I was able to set them to walk into Chiang Mai. However 2nd RTA managed to retake Chiang Mai and meet them at the hex west of Chiang Mai.

[BBfanboy]

AFAIK the Daily Autosave always saves in the same slot, so it overwrites itself each day.

[tarkalak]

This is with the -autosave switch.

"E:\Games\War in the Pacific Admiral's Edition\War in the Pacific Admiral Edition.exe" -cpu2 -dd_sw -multiaudio -deepColor -autosave -altFont -skipVideo

It creates a separate directory called autosave in the SAVE directory. You have to manually move and rename the saves to load them.

EDIT: But I did rewrite the saves since May 2nd, and the problem was after that. I will see if I can reproduce it when I have time.

[BBfanboy]

I did not know the -autosave switch did all that! Thanks for the explanation.

[tarkalak]

No problem! [:)]

Pay attention that when you use that switch the 000 (begining of current turn) and 001 (battle animations) autosaves will not be updated any more.
The 002 (end of last turn) will still be updated

[tarkalak]

Now I decided to go back and replay from the moment I think things went wrong with my Chiang Mai front.

I looked at the turns 28.04 ~ 02.05 in order to analyze the events.

I copied them to saveslots 008 to 011.

So I started the 29th turn and ordered the 1/BFF to Chiang Mai and the rest to follow them.

However when I played it the units did proceed hapily towards Chiang Mai. So mystery remains. [&:]

[tarkalak]

Now I decided to go back to the original April 30th turn.
On that turn I have already given the orders to move and the 1/BFF was 4 miles on track.

When I played the next dosen of turns or so, the 1/BFF and followers went to Sittang Bridge instead of towards Chiang Mai.

So, in conclusion, on the original April 29th turn, when I ordered the 1/BFF to switch march targets to Chiang Mai, they somehow decided to conyinue moving towards their old target of Moulmein. Even though they showed Chiang Mai as target AND they used the move speed (4 miles per day) as if they were really going there.



Mystery remains. [&:]

Can someone call Scooby-Doo. [:D]

[BBfanboy]

With a Leadership skill of 41, that guy doesn't know how to read a map!

Just a suggestion - I never use the follow command because sometimes it causes strange movement. Instead I use the move command for one unit, then for the other units "set all to this op mode (move)" and "set all to march (to the same target hex)".