|
rkr1958 -> RE: 4.4.1 Out of Memory & 4.2.3.2 Move Delay Due to Supply Calculation (2/6/2022 8:41:42 PM)
|
Zip file of CP-ArabianSea-Typical.GAM & NoCP-ArabianSea-Delays.GAM games attached.
To "quantify" the move delays we're seeing I timed how long it took to move 6 German units in Russia and 4 Italian units in France. The specific moves were:
Russia. German Units.
(1) V Mot corps. 40,50 to 38,52.
(2) Rommel HQ-A. 44,55 yo 47,54.
(3) XLVII Arm corps. 53,58 to Nikolayev 57,57.
(4) XLI Arm corps. 55,58 to Nikolayev 57,57.
(5) Mot div. 56,58 to Nikolayev 57,57.
(6) 1st Arm div. 51,56 to 56,58.
France. Italian Units.
(7) Cavallero HQ-I. 59,28 to 58,28.
(8) Badoglio HQ-I. 58,28 to 57,27.
(9) African Mech corps. 58,30 to 58,28.
(10) 3rd Inf div. 58,28 to 59,28.
I need to caveat the following timing results. There's learning involved that affects times as I went through these 10 moves at least a half of dozen times. There's inherent "noise" is pointing-clicking-moving-pointing-clicking too. However; with all that said I think the timing differences are stark and informative.
4.2.3.2
(1) CP-ArabianSea-Typical.GAM, 2 minutes, 40 seconds, Avg = 16 sec/move
(2) NoCP-ArabianSea-Delays.GAM, 5 minutes, 22 seconds, Avg = 32 sec/move (100% longer or double the time to make these 10 moves)
3.2.0.
(3) CP-ArabianSea-Typical.GAM, 1 minute, 40 seconds, Avg = 10 sec/move
(4) NoCP-ArabianSea-Delays.GAM, 1 minute, 30 seconds, Avg = 9 sec/move (considering "noise" no difference between these two cases with 3.2.0. Also, it took 60% to 320% longer to make these moves with 4.2.3.2.)
|
|
|
|
