Hello all,
First, sorry for the caps, I dont usually use them but I believe this post is important, so....
Many players have posted about the 1940 save crash bug. For those of you who dont know about it, it seems that around 1940 (spring for a 36 GC and later for a 39 GC) the game often crashes, especially right after reloading a saved game. What usually happens is that, after getting everybody in game and pausing until everybody finishes giving his orders, the host unpauses the game which will run an hour or two before the host crashes.
Tonight, the regular group I am playing in met at 21h00 for our weekly Wednesday night game. We are currently playing a 36 General Campaign that started several weeks ago. We loaded our saved game (February 23rd, 1940), got in game, paused the game while everybody gave their orders, unpaused.... and the host crashed! Rince and repeat, rince and repeat, the scenario repeated itself whatever we tried. And we did try all kind of solutions without any success.
After about three hours of unsuccessful attempts (and only 1 defection from our 7 strong - very dedicated! - players group), one of us, Seleucus not to name him, became convinced that the crashes had something to do with the initial pausing. He suggested that we should load the game and start it without pausing, giving our orders 'on the fly'. We tried it, our 1000th test of the night, and, oh!, miracle!, it worked!!! We could give orders and play normally and it did not crash and seemed very stable.
Of course, this needs more testing and right now it is just a hypothesis, but it would seem that the fact that the computer has to redo the strategy for every AI nations (presumably a lot of calculations) added to the rather huge number of orders given by the human players after a reload makes the host's computer crashes. This hypothesis is further supported by several observations we made:
1) Pausing after a few days have gone by (after relaoding a saved game) has no harmful effect, probably because the calculations/orders for the AI nations are less numerous then;
2) This bug occurs mainly in 1940. Prior to that, there is less warring, less units of all kind in play and presumably, a lot less calculations for the computer;
3) We did try not to give any order (movement or attacks) and let the game run. Everything went well and we experienced no crash. Again, we can assume that without the human players' orders, the computer was able to cope with the AI nations calculations/orders.
In conclusion, we think/hope that the bug is due to the huge number of AI calculations/human orders that the computer has to cope with after the reload of a saved game at a time (1940+) where the number of units on the map and the number of warring nations has increased significantly.
Please give any feedback that could help the players to pass this very annoying bug and Paradox to fix it. Further results from testing would be great to see if our solution works for other players.
Regards,
Ghis
First, sorry for the caps, I dont usually use them but I believe this post is important, so....
Many players have posted about the 1940 save crash bug. For those of you who dont know about it, it seems that around 1940 (spring for a 36 GC and later for a 39 GC) the game often crashes, especially right after reloading a saved game. What usually happens is that, after getting everybody in game and pausing until everybody finishes giving his orders, the host unpauses the game which will run an hour or two before the host crashes.
Tonight, the regular group I am playing in met at 21h00 for our weekly Wednesday night game. We are currently playing a 36 General Campaign that started several weeks ago. We loaded our saved game (February 23rd, 1940), got in game, paused the game while everybody gave their orders, unpaused.... and the host crashed! Rince and repeat, rince and repeat, the scenario repeated itself whatever we tried. And we did try all kind of solutions without any success.
After about three hours of unsuccessful attempts (and only 1 defection from our 7 strong - very dedicated! - players group), one of us, Seleucus not to name him, became convinced that the crashes had something to do with the initial pausing. He suggested that we should load the game and start it without pausing, giving our orders 'on the fly'. We tried it, our 1000th test of the night, and, oh!, miracle!, it worked!!! We could give orders and play normally and it did not crash and seemed very stable.
Of course, this needs more testing and right now it is just a hypothesis, but it would seem that the fact that the computer has to redo the strategy for every AI nations (presumably a lot of calculations) added to the rather huge number of orders given by the human players after a reload makes the host's computer crashes. This hypothesis is further supported by several observations we made:
1) Pausing after a few days have gone by (after relaoding a saved game) has no harmful effect, probably because the calculations/orders for the AI nations are less numerous then;
2) This bug occurs mainly in 1940. Prior to that, there is less warring, less units of all kind in play and presumably, a lot less calculations for the computer;
3) We did try not to give any order (movement or attacks) and let the game run. Everything went well and we experienced no crash. Again, we can assume that without the human players' orders, the computer was able to cope with the AI nations calculations/orders.
In conclusion, we think/hope that the bug is due to the huge number of AI calculations/human orders that the computer has to cope with after the reload of a saved game at a time (1940+) where the number of units on the map and the number of warring nations has increased significantly.
Please give any feedback that could help the players to pass this very annoying bug and Paradox to fix it. Further results from testing would be great to see if our solution works for other players.
Regards,
Ghis
Last edited:
