GalCiv never sleeps?
from 
Stardock Forums
Stardock Forums
Is it possible that GalCiv does not detect wshen it has been put into the background?
Try this. Open the GalCiv folder so you can see the debug file (It may not exist if you
have never played a game). Start CalCiv. After a couple of turns go to the OS desktop
(CTRL-Esc). Refresh the GalCiv folder if necessary to show the icon for the debug file.
Left click _once_ on the debug file and the file's size shows up on the left side of the
window. Wait a few seconds, refresh and left click on the icon again.
In about a minute the debug file increased from about 1K bytes to 1Meg when I did this.
The bulk of the file seems to be a repetition of the following four lines:
------------
Debug Message: Lock: Unable to restore surface.
Debug Message: Surface Lost. Now restoring.
Debug Message: Trying to restore back surface.
Debug Message: DirectDraw Error: WRONG MODE
-----------------------------
This may not seem like much of a problem until the debug file gets so large that the OS
starts thrashing when you try to open it to find useful information on a crashed game. I
habitually play the game until I find something wrong, then switch to the desk top to
report the anomally, then switch back to the game. I have seen debug files of 80 Meg, which
when I try to load them cause the OS to thrash so badly trying to load the whole thing into
memory that my only resort is BRS.
Cheers,
Jack
Try this. Open the GalCiv folder so you can see the debug file (It may not exist if you
have never played a game). Start CalCiv. After a couple of turns go to the OS desktop
(CTRL-Esc). Refresh the GalCiv folder if necessary to show the icon for the debug file.
Left click _once_ on the debug file and the file's size shows up on the left side of the
window. Wait a few seconds, refresh and left click on the icon again.
In about a minute the debug file increased from about 1K bytes to 1Meg when I did this.
The bulk of the file seems to be a repetition of the following four lines:
------------
Debug Message: Lock: Unable to restore surface.
Debug Message: Surface Lost. Now restoring.
Debug Message: Trying to restore back surface.
Debug Message: DirectDraw Error: WRONG MODE
-----------------------------
This may not seem like much of a problem until the debug file gets so large that the OS
starts thrashing when you try to open it to find useful information on a crashed game. I
habitually play the game until I find something wrong, then switch to the desk top to
report the anomally, then switch back to the game. I have seen debug files of 80 Meg, which
when I try to load them cause the OS to thrash so badly trying to load the whole thing into
memory that my only resort is BRS.
Cheers,
Jack
