Shannon V. OKeets -> RE: Game Crashes at Annual Additions (1/11/2014 3:08:05 AM)
|
quote:
ORIGINAL: Cad908 quote:
ORIGINAL: Shannon V. OKeets quote:
ORIGINAL: GTMOON51 Rob Sent Bug Report to madexcept@matrixgames.com Gary Like Rob, I was able to restore and run your saved game without any trouble. The bug report gives and I/O error 103, which means it was trying to write out an automatic saved game and was unable to close the GAM file after having written out all the data. Is there a problem with your disk drive? The bug report shows that there is plenty of RAM available and your running the most recent version (1.0.8.3), so those aren't the problem. One other possibility is that there are two copies of MWIF running. In your screenshot it looks like that is the case - but I could be interpreting the icons incorrectly. Steve, Gary e-mailed me that he was able to clear this by turning off the autosave before advancing to Jan/Feb 40's Annual Additions. Seems odd as there were 2 full turns without an issue with the autosaves, yet it crashed at the first Annual Addition. There is no player interaction with that phase as the game updates the force pool automatically. Something specific in the code for Annual Addition's autosave? Operating System (Windows 8)? Is the autosave necessary here? No other player has reported this bug and I have never seen this on any of my systems. Strange. -Rob I have had occasional "I/O error 103" reports from players but I have not been able to reproduce any of them. Nor can I see any commonality when they occur. Apparently it can happen anytime an autosave is performed.
|
|
|
|