ORIGINAL: gliz2
Bob we could thrown in examples but I think the discussion is missing the common ground.
How long it took for Hitler to (not) react to Normandy, 6 hours (he was a late sleeper)? Or Soviets to order the full counter offensive in June'41?
I also have a France 1944 D-Day scenario at 1/2 week intervals that also works like a charm.
tm.asp?m=1726673
And ordering something is not the same as having the orders carried out.
I think you are confusing strategic planning with normal reaction to the events, which was happening without much of a delay. Simple example? Dispatchimg paras to Bastogne during the Bulge. You are not able to react that quick with 3.5 days turn on a 5-10km scale. The reality is that the conditions change by the hour not by a week.
I actually model that in my Germany 1945 scenario (full week turns). 101st airborne is in reserve and reacts into the German spearhead.
tm.asp?m=1818685
Meanwhile, the rest of the Allied force (including Patton) didn't even react until they had a face-to-face meeting in Reims. That was not until the bulge had enveloped Bastogne and moved far past it. At that point, Monty still wouldn't commit to any reaction, saying he needed "some weeks" before he would be able. Patton's legendary swift reaction is far beyond the exception - it is still so remarkable as to be seen as proof of his genius.
The fact is that it takes time to figure out what is going on, with frontline units shattered or heavily engaged so that they are hard to contact - or they may not even know what is going on themselves. Then it takes time to plan the reaction, shift supplies, etc..
And just because someone programmed a scenario with a vision to get a specified result it does not mean that the system works.
That's not what I did. I modeled the historical conditions only. The scenario can go in any number of non-historical directions if non-historical moves are opted. But, if the historical moves are opted, it produces very historical results.
tm.asp?m=1893814