invalid type-aa assertion failure

[donaldseadog]

uses GE 2023.002,

included in zip:

custom battleset southPacificIslands,

hccw140314 db,

GE.log

screen shot

saved game 1 sec before popup.

game played on after ignoring error

 

type-aa-invalid-ge.zip

[TonyE]

Man, the impossible bug that keeps happening...

[TonyE]

Do you happen to know how/why AZA was launched?  I'm looking at a scary global variable called AirTargetType that could have been set when you launched airplanes from a base for an attack (as opposed to say pulling them out of a formation patrol, ferry mission, or long range patrol).   That global variable is throwing things off.  That is also why the problem isn't readily reproducible from a saved game since the state of the AirTargetType global variable is not saved to and loaded from saved games so it resets to the more friendly value of 0 rather than the unfriendly value of 1 that is leading to the assertion.

[TonyE]

Fix coded (again).  Thanks to your provided ge.log and saved game, I can force the unexpected value into AirTargetType which then leads to the assertion.  That lends credence to my theory about AirTargetType being the culprit but does not conclusively prove that theory nor conclusively prove that the fix is correct.

HCE - 2023.003 - 2023-04-##
===========================
- Chg:32923 GE Attempt again to fix type_aa != INVALID_ATTACK_CODE in Combat5.c
                assertion.  The theory this time is that the AirTargetType
                global is causing everything to go astray.  It should only
                be used by the player and I believe only when launching attacks
                so its value is reset to zero after any of those situations.
 

 

[donaldseadog]

3 hours ago, TonyE said:

Do you happen to know how/why AZA was launched?  I'm looking at a scary global variable called AirTargetType that could have been set when you launched airplanes from a base for an attack (as opposed to say pulling them out of a formation patrol, ferry mission, or long range patrol).   That global variable is throwing things off.  That is also why the problem isn't readily reproducible from a saved game since the state of the AirTargetType global variable is not saved to and loaded from saved games so it resets to the more friendly value of 0 rather than the unfriendly value of 1 that is leading to the assertion.

AZA was launched by me from base PortMorseby I'm fairly sure as an attack on the enemy base Manus Is but reassigned to attack the shipping. I think while flying to manus it detected the shipping and was reasigned by selection of AZA and issuing an F1 command to attack the shipping contact

As best I remember.