Philippe wrote:I just ran the Steam version of TEAW 1916 scenario for about four turns without crashing.
(The reason I mentioned that it was the Steam version is that the Steam version should have slightly fewer system resources available to it).
So the good news is that I seem to be able to run 1916 without crashing. The bad news is that turn processing is not the worst that I've seen, but it is on the slow side. I attribute this to the fact that Athena has to make a lot of decisions and give a lot of orders because the sceanrio is so big. The game needs more standalone scenarios that focus on smaller chunks of the action, like a Verdun piece that might include the battle of the Somme, but no Italy, no Eastern Front, no Middle East. The 1916 scenario is a mini-monster as far as processing goes. At least on my rig.
Bottom line: whatever issues there are may be peculiar to the OP's hardware and configuration. Probably not a Pocus issue unless it turns out that there's a whole class of users who are in the same boat for the same reason.
(For the record, I am running with 64-bit Windows 7 Professional and 8 Gigs of Ram).
It appears that I jumped the gun as to this being a bug. It's not a crash, but just extremely LONG turn processing times. I've never seen an AGEOD scenario take so long to process a turn. The turn was taking so long to process that I just assumed that it to be a crash. (And when I pressed CTRL-ALT-DEL to get out of the game, my task manager would state that the game had stopped responding.) Still, upon reading your experience as to long turn processing times, I decided to give it another shot. I actually stepped out of the room while the turn was processing so I'm not exactly sure how long it took, but when I returned the scenario had successfully proceeded to turn 2.
I've got an I-5-4460 3.20 with 8 GB Ram. It's a fairly decent machine, but obviously this scenario tasks it