Peter:
Let's assume that the rise of terrain for PG hill starts in the hex before the hex with the contour line and ends in the hex with the contour line and covers the entire distance of the two hexes, thus 400 meters. Thus the rise is a 5% slope. On a road on flat ground it takes a truck travelling 30 mph, 30 seconds to traverse the 400 meters (calculated at
Speed Distance Time Calculator). So assuming a laden truck will double its time traversing a 5% slope (although I would think the driver could simply accelerate), it would take a minute. In a 15 minute turn the notional truck could traverse 30 such hexes which is certainly greater than the 16 hexes a truck with 8 MF can do in a turn. (This actually then jives with strategic movement and thus the normal movement rate was likely slowed down for "tactical" reasons such as moving slower and more cautiously when near the enemy). So, the 8 MF is taking into account many variables that could slow down a truck and we PG battalion commanders are above that resolution of the game.
Now if a scenario or module has extreme terrain, such as long mountain roads such as what you live near etc. The module/scenario designer should include special rules to compensate for such terrain. However, the general rule does not need such compensation becasue the extremes should not drive a rule
However, again, I reiterate, hopefully a bit more clearly this time, that the reality argument is immaterial to the rules as written. And the rules are quite clear:
To obtain the movement benefit of roads, movement must follow the road across a hex side containing the road, not just into or out of a road hex. Units moving along a road (including bridges)
pay the road movement cost on the TEC, not the cost of the terrain in the hex.
Slope is a terrain, it is listed on the TEC distinctly as a "terrain type." Thus, IAW Rule 5.2, the +2 for Motorized movement on slope and +1 Mechanized moment are ignored when calculating movement costs when moving along the road. There is no other way to see it. And reality arguments and other rules that don't explicitly address 5.2 do not matter, nor influence and thus do not pertain to Rule 5.2.
