Moved to another Patch 06 - Public Beta - Build 1108p3 updated 10 July

[Sardaukar]

But it says on unit screen that march direction is: E....which is how the tick shows. Seems they are taking a detour.

[berto]

ORIGINAL: Sardaukar

But it says on unit screen that march direction is: E....which is how the tick shows. Seems they are taking a detour.

Good point. The move tick does indeed match the displayed March Direction: E.

Nevertheless, the 21st Medium FA Bn and all other LCUs in that group did in fact move west, directly down the secondary road to Paingkyon, with no detour at all.

save

By and by, see this thread for a corroborative screenshot.

Seems like there is a bug: a mismatch between the march orders and actual movement on the one hand, and the move tick and displayed March Direction on the other.

[michaelm75au]

The 'tick' is based on the march direction. Which is calculated when you order the unit to march and then gets updated when the unit moves hex.

[berto]

ORIGINAL: michaelm

The 'tick' is based on the march direction. Which is calculated when you order the unit to march and then gets updated when the unit moves hex.

I can assure you that, after gathering at Chiang Mai, all units were ordered to march west, never east. For day after day lasting over a week and more.

In other words, the sequence was:

--units at Chiang Mai
--ordered them to march west, directly down the secondary road, to Paingkyon
--after several days, they moved one hex west, as intended
--the move tick, and the March Direction, displayed east
--the units continued their westward march, several days later arriving at Paingkyon one hex to the west, with no detour or delay evident

And referring back to my earlier example, in no way did I order any LCUs at Chiang Mai to move southeast (instead, directly to Paingkyon, to the west). But here is what the map showed:



???

[michaelm75au]

Not doubting you, just saying how it works.
I will look at the save when I get the chance.[:)]

[berto]

Thanks for the promised look.

Grand campaign PBEMers may be reluctant to risk trying betas.

Since for now I only play short-duration scenarios, hence I have less to lose, you can count on me to play test all beta releases going forward. And to calls 'em as I sees 'em. [;)]

[michaelm75au]

The units are moving as directed despite the march direction indicating the opposite. The initial direction may be picking the direction of least resistance, which would be the trail not across the river.
I'll cancel the movement of the units and try to set it myself to track the path.

Question: Did these units start in the current hex (of save) or from further away?
When I canceled move and then set it again, they directly moved West as expected. This is the way I expect a single move to work.
Okay I went back re-read last post.

Reloaded your save from 31 Jan and played forward. The march direction remained correct 'W' on the units, so not sure when/why it changed to 'E'.
Do you have the save from 12 Feb, the one before the one you posted above? Want to try to track down when it changed to 'E'.

[berto]

Pardon me if, after rereading the above, you've figured it out, but ...

ORIGINAL: michaelm

The units are moving as directed despite the march direction indicating the opposite. The initial direction may be picking the direction of least resistance, which would be the trail not across the river.

But the "direction of least resistance" would have them moving away from the Salween River. One way or the other (one route or the other), they will eventually have to cross the Salween to get to Paingkyon. As you can see from the map, the Salween extends from the Bay of Bengal north through Burma and on into southern China.

Question: Did these units start in the current hex (of save) or from further away?

All units in the vicinity of Chiang Mai originally strategic moved via rail up from Bangkok. After staggered arrivals at Chiang Mai (because I moved them, not as a single group, but in subgroups days apart), in all cases units were ordered to move westward, either to hex 57,53 (midway between Chiang Mai & Paingkyon), or to hex 56,53, Paingkyon. (Always in Move Op Mode, never Combat.) When I observed the late arrivals apparently moving southeast (as described above), I cancelled move orders for the earlier arrivals. They stayed put in 57,53 awaiting the arrival of the laggards. When all units had assembled in 57,53 I ordered them to march west to Paingkyon. That's when I observed the east-pointing move tick. As reported, subsequent to that, they moved west (despite what the move tick and March Direction showed).

I should add that throughout, I have been doublechecking all march orders, Op Modes, etc. Cycling through every unit, checking to make sure one by one.

I've been play testing this one scenario for the last couple of months. Before the current beta build, I tried the 1108k7 build, and before that the latest official release. I've never observed these quirks before. Could be a recent glitch.

[berto]

ORIGINAL: michaelm

Reloaded your save from 31 Jan and played forward. The march direction remained correct 'W' on the units, so not sure when/why it changed to 'E'.
Do you have the save from 12 Feb, the one before the one you posted above? Want to try to track down when it changed to 'E'.

The only saves I have are in this thread or in the Burma scenario thread.

Or you could just visit this site.

The last post provided a more detailed account of how I got from there to here.

[hunchback77]

ORIGINAL: michaelm

I may compromise (as usual) by just showing the 'green dots' of the hexes within the supply range.
You wont know if the path ended due to running out of supply points or presence of enemy unit.

I like the numbers instead of the green dots Michael, it helps in understanding the flow of supply. Please keep it as is for AI games and add the option to turn it off in PBEM games. Thank you.

[berto]

ORIGINAL: hunchback77

ORIGINAL: michaelm

I may compromise (as usual) by just showing the 'green dots' of the hexes within the supply range.
You wont know if the path ended due to running out of supply points or presence of enemy unit.

I like the numbers instead of the green dots Michael, it helps in understanding the flow of supply. Please keep it as is for AI games and add the option to turn it off in PBEM games. Thank you.

+1

My position exactly.

Although I don't like to bean count my way through the Fog of War, I can resist the temptation to inspect the numbers too closely. But, yeah, they are of immense help in understanding supply. It would be a shame to lose them.

[Buck Beach]

ORIGINAL: berto

ORIGINAL: hunchback77

ORIGINAL: michaelm

I may compromise (as usual) by just showing the 'green dots' of the hexes within the supply range.
You wont know if the path ended due to running out of supply points or presence of enemy unit.

I like the numbers instead of the green dots Michael, it helps in understanding the flow of supply. Please keep it as is for AI games and add the option to turn it off in PBEM games. Thank you.

+1

My position exactly.

Although I don't like to bean count my way through the Fog of War, I can resist the temptation to inspect the numbers too closely. But, yeah, they are of immense help in understanding supply. It would be a shame to lose them.

+2

[sspahr]

ORIGINAL: KHawk

That is kind of why I am asking. I go in at 12000 just to be safe.

There has been changes with the attack bombers and torpedo bombers.

Recently I tried using fighters at 12000 and they seemed to Level Bomb.

Was hoping to get the facts.

KHawk

I've noticed the same since changing to 1108k9 from 1108k7. Also, dive bombers were level bombing from 16000ft when I was playing with 1108k9 last night, so something has changed that's not in the notes.

[michaelm75au]

ORIGINAL: sspahr

ORIGINAL: KHawk

That is kind of why I am asking. I go in at 12000 just to be safe.

There has been changes with the attack bombers and torpedo bombers.

Recently I tried using fighters at 12000 and they seemed to Level Bomb.

Was hoping to get the facts.

KHawk

I've noticed the same since changing to 1108k9 from 1108k7. Also, dive bombers were level bombing from 16000ft when I was playing with 1108k9 last night, so something has changed that's not in the notes.

Hasn't been any changes for air attacks between k7 and k9.
When I have a chance, I'll update the advised table.

[sspahr]

ORIGINAL: michaelm
Hasn't been any changes for air attacks between k7 and k9.
When I have a chance, I'll update the advised table.

Here are the combat reports pertaining to the dive bombers appearing to level bomb when set to 16000ft that I referred to. I suppose they could be glide bombing with the attack altitudes not being updated for the report.

--------------------------------------------------------------------------------
Morning Air attack on TF, near Akyab at 54,45

Weather in hex: Thunderstorms

Raid spotted at 26 NM, estimated altitude 20,000 feet.
Estimated time to target is 10 minutes

Japanese aircraft
Ki-27b Nate x 7
Ki-43-IIa Oscar x 3



Allied aircraft
Hurricane IIc Trop x 16
Vengeance I x 16


Japanese aircraft losses
Ki-27b Nate: 1 destroyed

Allied aircraft losses
Vengeance I: 1 damaged

Japanese Ships
xAK Teiren Maru
xAK Tonan Maru
xAK Nansin Maru



Aircraft Attacking:
16 x Vengeance I bombing from 16000 feet
Naval Attack: 2 x 500 lb SAP Bomb, 2 x 250 lb SAP Bomb

CAP engaged:
25th Sentai with Ki-43-IIa Oscar (0 airborne, 0 on standby, 2 scrambling)
(1 plane(s) diverted to support CAP in hex.)
1 plane(s) not yet engaged, 0 being recalled, 0 out of immediate contact.
Group patrol altitude is 13000 , scrambling fighters between 14000 and 15000.
Time for all group planes to reach interception is 37 minutes
2 planes vectored on to bombers
244th Sentai with Ki-27b Nate (0 airborne, 0 on standby, 7 scrambling)
Group patrol altitude is 7000 , scrambling fighters between 8000 and 14000.
Time for all group planes to reach interception is 40 minutes
1 planes vectored on to bombers
--------------------------------------------------------------------------------
Afternoon Air attack on TF, near Akyab at 54,45

Weather in hex: Light cloud

Raid spotted at 19 NM, estimated altitude 20,000 feet.
Estimated time to target is 7 minutes

Japanese aircraft
Ki-27b Nate x 13
Ki-43-IIa Oscar x 5



Allied aircraft
Hurricane IIc Trop x 14
Vengeance I x 15


No Japanese losses

Allied aircraft losses
Hurricane IIc Trop: 1 destroyed
Vengeance I: 3 damaged

Japanese Ships
CL Yubari, Bomb hits 1, on fire
xAP Tenzan Maru, Bomb hits 1, on fire



Aircraft Attacking:
15 x Vengeance I bombing from 16000 feet
Naval Attack: 2 x 500 lb SAP Bomb, 2 x 250 lb SAP Bomb

CAP engaged:
25th Sentai with Ki-43-IIa Oscar (1 airborne, 0 on standby, 0 scrambling)
(5 plane(s) diverted to support CAP in hex.)
1 plane(s) intercepting now.
0 plane(s) not yet engaged, 4 being recalled, 0 out of immediate contact.
Group patrol altitude is 13000
Time for all group planes to reach interception is 2 minutes
244th Sentai with Ki-27b Nate (0 airborne, 0 on standby, 0 scrambling)
(13 plane(s) diverted to support CAP in hex.)
0 plane(s) not yet engaged, 9 being recalled, 4 out of immediate contact.
Group patrol altitude is 7000
Time for all group planes to reach interception is 27 minutes
4 planes vectored on to bombers

Heavy smoke from fires obscuring CL Yubari
Heavy smoke from fires obscuring xAP Tenzan Maru


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

[witpqs]

ORIGINAL: michaelm

BTW, has anyone tried the password change function in last build?

I thought it might be useful as I have had requests to change the password in the past.

I can't find the function. Am I looking in the right place?

[michaelm75au]

ITS GONE!!![&:]

It was there. Honest.

Found it.
My error. Changed a variable and forgot to update the save screen.

It will be back on the next build.

[witpqs]

ORIGINAL: michaelm

ITS GONE!!![&:]

Oh no, I broke it! [X(]

[:D]

[michaelm75au]

ORIGINAL: sspahr

ORIGINAL: michaelm
Hasn't been any changes for air attacks between k7 and k9.
When I have a chance, I'll update the advised table.

Here are the combat reports pertaining to the dive bombers appearing to level bomb when set to 16000ft that I referred to. I suppose they could be glide bombing with the attack altitudes not being updated for the report.

--------------------------------------------------------------------------------
Morning Air attack on TF, near Akyab at 54,45

Weather in hex: Thunderstorms

Raid spotted at 26 NM, estimated altitude 20,000 feet.
Estimated time to target is 10 minutes

Japanese aircraft
Ki-27b Nate x 7
Ki-43-IIa Oscar x 3



Allied aircraft
Hurricane IIc Trop x 16
Vengeance I x 16


Japanese aircraft losses
Ki-27b Nate: 1 destroyed

Allied aircraft losses
Vengeance I: 1 damaged

Japanese Ships
xAK Teiren Maru
xAK Tonan Maru
xAK Nansin Maru



Aircraft Attacking:
16 x Vengeance I bombing from 16000 feet
Naval Attack: 2 x 500 lb SAP Bomb, 2 x 250 lb SAP Bomb

CAP engaged:
25th Sentai with Ki-43-IIa Oscar (0 airborne, 0 on standby, 2 scrambling)
(1 plane(s) diverted to support CAP in hex.)
1 plane(s) not yet engaged, 0 being recalled, 0 out of immediate contact.
Group patrol altitude is 13000 , scrambling fighters between 14000 and 15000.
Time for all group planes to reach interception is 37 minutes
2 planes vectored on to bombers
244th Sentai with Ki-27b Nate (0 airborne, 0 on standby, 7 scrambling)
Group patrol altitude is 7000 , scrambling fighters between 8000 and 14000.
Time for all group planes to reach interception is 40 minutes
1 planes vectored on to bombers
--------------------------------------------------------------------------------
Afternoon Air attack on TF, near Akyab at 54,45

Weather in hex: Light cloud

Raid spotted at 19 NM, estimated altitude 20,000 feet.
Estimated time to target is 7 minutes

Japanese aircraft
Ki-27b Nate x 13
Ki-43-IIa Oscar x 5



Allied aircraft
Hurricane IIc Trop x 14
Vengeance I x 15


No Japanese losses

Allied aircraft losses
Hurricane IIc Trop: 1 destroyed
Vengeance I: 3 damaged

Japanese Ships
CL Yubari, Bomb hits 1, on fire
xAP Tenzan Maru, Bomb hits 1, on fire



Aircraft Attacking:
15 x Vengeance I bombing from 16000 feet
Naval Attack: 2 x 500 lb SAP Bomb, 2 x 250 lb SAP Bomb

CAP engaged:
25th Sentai with Ki-43-IIa Oscar (1 airborne, 0 on standby, 0 scrambling)
(5 plane(s) diverted to support CAP in hex.)
1 plane(s) intercepting now.
0 plane(s) not yet engaged, 4 being recalled, 0 out of immediate contact.
Group patrol altitude is 13000
Time for all group planes to reach interception is 2 minutes
244th Sentai with Ki-27b Nate (0 airborne, 0 on standby, 0 scrambling)
(13 plane(s) diverted to support CAP in hex.)
0 plane(s) not yet engaged, 9 being recalled, 4 out of immediate contact.
Group patrol altitude is 7000
Time for all group planes to reach interception is 27 minutes
4 planes vectored on to bombers

Heavy smoke from fires obscuring CL Yubari
Heavy smoke from fires obscuring xAP Tenzan Maru


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

Got a save?

[michaelm75au]

I got tired of trying to work out if the Burma Road was giving supply or not.

So I have added a line on the base screen of Tsuyung and Ledo/Rangoon to indicate that the 500 daily supply is being added.

Bottom line on the left hand side in case you can't see the colored box.