From: Genoa, Republic of Genoa (occupied by Italy)
Well it does take some time on my computers as well, 35-45 seconds.
ORIGINAL: Peter Fisla
UP844, I have done some testing with your saved game file and for me it takes about 30 seconds for the game engine to respond.
Thanks for the tests: your replies confirm that - even with a PC more recent and powerful than mine - moving the T-34 closer to the front will then take a significant amount of time.
Assuming the tank is CE and able to use the road movement rate, it will take 10 to 15 minutes to move 20 hexes (spending some MPs to start, change elevation and changing its VCA). The Russian receives 18 AFVs as reinforcements on turns 13,14 and 15, which will then require 180 to 240 minutes to move.
ORIGINAL: Peter Fisla
Every time your friendly unit moves, the game needs to check every enemy hex if it actually contains enemy units, to see if there is a LOS or not.
The T-34 in the saved game file is approximately 50 hexes away from the nearest German unit (a broken SS squad in 3,81). Since the delay is much shorter in night turns, when visibility is 2 hexes, I suppose the LOS-checking routine does not perform the whole LOS-checking procedure if the range is greater than the visibility range. Is this assumption correct?
Some more remarks I hope could be helpful to solve the issue:
I have noticed, in CG001, that the delay does not significantly decrease even when there are very few enemy units on the map. By way of example, at the end of day 3, the only "enemy-occupied hexes" were a few hexes (about half a dozen) containing unpossessed German SW (which require a LOS check to decide if the SW counter must be displayed or not).
I also noticed that the delay does increase as the game progresses: I started another CG002 and moved a KV-1s on Turn 1: the delay is about 5-7 seconds (see attached save file), even though there are much more German units than in the saved game I attached above.
I launched the LOS tool to see if it could calculate the range between the T-34 and the nearest German unit: the message appearing in the LOS tool window reported that range was greater then the scenario visibility range, but it also stated "Check_LOS_FOW executed 2347 times" and "64.65 seconds".
Apparently, every LOS check took approximately 0.0275 seconds: what does, however, a single LOS check execution imply? Checking LOS between a unit and an enemy-occupied hex? In this case, checking LOS between the T-34 and all the enemy-occupied hexes (let's assume there are 30 of them) should not take more than 0.825 seconds. I'm quite puzzled .
Chasing Germans in the moonlight is no mean sport
Long Range Fire (A7.22)........1/2 FP