Crashes

[Distiller]

I also had the "EXIT" button problem. Now I wait extra long after saving, maybe 15 seconds or so, during which time my HDD light flickers three or four times, and only then I hit "EXIT". No black screens any more.
But I still have freeze-ups in the CBI area (mostly) when managing ground units. Game just freezes. Therefore I save after each and every larger island or base I manage, so I don't have to do things twice (which is extremely annoying) after reboot.
First thing I do after the computer had its turn I make a saving named "Start", then during my turn I do a couple of savings I have named "Ingame", and when I'm finished before pressing "end order phase" I do a saving named "End". So I keep losses to a mimum.
Will observe Frag's advice about the "Back" buttons. We'll see.

[Mr.Frag]

I hate to admit it here, but for the last week I have been playing HOI 2. It, like other of paradox's games, is buggy. CTD's. My last CTD happened during a "save" file being made. Blew away a week of gaming. Sigh.

Ouch, a week of HOI2 ... thats a lotta non-turns ... I feel for ya [:(]

[Mr.Frag]

Therefore I save after each and every larger island or base I manage, so I don't have to do things twice (which is extremely annoying) after reboot.

Hard hang? What operating system you running?

[Distiller]

ORIGINAL: Mr.Frag

Therefore I save after each and every larger island or base I manage, so I don't have to do things twice (which is extremely annoying) after reboot.

Hard hang? What operating system you running?

XP

[Mr.Frag]

XP

Did you have sound problems? Hard hangs of your system generally point to driver issues. Crashing to desktop is a "it's a bug" type thing. (not always the case, but 90% of the time)

[Distiller]

I don't know, I don't use sound.
Once when listening to Rush Limbaugh in the background it hung and produced a 10sec loop.
But I have the latest driver, so I don't think it's a sound problem.

[Charles2222]

ORIGINAL: Mr.Frag

Frag, try listening once. Those of us who have tried to pass along information to you about how the save screen crash occurs have told you again and again that the crash ensues when you click the EXIT button.

Try reading what I said again.

The crash at save is related to a blown stack ... the stack is blown from some other activity before you even get to the save screen. It has *generally* been pinned back to the same problem that causes the game to crash when using the back button. Avoiding the back button *elsewhere* generally results in not seeing the save crash.

As you will have noticed, no one *ever* complains about crashing on save after playing 1 turn. It is a buildup of leaks from something else that causes it after multiple turns.

Is this possibly related to the CTD's I get on occasion due to memory leaks? I never CTD or lockup on saves, but only during the game. What do you guys mean by 'back' button anyway? I maan I see back buttons ordinarily on unit screens but don't recall one on the save game menu. Would the back button also be translated as the Esc. key?

[Mr.Frag]

Would the back button also be translated as the Esc. key?

No, it's the quit/exit button.

Is this possibly related to the CTD's I get on occasion due to memory leaks?

Yes, it seems to be the prime cause. I have run hundreds of turns back to back ai vs ai without memory leaking so the leaks have to be in the interface itself (selection boxes, panels, sort, etc)

What drives me insane with stuff like this is the autosave runs perfectly well ... which pretty much rules out the save routine itself.

There is a command line switch -dd or -dw (-wd or -ww) that triggers automatic saving every turn (d) or every week (w) but be careful, it will overwrite other saves in the way.

first letter = d (full screen) or w (windowed)

[Charles2222]

I put so much work into each turn, I've pretty much got into the routine of saving 3-4 times a turn. Each save has a city name or 'end'. Too bad the auto-save won't save every 30 minutes or so regardless if it's the same turn or not.

[pad152]

Witp 1.4 has two crash bugs.

1. Save game crash bug:
Seems to happen on when you click on the exit button right after saving. It seems to happen more on a system that has a large number of saved files (60+) and the system is busy doing other things or needs a defrag. I bet this is a timming issue, the game is alowing you to click exit before the game is finish updating the save game file list. If you wait for the disk drive light to finish flashing (save finished) then click on exit, it won't crash.

2. Nighfighter crash bug:
Game crashes during nightfighter intercepts with combat animation on.

[mlees]

Seems to happen on when you click on the exit button right after saving. It seems to happen more on a system that has a large number of saved files (60+) and the system is busy doing other things or needs a defrag. I

Negative, good buddy.

I have routinely experienced this while I only have one save file. I only have Norton Antivirus in the "active programs" system tray, but it actually only does a full system sweep once a week. I do not have ANY other software running in the background. I even unplug my internet modem when I play games. (It's only "on" when I surf...) I defrag once a week also (right after the AV sweep). WinXP Home. No sound issues.

Different machines make for painful bug control. (That's why console games are stable: it's in their nature.)

[33Vyper]

1. Save game crash bug:
Seems to happen on when you click on the exit button right after saving. It seems to happen more on a system that has a large number of saved files (60+) and the system is busy doing other things or needs a defrag. I bet this is a timming issue, the game is alowing you to click exit before the game is finish updating the save game file list. If you wait for the disk drive light to finish flashing (save finished) then click on exit, it won't crash.

YaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaY !!!!! [:D]

I have done this. If I wait a few seconds after saving before clickin on the exit button it has not crashed.....yet.

[Mr.Frag]

I have done this. If I wait a few seconds after saving before clickin on the exit button it has not crashed.....yet.

That is a very real possibility ... the routine could be releasing a bit too quickly still.

[von Beanie]

This crash bug is VERY frustrating because it is hard to remember during normal play. Many times I spend more than an hour moving my units and adjusting orders, using the "back" button frequently. Then, at the end of my turn I look to see what reinforcements are coming soon. The "back" button works for all of the screens except the new ships screen. On that screen it crashes the game, costing me the hour it took to review the map, micromanage my forces and enter orders. This has happened at least three times in the last week because I'm a very slow learner when it comes to these sorts of problems.

Is there any way in v. 1.5 you could change the "back" button on the future ships screen to simply read: "Commit Harikiri"? Only then would I remember what the button really does.[:)]

[Mr.Frag]

Is there any way in v. 1.5 you could change the "back" button on the future ships screen to simply read: "Commit Harikiri"? Only then would I remember what the button really does

I bet Mike would like that request, he's spent enough time hunting for it [:(]

[mlees]

Hmmm. How do you play without using the "back" button at all?

Do you use the escape key instead?

[Mr.Frag]

Do you use the escape key instead?

Yeppers