Removed an inconsistency between quickload and regular load

Turned on heap checking for debug builds.  *Could cause memory to run low if game runs for extended periods
Fixed assertion message for case where soldier groups try to cross impassible terrain
Fixed inventory memory leak


git-svn-id: https://ja2svn.mooo.com/source/ja2/trunk/GameSource/ja2_v1.13/Build@1110 3b4a5df2-a311-0410-b5c6-a8a6f20db521
This commit is contained in:
Overhaul
2007-07-24 09:14:56 +00:00
parent 48527d4aa5
commit b559e8601d
4 changed files with 12 additions and 5 deletions
+5
View File
@@ -430,11 +430,16 @@ void SetSaveLoadExitScreen( UINT32 uiScreen )
SetPendingNewScreen( uiScreen );
#if 0
// 0verhaul: This is a repeat of the previous line, but with a different variable set.
// None of it really makes sense. Why would a quicksave be different from a regular one?
// Why should ctrl+L act differently than alt+L?
if( gfDoingQuickLoad )
{
fFirstTimeInGameScreen = TRUE;
SetPendingNewScreen( uiScreen );
}
#endif
ExitSaveLoadScreen();