Defect Name: Assertion errors on quit

Build: HCE 2007.000

Repeatable: Y

Operating System: XP

DB used: HCDB-070524

Scenario used: WW3.SCq

Long Description: Game throws assertion errors when user attempts to end game.

 

In other test runs, assertion errors are reported within the game (user does not need to end game to cause them). It is not known if these two cases are related. Assertion errors occurring within this scenario are sporadic but non-replicable with any consistency. They do appear with this scenario approximate 1 in 7 runs.

 

Sequence to reproduce:

1. Order TROKA division to bombard Taebukpo-Ri.

2. Repeat gun order every second or so for the next 30 seconds until aircraft groups appear to launch from Taebukpo-Ri.

3. Planes will appear in a massive groups even though the airbase only had 90 at the start of the game

4. Quit game by clicking on Window close box.

5. Messages: Assertion11, Assertion12, Assertion13, Main executible appear

 

 

6. On a second test run, error messages; Assertion 21, Assertion 22, Assertion 23 appear

 

 

Expected behaviour: Game should not throw Assertion errors either in the game or when ending.

Observed behaviour: Game throws assertion errors.

Assertion_errors_on_quit.zip

I was unable to reproduce these errors with a new game and my current beta build. If you can consistantly reproduce it, would it be possible for you to get a save game that is close to the time that it happens and post it up? That way I can be sure if I can reproduce it or not.

I could create a saved game file, but there really isn't much of a point to it, IMO. You can just as easily create your own in about 35 seconds and it would probably be more valid by just following the instructions I've listed. It's only a matter of starting scen and running about 35 seconds in the game.

 

I don't use the the Beta release. I only use the game release.

I could create a saved game file, but there really isn't much of a point to it, IMO. You can just as easily create your own in about 35 seconds and it would probably be more valid by just following the instructions I've listed. It's only a matter of starting scen and running about 35 seconds in the game.

 

I don't use the the Beta release. I only use the game release.

 

In that case, perhaps it is safe to assume that the problem as been fixed by one of the beta patches? I made several tries last night and could not produce the errors.

Thanks for the effort. There's no way I can either confirm or deny it until the patch is released, then. Sorry, I have no access to the Beta.

Problem does not seem to appear in Patch 2008.024