Guess the movt cost - K43

[Lethal]

Hi PzC Players,

Kharkov '43

Found an answer to one of my questions re movement of Primary Roads in the video I posted earlier.  
It is on the first image - K43HQmovt.

Have a look at K43HQmovt and guess what is the cost to move the HQ Unit, Soft Halftrack, Secondary Road across a Stream onto a Secondary Road hex.  

The result in-game is displayed in K43HQmovtResult.

PS The insert image option does not seem to work

[Xerxes77]

Hi PzC Players,

Kharkov '43

Found an answer to one of my questions re movement of Primary Roads in the video I posted earlier.  
It is on the first image - K43HQmovt.

Have a look at K43HQmovt and guess what is the cost to move the HQ Unit, Soft Halftrack, Secondary Road across a Stream onto a Secondary Road hex.  

The result in-game is displayed in K43HQmovtResult.

PS The insert image option does not seem to work

I think I know this one. Ground conditions do not affect hexsides, so you get the nominal Stream cost (30 MP) + the adjusted Secondary road value (5 *1.5 = 7 MP) to arrive at the final 37 MPs.

[Lethal]

That is very helpful. So, on the parameter data screen, trail, secondary and rail are modified by ground conditions. (Not movement by "Rail" - R). The hexside factors listed on the parameter data screen below these factors are not affected by ground conditions. Noting that Primary road has its own rule.

thx

[Xerxes77]

That is very helpful.  So, on the parameter data screen, trail, secondary and rail are modified by ground conditions.  (Not movement by "Rail" - R).  The hexside factors listed on the parameter data screen below these factors are not affected by ground conditions.  Noting  that Primary road has its own rule.

thx

That is my understanding, however I'm not 100% sure as I have not tested them all.

I've always found the terminology around hex sides confusing, as functionally there are either "border" or "crossing" features, i.e. streams and walls run along hex sides, but roads and rails cut through them. They are lumped together in the parameter data, but apparently it's the features that actually cross the surface of a hex that are affected by ground conditions.

[ComradeP]

Though I guessed it would be 37, it is still a bit odd as technically you would expect that the unit can't enter the hex by road. After all, there's no bridge.

On the other hand, that would mean all those scenarios in the USSR with streams without bridges would be even harder to move around on. That might be why the movement cost is Stream+secondary road modified by weather conditions, rounded down instead of Stream+Village modified by weather conditions.

[ComradeP]

After giving it some further thought: I've always used "movement cost=whatever it costs to cross the stream into the terrain type on the other side" when trying to determine movement cost when moving into a hex. The situation in the screenshots seems to be a bug, as the situation with a bridge the unit type can't use and without a bridge at all are not identical even though they should be, I think.

I'll create a separate thread.